How it works
What does on-premises mean, and why does it matter?
On-premises means the software installs on your own computers instead of a company's cloud. There is no server in a distant data center and no copy of the data on someone else's machine, so the reason the data cannot leak is that it never leaves the building.
Installs on your machines · no distant data center
Cloud software keeps your records on a company's servers and charges you to reach them. On-premises software runs where you are, on hardware you control.
That one difference changes everything downstream: the data stays with you, the system works offline, there is no account that can be shut off, and there is no bill that grows as you add staff.
It installs as an ordinary app, starts on a single office machine, and grows to a shared server later without redoing the work.
What it looks like on day one
It installs the way any other application on a staff computer installs. There is no data center to build, no rack to buy, and no minimum fleet. One office machine is a legitimate starting point, and many tribes begin exactly there.
The system looks at the machine it is running on and adapts to it. A standard office computer runs a department comfortably. A stronger machine simply runs the AI faster. Nothing about the design assumes you have bought new hardware.
What your IT is actually taking on
- Install
- An ordinary application on a machine you already own. No data center, no rack, no minimum fleet.
- Network
- Your own. The system runs with no internet connection at all, and can be configured with no path to an outside network.
- Growth path
- One office computer, then a shared server on your own network, then more offices. The same sealed records carry forward. Nothing is redone.
- Backups
- An encrypted copy on a drive you hold. Restore onto another machine when you need to.
- Who administers it
- You do. There is no vendor console with standing access to your government's records.
- Remote staff
- Reached over an encrypted connection your government controls, not a public login page.
How it grows without being rebuilt
The usual trap in government software is that the pilot is disposable. You prove the idea on something small, and then the real deployment throws that work away and starts over.
This grows along one path instead. The records sealed on the first machine are the same records that move onto a shared server, and the same records that a second office reads across your own network. The first department's work is the foundation of the second, not a rehearsal for it.
- One machine, one departmentStand it up where the work is hardest right now. Real matters, real records, real staff.
- A shared server on your own networkWhen more people need it, the same sealed records move onto a machine your offices reach across your own network. No traffic leaves for the internet.
- More offices, one governmentThe courthouse, the tribal center, and enrollment work from the same records, so a person is one person across all of them.
- Remote staff, on your termsPeople working from another building or from home reach it over an encrypted connection your government runs and can revoke instantly.
On-premises, from each seat
Tribal IT
It is yours to run, and it is small enough to run.
Standard machines, your network, your backup drive, your keys. The work it adds is a backup you already know how to take. The work it removes is administering accounts with an outside company.
Council
The records are in the building.
There is no distant server holding the government's records under another jurisdiction, and no account that can be suspended by someone who is not accountable to the tribe.
Staff
It is just an app on your computer.
You open it and work. No login page that is down, no waiting on a connection, no slow days when the line to the outside world is bad.
Questions IT asks first
- Are we now responsible for uptime?
- You are responsible for the machine, the way you already are for the machines in your offices. What you are not responsible for is a dependency on someone else's uptime, which is the part you could never actually control.
- What happens if a machine dies?
- You restore the encrypted backup onto another machine and keep working, with the complete sealed history intact. That is a drill worth running once so the office has seen it.
- Do we need someone on staff who knows this deeply?
- No. It is stood up with your IT so your IT can run it, and the day-to-day is ordinary computer administration. The specialized knowledge is in the software, not in the person who maintains it.