The record runs on
your infrastructure.
One organization, one installation. Deploy Resident Tab inside your own network — the data, the backups and the uptime stay entirely under your control. No shared tenancy, ever.
Four steps from zero to your own record.
Provision a host
A Linux VM or container host on your infrastructure, meeting the baseline spec.
Install & configure
Run the installer, point it at your database and storage, set your org name.
Provision operators
Create your team's accounts — there are no public sign-ups to lock down.
Start the record
Add your first unit and the timeline begins — permanent from event one.
Everything sits inside your boundary.
Resident Tab server
The application, running as a single-tenant install.
Immutable ledger DB
The permanent record — corrections appended, never overwritten.
Document storage
Leases, signed copies and uploads — on your volumes.
Backups & logs
Your backup policy, your retention, your audit logs.
Standard building blocks. No exotic dependencies.
If your team already runs containers and Postgres, you can run Resident Tab. On-prem, private cloud, or an air-gapped rack in a closet — it doesn’t care, as long as it’s yours.
ON YOUR METALHost it yourself — or have us host it, privately.
Customer-hosted
You host on your infrastructure. Data, backups and uptime are entirely yours.
Managed private hosting
We run a dedicated, single-tenant instance for you. Still one org, still isolated — just not your ops burden.
A system of record should outlive the vendor that shipped it. Self-hosting means the history of your units is yours — not a login you hope keeps working.
Own the record,
end to end.
We’ll walk your team through the deployment guide, the baseline spec, and whether customer-hosted or managed private hosting fits you best.