Build faster.
Model the business once and build on it. Applications, developers and coding agents start from entities, decisions and permitted actions that already exist, instead of rebuilding them each time.
Turn your business into infrastructure
The Composable Business Runtime for AI.
Turn how your business works into trusted, reusable building blocks for applications and AI. Build faster, operate reliably and put AI to work without giving up control.
Build faster.Run deterministically.Reuse everywhere.
Why Archiveris
Run deterministically.
The same inputs give the same result, with the reasons behind it. Business definitions are compiled, tested and versioned, so consequential work does not depend on a model's mood.
Reuse everywhere.
Define it once, then use it everywhere. The same governed building blocks serve your applications, your workflow and BPM tools, your agents over MCP, and whatever you build next.
What are you trying to accomplish?
The same runtime, read four ways. Start where your problem is.
Modernise applications
Build on reusable business definitions instead of rebuilding data, logic and permissions into every application.
Application modernisation Deploy trustworthy AI and agentsGive AI governed facts, deterministic decisions and bounded actions, instead of asking it to reason about everything.
Trustworthy AI Strengthen risk and complianceTurn policy, regulation and authority into executable controls that produce evidence and traceability as they run.
Risk and compliance Automate business operationsAdd governed operations to the workflow tools, BPM suites, applications and agents you already run.
Business automation
Kebiki
Decision infrastructure
Some things shouldn't be left to AI judgment.
Turn policies, contracts and regulations into tested, versioned decision APIs. Every result is deterministic, explainable and traceable to the sentence it came from.
EligibilityClassificationCalculationRoutingComplianceApproval
Can this patient receive an MRI?
clinical_eligibility v2.1 · production
Input
PatientPlanProcedure
Eligible
- Clinical criteria satisfied
- Plan covers the procedure
- Prior authorisation requirements met
Illustrative decision.
Business Operations
Compose the operations your business runs on.
A Business Operation is a published, deterministic function composed from the building blocks the job requires. It may make a single decision, or combine business context, policy logic and permitted actions behind one stable contract.
Applications, agents and workflows call the operation without needing to understand how its business logic is assembled.
- No fixed template
- Deterministic at runtime
- Typed, versioned and traceable
Different operations. Different compositions.
Use the primitives the job needs, and no more.
What tax applies here?Calculation
Inputtransaction, jurisdiction
KebikiTax determinationTax amountrate, basis and the rule applied
Assess a claimMulti-step composition
Inputclaim, actor
JiwariGet claim contextKebikiCoverage and settlement
TebanPermitted actionsClaim assessmentoutcome and next actions
Route an applicationClassification
Inputapplication
KebikiClassification logicQueue assignmentqueue and reason
Illustrative compositions.
The boundary
Archiveris composes. Your tools orchestrate.
A business process runs for days and waits on people. An operation runs to completion in milliseconds. Those are different jobs, and we only do one of them.
Keep the workflow engine, the BPM suite or the agent framework you already use. When something consequential has to happen according to the rules of your business, it calls an Archiveris operation and gets a governed outcome back.
Jiwari knows.
Kebiki decides.
Teban permits.
Archiveris composes.
Your tools orchestrate.
Your toolsOrchestration stays yours
ApplicationsAgentsWorkflowBPM
call governed operations over REST, MCP and SDKs
Business OperationsArchiveris composes
Assess claimDetermine settlementApprove claim
composed from
The building blocksUsed alone, or together
Jiwari · what is true
Kebiki · what follows
Teban · what may happen
Three building blocks. Composed for the job.
Jiwari models what is true. Kebiki determines what follows. Teban defines what may happen. Use them on their own, or compose them into Business Operations.
Jiwari
Business world infrastructureModel what is true.
Capture your business — its entities, relationships, state and context — and give AI and applications one governed view of what is true.
Entities and relationshipsGoverned schemasAPI and MCP
Explore Jiwari
Kebiki
Decision infrastructureDetermine what follows.
Turn policies, contracts and regulations into tested, versioned decision APIs that return consistent results with traceable reasons.
Policy compilationScenario testingDecision traces
Explore Kebiki
Teban
Business affordancesDefine what may happen.
Determine which actions are permitted for an actor in the current situation, including the conditions, limits, authority and evidence required.
Permitted actionsAuthority and limitsEvidence requirements
Explore TebanAdoption
Use what you need. Compose when you need more.
Each product solves a problem on its own. Nothing here requires you to adopt an architecture before you get value from a decision.
Kebiki alone
Make consequential business decisions deterministic, explainable and testable.
Jiwari + Kebiki
Resolve authoritative business context, then decide against it, so every caller evaluates the same facts.
Kebiki + Teban
Turn determinations into governed possibilities: what this actor may now do, and under what limits.
All three
Compose complete Business Operations for applications, agents and workflows to invoke as one call.
Where operations run
One runtime. Across the business.
The same three building blocks, composed into whatever each domain runs on: the context it works from, the determinations it makes and the actions it permits.
Healthcare
- Patient context
- Eligibility
- Care authorisation
Financial services
- Customer context
- Credit decisions
- Payment authority
Insurance
- Claim context
- Coverage and settlement
- Permitted actions
Travel and expenses
- Employee context
- Policy decisions
- Payment authority
The public sector
- Case context
- Benefit eligibility
- Case actions
Illustrative compositions, not a list of deployments.
Inspectable
Know exactly what your business is running on.
Every Business Operation is assembled from explicit, versioned business assets. Inspect the context it resolved, the determinations it made, the actions it permitted and the versions that produced the outcome.
Business OperationAssess claim
Jiwari
Where did the facts come from?
The records the operation read, the schema that governed them and the version in force when it ran.
Claim model v8 · Policy model v4
Kebiki
Why was this determined?
The rule that fired, the requirement it implements and the passage in the source document behind it.
Coverage and settlement v7.2
Teban
Why was this permitted?
The authority the actor held, the conditions that applied and the evidence the action required.
Claim actions v2.8
Archiveris
How was it composed?
Which building blocks ran, in what order, at which versions, and what the operation returned under its published contract.
Assess claim v3
An illustrative composition.
See an operation runThe compound effect
Define once. Compose repeatedly.
Nothing you define here belongs to the application that needed it first. Each governed building block is available to everything you build afterwards.
A customer model
Modelled for a claims operation, it also serves servicing, underwriting and fraud, without being rebuilt in each one.
An eligibility decision
Called by an agent today and by a web application tomorrow, returning the same determination to both.
An action model
One account of what each actor may do, governing every surface that asks, from the portal to the workflow engine.
Your business definitions stop belonging to individual applications. They become infrastructure.
What do you want to build or automate next?
Bring us a use case. We will show you where Archiveris can provide the foundation.