Governed teammates for real team work.
Teammates sign in to your tools, use them the way your people do, and come back with finished work. Adaptable to how you work. Auditable on every step.
Built from our state and federal work · Mac app, iOS and Android coming soon
Head to head
How it compares.
Other ways to put agents under control, side by side. Pick one to see where Ori differs; each row is drawn from that product's own public positioning.
| Compare | Ori | Palantir AIPAI platform for data and operations |
|---|---|---|
| Built for | Procedure work in regulated teams | Critical commercial and government operations |
| Where it runs | Your environment, by our engineers | Cloud, on-premises or air-gapped, managed by Apollo |
| Signs in to your tools | Through Data Connection sources and webhooks | |
| Policy per kind of work | Role grants, Markings and project controls; per-action confirmation on chatbot actions | |
| Every action recorded | Allowed, refused or waiting, with its reason | Audit logs, session logs and execution traces |
| Human sign-off | Built in | Confirmation on chatbot actions; Ontology edits staged for human review |
| Voice and video | Voice via Realtime audio; video not stated |
When Palantir AIP is the better pick: You already run, or plan to run, Foundry's Ontology as your operational data layer and want agents, human review and audit inside that platform, on-premises or air-gapped included.
Competitor rows describe each product's own public positioning as of November 2026. Check their sites for current details.
The job
Procedure work is most of the work. It still runs on people's afternoons.
Write the procedure once. Teammates follow it in their own computer, every time, and bring the result to a person.
- Someone re-reads the rules for every bid
- Exceptions surface when an auditor finds them
- Citations are copied by hand and rarely rechecked
- Nobody can show who did what, and why
- The procedure runs the same way every time
- Every exception is raised as it happens
- Each citation is checked by code
- Every action is recorded as allowed, refused or waiting
Use cases
Any work a team already does by procedure.
Procurement
Bids compared to your rules
Flags the gaps and drafts the award memo for sign-off.
Concessions
Operator reports against the contract
Tracks minimums and renewals, and raises every exception.
Contracts and leases
Every clause cited
Marks what breaks policy. Each citation is checked by code.
Finance operations
Invoices matched to orders
Chases missing paperwork and queues payments for approval.
Voice and video
Talk to a teammate. Or watch one work.
Start a call from any chat. Teammates answer out loud, take instructions while you walk, and ask before they do anything that matters.
Video agent
Face to face with your teammate
Start a video call from any chat. The teammate answers on camera and asks before it does anything that matters.
Concept · in the apps you already use
Reach your teammates from Claude or Codex.
This is where we are taking Ori: ask from the AI app you already work in, and the same governed teammate does the work. The policy, the audit trail and the person who signs off stay in Ori.
The teammate recommends bid A and drafted the award memo. It is waiting for a person to approve it in Ori before anything goes to legal.
Governance
Adaptable to your work. Auditable on every step.
Built from our state and federal work, where the security bar is the highest we operate under.
Adaptable
Each kind of work has its own policy: what a teammate may use, which sites it may open, when it must ask. Change the file and the teammate changes with it.
kind: procurementteammate: Procurement Buyertools: documents, spreadsheets, email (draft only)sites: vendor-portal.example.govask_before: any write outside the workspaceask_before: sending anything to a vendorjudge: reads every award memoevidence: every rule cited is checked by codesign_off: procurement officer
Change the file and the teammate changes with it.
Auditable
A judge reads the work, code checks the evidence, and a person signs off. Every action is recorded as allowed, refused or waiting, with its reason.
| When | Teammate and action | Outcome |
|---|---|---|
| 10:42 | Procurement Buyer Read bid-B.pdf | Allowed |
| 10:41 | Procurement Buyer Write to the vendor portal. Writing outside the workspace asks a person first. | Needs approval |
| 10:15 | Concessions Manager Open a website. The site is not on this teammate's allowed list. | Refused |
| 09:58 | Contract Reviewer Record a finding on the late fee. The citation was found on page 7 by code. | Allowed |
One action
Allowed, refused or waiting. Never silent.
Before a teammate acts, its policy decides. Reads inside the workspace go ahead, writes outside it wait for a person, and sites off the allowed list are refused, with the reason recorded each time.
teammate Procurement Buyer policy procurement10:42 read bid-B.pdf allowed10:41 write vendor portal needs approvalwriting outside the workspace asks a person first10:39 judge reads award memo passed10:39 code checks rule 4.2 citation found, p. 3waiting on: procurement officer
How it runs
Four steps from procedure to sign-off.
- 01
Write the procedure
Once, the way your team already does the work.
- 02
Set the policy
What the teammate may use and open, and when it must ask.
- 03
The teammate works
In its own computer, signed in to your tools.
- 04
A person signs off
A judge reads it, code checks the evidence, you decide.
The honest limit
Start here
Take the guided tour of the live demo: what people see, then what admins govern. Or bring a procedure to a call.