Reinvent function by function
Each new application reuses the building blocks and controls you already approved.
The platform
Every RatioCore application, from an agent-run store to an agentic SOC, is built on the same core: how work comes in, the steps it follows, the knowledge and systems agents use, the limits they work within and the people who approve. Reinvent the next function on the same foundation, run it where you choose, and keep the freedom to change models and infrastructure.
RatioCore PlatformApp
Daily report for your agents.
Priya NairPlatform owner
Keeping the limit. It resets tomorrow.
What it gives your organization
Each new application reuses the building blocks and controls you already approved.
Access, budgets, approvals and records work the same in every function.
Every agent has a budget, tracked spending and an off switch.
Your infrastructure, your choice of models, your data in your own database.
Any channel, one set of controls
Whether a request arrives in Teams, Telegram, WhatsApp, another approved channel, an API or a system event, the same permissions, approvals and records apply.
RatioCore AssistantbotWhat is the approval limit for travel above 2,000 EUR?
15:10Trips above 2,000 EUR need the department head's approval before booking.
Source: Travel Policy v4, section 3.1
The total is 2,480 EUR. Shall I start the approval request?
15:11
RatioCore · IT accessBusiness accountI need access to the finance reporting system
10:02Sure. Which role do you need?
10:02Analyst
10:03Until when?
10:03End of quarter
10:03Request sent to your manager for approval. Access will expire on 31 December.
10:04Elena CostaService desk
RatioCore summarise today's open requests
RatioCore Service DeskApp
Here is today's summary.
Examples shown in WhatsApp, Telegram and Microsoft Teams. Each channel is enabled by your administrators and follows your policies.
The product in practice
Every RatioCore application is assembled from the same parts. Each part has a clear job, and all of them run under the same access, approval and audit controls.
Guide people through what the agent needs to know. Use structured intake for work that starts from messaging, a business system or an API.
Set the sequence, branches and approval steps in the visual workflow builder. Use fixed rules for predictable work and agent judgment where context matters.
Retrieve from enterprise documents and records with vector and lexical search. Add knowledge graph relationships where the workflow calls for them.
Define which tools agents can use and which actions require approval. Extend workflows with integrations, APIs and MCP tools.
Tenant and role permissions limit access. Sensitive actions route to the people responsible, and authorization is rechecked before execution.
Use a shared agent catalog, release controls and operational views. Inspect runs, decisions and external effects as your fleet grows.
Governance in practice
RatioCore enforces authority when an agent tries to act, not only in a report afterwards. Every protected action passes three checkpoints.
Tenant-scoped identity, role permissions and versioned policies establish who can use a tool and when approval is required. Missing authority blocks dispatch.
Approval is specific to the intended action. The runtime rechecks permissions just before dispatch, then records the action and its outcome.
Follow policy decisions, approvals, tool calls and outcomes in context. Reconcile any uncertain external result before retrying it. Use release controls to manage changes across teams.
Flexibility in practice
Use rules where work is predictable and agents where it needs judgment. Then choose how knowledge, systems and models fit each workflow.
Keep predictable steps in a visual workflow. Add agents where context or judgment is needed, and keep a person in charge of the decision.
Bring in knowledge through vector and lexical retrieval, or use graph context when the relationships between records matter.
Connect approved systems through channel adapters, APIs and MCP tools. Each connection adds a data path to review before you enable it.
Different workflows can use different model routes. Models can reason and draft, but they never gain authority to execute actions.
Run it like production
Know what every agent spends, and stop it when you need to.
Built so that a restart or a busy GPU does not lose work.
From one function to the whole company
Commerce, security, procurement and maintenance need different agents and rules. Each application keeps its own tools, roles and limits, while sharing one platform for approvals, releases and audit records. That is how a company moves from one agent-run function to many.
Positioning
The Core
Every organization that puts agents into production has to answer the same six questions. RatioCore answers them in the Core, so each new agent inherits the answers instead of rebuilding them.
Tenants, identities, groups and grants. Every agent gets its own service identity, and every authorization decision is logged.
Versioned policies and declared tool risk (read, write, destructive) decide. Risky actions wait in an approval queue.
An audit trail, turn traces and tool events show what each agent did, step by step.
Tokens are metered per agent per day, with daily budgets and quotas.
Durable admission and delivery, leases and backup checkpoints keep work recoverable.
Named principals, separation of duties and decision logs keep ownership clear.
For architects · in the product
Every effect, receipt and journal entry commits in one fenced transaction.
Destructive steps get an approval bound to the specific run, step and input, with an expiry.
Published workflows and dialogs cannot change; each run snapshots the definition and its hash.
Deny beats approval beats allow, and every policy can be simulated before activation.
Dialog respond steps return a fixed answer with no model call at all.
Removing a dialog's binding from an agent switches that dialog off immediately.
For architects · design stance
Admission, identity, the execution gate, tool bindings and approvals refuse when in doubt.
Memory, grounding and catalog overlays degrade gracefully instead of blocking a turn.
Nothing is shown to a user that has not first been stored.
Applied alike to workflows, dialogs and agent profiles.
Proof of value
A good evaluation tests both what the business needs and what the platform promises, in an environment like yours.
FAQ
Still deciding? Bring your questions to a walkthrough.
A workflow sets the sequence, branches and approval steps. Fixed rules handle predictable routing. Agents handle steps that need context or judgment, such as gathering evidence or recommending a next step. Policy and role permissions govern what either can run.
Versioned policies and role permissions define when approval is required. Sensitive actions wait for a named approver. Approval is tied to the specific intended action and rechecked just before dispatch. If the required authority is missing, the tool call is blocked.
Yes. Agents retrieve from enterprise documents and records with vector and lexical search, and can use knowledge graph relationships where the workflow calls for them. The evidence is attached to the agent's proposal, so reviewers can check it before they decide.
Use the shared agent catalog, release controls and operational views. Operators can inspect runs, decisions, tool calls and external effects. If an external change has an uncertain outcome, it must be reconciled before anyone retries it.
Neither. RatioCore is a platform for running business functions with agents. It sits between your models and your business systems, runs agents, workflows and dialogs, and decides what they are allowed to do. You bring the models you approve, and you can change them later.
See it on your business
Bring a process your team runs today. In a demo we show how agents could run it, where your people stay in charge, and what a focused pilot could prove.