We install AI inside your business.
Private agents that run on your own hardware, answer from your own data, and cost nothing per question, per seat, or per user.
What we build
Three practicesAgentic architectures
Retrieval and reasoning systems wired into the databases, ERPs and schedulers a business already runs on — with failure modes designed in, not discovered later.
- RAG over live operational data
- Failure-aware response design
- Human-in-the-loop approval paths
Automation & orchestration
Workflow automation that carries production discipline: versioned, monitored, alerting on its own failures, and reviewable line by line before it ever touches your data.
- Workflow and API orchestration
- Scheduled and event-driven pipelines
- Operator alerting and escalation
Sovereign & private AI
For regulated and defence-supply-chain work: models that run on your own hardware, on your own network, where no prompt leaves the building.
- On-premises models, no GPU required
- Active Directory and LDAP integration
- Essential Eight ML2 alignment
- Data-residency by architecture
The reference architecture
Full stack · Observability at every layerWe deliver the whole stack, not a layer of it — and every layer reports on itself, so the platform can be proven to be working rather than assumed to be. We do not publish the bill of materials. Components are selected per client against their regulatory and network constraints, and disclosed under engagement; naming the internals of a client's platform on a public page is reconnaissance we are not willing to hand out.
The hardware question
Local modelsNo GPU.
For everyday operational tasks, a locally hosted model does the work most people currently send to a public AI service — with the difference that nothing leaves your network.
Inside the platform
Three surfaces, one stackThe staff portal
One address for everything AI in the business. Tiles a person is not entitled to stay visible but inert, so staff can see what exists and request access — rather than discover a wall.
AI PLATFORM
▾
▾
The operations launchpad
Every console behind the platform in one gated page, with a live health indicator polling the status plane. Delivery is the easy part — this is the surface that proves the thing is being run.
ADMIN LAUNCHPAD
▾
▾
The agent at work
An answer grounded in the company's own operational data, with the source named and the limits of the answer stated. When it cannot know something, it says so instead of inventing it.
SO-48117 is the most exposed — it is queued behind a changeover and has no float left. SO-48122 and SO-48130 lose their buffer only if the changeover runs over its standard time. SO-48145 is at risk from a material receipt that has not been booked in.
I can see the schedule and the order book, but not the inbound delivery status — the receipt date for SO-48145 needs confirming with purchasing before you treat this as final.
Representative interfaces · fictional company, fictional data · no client system depicted
How we work
Four commitmentsArchitecture before tooling
TOGAF-grounded design. We establish the target state and the constraints — regulatory, network, budget — before a single product is chosen.
Production discipline from day one
Backups before edits, controlled restarts, a stated rollback path for every change. There is no "it's only the pilot" phase.
You get the documentation, not a dependency
Every engagement ends with a set of documents your own team can work from. Lock-in is a business model, not an outcome.
Compliance is designed in
Defence Industry Security Program and Essential Eight Maturity Level 2 obligations shape the architecture from the first diagram, not the final audit.
Who this is for
And who it is notThis is for you if
- ✓Your industry, your insurer or your customers impose obligations on where data lives and who can reach it.
- ✓You already run your own servers, or you are willing to, and you would rather own the thing than rent it per seat.
- ✓Your team is doing work by hand that a system should be doing, and you can name it.
- ✓Someone internal will hold the keys afterwards — you want documentation, not a retainer you can never leave.
This is not for you if
- ✕You want AI to replace your team. It will not, and we will not sell you that.
- ✕You want the cheapest option rather than the right one. A public subscription is cheaper on day one, and that is a legitimate choice.
- ✕Nobody internally owns IT. Something that runs inside your business needs someone inside your business who cares that it is running.
- ✕You need it live next week. Architecture done properly takes longer than that.
Still sceptical? Good.
Three honest answers"We tried AI and it made things up."
So does an unconstrained model with no grounding. Ours answer from your documents and your databases, name the source, and state plainly when a question falls outside what they can see. The failure modes are designed and tested before anything reaches a user.
"It will become another thing we depend on you for."
Everything we build is handed over documented, down to the configuration files and the rollback path. If you replace us, the platform keeps running and your team has what they need to run it. That is a deliberate commercial position, not an accident.
"Our data cannot leave the building."
Then it does not. The models run on your hardware, on your network, behind your perimeter. This is the constraint we design for first, not a feature we bolt on afterwards for regulated clients.
A regulated Australian manufacturer, from zero AI capability to a governed platform serving staff and partner organisations.
How to start with private AI architecture
No obligationBring us a process you think an agent should own. We will tell you honestly whether it should, what it would take, and what it would cost to run.