A mine, a hospital, a fleet, a two-person shop. Rhetra reconciles your systems into one typed model of what you actually run, then gives every workflow, application and agent the same governed way to change it.
Batch syncs, live streams, file drops and agent writes, read continuously and typed on the way in.
Ingested records become typed objects. Customers, orders, invoices and sensors, each carrying properties, real relationships to one another, and the actions that are allowed to change them.
The schema is defined at runtime. Add a property or link two types and every record follows within the hour, without a migration.
Every change is recorded on two time axes. Ask what was true last quarter, or what you believed last quarter. Both are answerable.
The model carries the levers that move the operation. Logic is written against the objects you defined, in server-side TypeScript, with a client generated from your ontology: objectSet(), traversal, aggregation, all typed.
Rename a property and the function that uses it fails to compile. The ontology is the contract.
Logic chains mix LLM calls with conditionals and loops. Every chain ships with an eval suite, so a prompt change reports a pass rate before it reaches production.
Functions compute. They don’t commit. When logic needs to change something it calls an action, and inherits its rules.
Functions read the ontology freely. Every write routes through an action, and its criteria.
Every write goes through an action with submission criteria, so the rules live on the type rather than in someone’s head. Workflows chain actions into processes, automations watch the data and react, and decisions write back to the ontology and out to the source systems the records came from.
The only write path. Submission criteria decide who can change what, enforced on dispatch. Same rules for a person, a workflow, or an AI agent.
Multi-step processes with branching, waits, and checkpoints. A checkpoint pauses the run until a reviewer approves in the Inbox.
React to the data itself: entity created, entity updated, or a schedule. Conditions, retries, and cooldowns keep reactions deliberate.
One command generates a fully typed TypeScript client from your ontology. Build real apps on it. The platform hosts them, wired to the same actions and permissions as everything else.
Workshop builds operational UIs without writing code. Tables, detail views, investigation graphs, action forms.
Rhetra speaks MCP. Point Claude, or any MCP client, at a workspace and it receives the full toolset: search, traverse, aggregate, run pipelines, trigger actions. An agent gets the same toolset an operator gets, and the same limits on what it can commit.
A live MCP session. Reads run free, writes route through an action, ontology edits become proposals.
rhetra-sdk mcp connects any MCP client to your workspaces with a personal token.
Every registered app can expose its slice of the ontology as a hosted MCP server. The tools are generated from your types and actions, not hand-written.
Agent writes go through actions and their submission criteria. Ontology edits land as proposals you approve in the Inbox. The rules apply to an agent exactly as they apply to a person.
Based in Sweden. Available remotely.