Where AssetBase Runs

AssetBase runs two ways from one codebase. The topology is a deployment choice, not a different product.

On-Premise Appliance

A sealed box (a mini-PC or a VM) that sits inside your site network and runs the whole system: the API (with its built-in sync scheduler) and its database (MongoDB) — as a single Docker bundle.

• Single-tenant — each appliance is provisioned for exactly one organization (its tenant id is baked in and enforced).
• Offline-tolerant — works fully offline; only reaches the network to authenticate, with an offline-grace window so audits never stop.
• Syncs up — when connected, it syncs its data to the central cloud for reporting and backup.
• Sealed — the appliance is delivered as a Docker image; source is not exposed. Optional hardware-bound licensing controls activation.

docker compose up # API (with built-in sync scheduler) + MongoDB

Cloud SaaS

The same product hosted centrally, multi-tenant, accessed in a browser.

• Tenant-partitioned — every record is scoped to its organization.
• Isolation option — organizations that need physical separation (e.g. on-prem clients, compliance-sensitive tenants) can be routed to their own database, without fragmenting everyone else.
• Hosting — the API runs as a Docker container behind a web server; the web app is served as static files. Managed MongoDB backs the data.

How Data Is Organized

• The asset register (installed_base) and purchase-order provenance are shared platform entities.
• AssetBase's own tables (scan_interface, audit sessions and exceptions) live in the AssetBase database.
• Everything is scoped by organization (tenant), whether pooled in one database or isolated per client.

See AB-060 for the data model.