Enterprise AI · Oracle, Workday, ServiceNow
AI agents that work inside your enterprise systems, as your people
Ask in Teams or Slack. The agent does the work in Oracle, Workday, and ServiceNow, as you.
- 1
- chat your people already use
- 0
- credentials in the model's context
- 1
- workflow to start with
Just ask
Every request, every approval, and every answer stays in the conversation
Sign in to review your approvals
Sign in to ServiceNow as yourself. No approval is made during sign-in.
Sign in to ServiceNowSigned in as you · 2 requests need your decision
- Backfill: Nurse, unit 4BPosition request
- Time off: 12 hours, Fri Oct 9Absence request
Our point of view
Business process is proprietary. The agent that runs it should be yours.
Built into each platform
Oracle, Workday, and ServiceNow each build agents, identity controls, and audit into their own platform, and each has opened a door for outside agents. We build for those doors.
Built around your business
A supplier invoice over its purchase order checks the order in the ERP, the contract terms, and an approval in ServiceNow, each in a different system. That path is yours, and that is the agent we build.
How we think about it
Three layers. Identity stays the same across all of them.
People, the assistant, and the systems it works in. Each layer has a clear owner and a clear boundary, which is what makes the whole thing reviewable by your security team.
01
People
Roles, and what each role may do.
- Each person has roles. Each role can do specific things in each tool.
- Teams or Slack tells the agent who is asking. The agent uses that identity for every check.
- A manager sees their departments. An admin sees more. The agent works within those limits.
Example. An employee asks for their own balance and gets it. A manager asks for a team member's balance and gets it only because the HR system already allows that.
02
The assistant
Runs inside your cloud. Decides, checks, asks, acts.
- Runs in your cloud: Microsoft Foundry, AWS Bedrock, or Claude managed agents. Your model, switchable later.
- Keeps its working state in PostgreSQL and logs every action. Business records stay in your systems.
- The model decides. Code acts as the person asking and checks every permission. The model never sees a credential.
Example. A manager asks to approve an invoice. The model picks the approval tool. Code confirms the manager is the assigned approver, waits for their yes, and submits it under their name.
03
Integrations
The systems you already run, connected as the person asking.
- Just-in-time OAuth: the person signs in as themselves, a short-lived credential is used for one decision, then it is gone.
- Each agent keeps its own identity, database, and secrets. Credentials from one agent cannot reach another.
- Connections are replaceable: a system's API today, its own agents and MCP endpoints as they appear, or an integration we build.
Example. A finance approver signs in to the ERP from the chat, approves one invoice, and the credential expires. The ERP's audit shows the approver.
- OracleHCM, ERP, Finance, CX
- WorkdayHR, finance, planning
- ServiceNowRequests, approvals, ITSM
- Your other systemsPayroll, scheduling, custom apps
Next step