Sovereign Infrastructure
Automated tagging, classification, and filing cut the time staff lose finding records and rebuilding reports, on cloud infrastructure the Nation or organization owns.
Llama
The platform
Context-aware documents. Clean data. Streamlined workflows.
The order is deliberate. Reporting is only as good as the records underneath it, and inference over a disordered corpus produces confident nonsense.
Migrate or integrate
Move what should move. Connect what stays.
Some records belong on the appliance. Some systems belong where they already are, connected to it. You decide which is which, department by department, and nothing has to change all at once.
Migrate records from your current provider
Integrate the systems you are keeping
Single sign-on and role-based access
The value
What it saves.
Estimates from our own deployment work, and marked as estimates. The rest are not.
Time to find a record
Less time spent locating a record, estimated. One permissioned search across documents, files, scanned text, tasks and notes, instead of a shared drive, an inbox and a filing cabinet.
Records on premises
Storage, database, search, character recognition, conversion and inference all run on the appliance in your building. Not an estimate.
Report assembly
Faster assembly of a recurring report, estimated. Reports are built from records tagged when they arrived, so the quarter is assembled rather than reconstructed.
Cost to leave
Dollars. Export in open formats on a defined timeline, written into the customer agreement rather than a policy we can revise. Not an estimate.
How it works
How a deployment runs.
Staged, and priced at each stage. Every step produces something you keep whether or not you carry on to the next one.
Discovery
Forty hours, department by department, mapping how information actually moves. You keep the map whether or not you go further. $6,000.
Architecture
Eighty hours turning the map into a record taxonomy, retention rules and a permission model your staff will actually follow. $12,000.
Deployment
One department first. The appliance goes into your building, records migrate, staff are trained. Managed operations from $1,500 a month after that.
Plans
What it costs.
Published so you can budget before you speak to anyone. Seats are per user per month. Hardware and setup are quoted separately and listed below.
FAQs
Questions we get asked.
If the answer you need is not here, ask us directly. We would rather answer it once, properly.
How long does a deployment take?
It is staged. Discovery is forty hours, department by department. Information architecture is eighty hours and produces the record taxonomy, retention rules and permission model. Deployment then starts with one department rather than the whole organization. We do not publish a fixed timeline, because the pace is set by how quickly your own people can make governance decisions, and that is the right order.
Where does our data physically live, and who can reach it?
What happens to our records if we stop working with you?
Does any of it work without an internet connection?
What is built today, and what is not?
What does it cost, and what changes as we grow?
Does this replace Microsoft 365, or our finance system?
Blog
Notes from the work
Occasional writing on records, reporting, and what sovereignty means once it has to run on hardware someone maintains.












