Your Own Servers, With No Route Out
Some organisations cannot put their asset register in someone else's cloud. Not because of preference, but because a policy, a regulator or a customer contract says so. ASTITVAAMS runs on your own hardware, inside your own network, with no connection to the outside world if that is what you need.
What On-Premise Actually Means Here
Most vendors who say “on-premise” mean a dedicated tenancy in their cloud account. That is private hosting, not on-premise, and it fails the same audit question: does the data leave our infrastructure?
Here it does not. The application, the database and the file store all sit on servers you own, in a data centre or a room you control. No outbound calls, no telemetry, no licence check that phones home. If your network has no route to the internet, the system still runs.
Who Asks For This
Defence and strategic facilities
Sites where an air gap is the security model, not a configuration option.
Regulated manufacturing
Plants where the customer contract specifies where production data may be stored.
Financial services
Institutions whose policy forbids third-party cloud for asset and infrastructure records.
Healthcare
Hospitals holding equipment and patient-adjacent records under strict residency rules.
Public sector
Departments required to host inside a government or sovereign environment.
Anyone with residency rules
Organisations answering to a regulator about which country the data physically sits in.
The Same Product, Not a Cut-Down Version
The on-premise deployment is the same thirteen modules as the hosted one. Asset registry, lifecycle, procurement, maintenance, audit and verification, compliance, documents, depreciation, vendors, reporting, mobile operations and access control. Nothing is held back for cloud customers.
That matters because cut-down on-premise editions are common, and they tend to lose exactly the parts that made the system worth buying. If you deploy on your own servers you get the whole product, and it updates on the same release cycle.
Scanning Without a Network
An air-gapped server is only useful if the people on the floor can reach it. The mobile app holds scans, transfers, tickets and inspection results on the device and syncs when it reaches your network, so a technician in a basement plant room or a stores area with no coverage works normally and syncs on the way back.
This is the same offline capability the hosted version uses. It was not bolted on for on-premise customers.
When You Do Not Need It
Most organisations do not. If nobody has asked where your data sits, if you have no regulator to answer to, and if your security policy already permits cloud services, hosted is simpler and cheaper. You get the same product with none of the server, backup or patching responsibility.
On-premise is worth it when the answer to “where does the data live” has to be a room you can point at. If that question has never come up, start hosted. Moving later is a data migration, not a rebuild.
What a Deployment Involves
Hardware sizing depends on how many assets you are tracking, how much document and image data sits against them, and how many people are scanning at once. A small single-site deployment and a multi-plant one with ten years of history are different machines, so we size it with your IT team rather than publishing a specification that would be wrong for most people.
What we need from you before that conversation is a picture of your current setup and roughly what you are tracking. What you get back is a sizing recommendation, a runbook your team owns, and an installation plan.