An Asset Register That Cannot Touch the Internet
Your servers, your network, no route out
Nothing phones home, including for licensing
Users see only the establishments they are cleared for
Every handover recorded and not editable afterwards
1. The Problem
A defence or strategic installation cannot put its asset register on somebody else infrastructure, and often cannot connect the network carrying it to the internet at all. That rules out most modern software, so the register stays on paper or in standalone spreadsheets on individual machines. Each establishment does its own thing, and there is no way to see a position across several without physically collecting files.
The other requirement is compartmentalisation. Not everyone who uses the system should see everything in it. A register that shows every establishment to every user is a problem in itself, which is a further reason paper survives: paper is compartmentalised by where it is kept.
2. How ASTITVAAMS Handles It
This is the same product as the hosted version, installed differently. Four things matter:
Installed on your hardware
The whole system runs inside your network. There is no external dependency, including for licensing, so an air-gapped installation behaves exactly like a connected one.
Visibility follows clearance
Users see the establishments their access covers and nothing else. The register is compartmentalised in software rather than by which cupboard it sits in.
Scanning without a network
Handheld scanning works entirely offline and syncs to the local server when back in range, which suits sites where coverage is deliberately absent.
Handovers that cannot be rewritten
Custody changes are signed and appended. A record of who held what in March is still there in December, unaltered.
The register moves off paper without anything leaving the premises. ASTITVAAMS runs on your own hardware with no route out, and users see only what their clearance covers.
3. What Changes for You
- ✓Modern records without an external connection: Scanning, custody trails and reporting work as they do anywhere else, with nothing crossing your network boundary.
- ✓A position across establishments becomes possible: Where clearance allows it, several establishments can be seen together without physically collecting files.
- ✓Compartmentalisation is enforced, not assumed: Access is defined in the system rather than depending on where a register is stored.
Take This Away
A PDF covering the on-premises deployment, what it requires from your infrastructure, and how clearance-based visibility is configured. Written for a technical and security review.