Integrations Roles What they do How it works Control Cloud Book a walkthrough
Clovar Cloud — now onboarding early-access businesses

The operating system for your AI workforce

Not a chatbot. A team of AI coworkers that work inside your ERP, your inbox and your spreadsheets, finish the job, and hand back the file — under rules you set, with a record you can show anyone.

Book a walkthrough Watch a morning's work
Live Tuesday · Operations 08:02
Team
Operations Coordinator manager
Inbox Assistant reads the shared mailbox
Procurement Buyer prices parts against the ERP
Finance Reviewer checks anything that costs money
You approve what matters
Task
Fill cost & lead time — Stocking Levels 6.1.xlsx
from customer email · 1,984 rows · 5 empty columns
  1. Received
  2. Looked up in ERP
  3. Columns filled
  4. Approved by you
  5. Delivered
Cost so far $0.00
Activity

    A simulated morning, using the platform's real tools. Every line is something Clovar agents do today.

    158
    Actions agents can take
    20+
    Systems they plug into
    13
    Ready-made roles
    6
    Levels of trust
    24/7
    Always working
    Integrations

    Works with what you already run

    An AI coworker is only useful if it can reach your real data. Clovar agents read and act inside the systems your business already depends on — no migration, no rip and replace.

    HubSpot Salesforce QuickBooks Slack Microsoft Teams Microsoft 365 Gmail LinkedIn Meta X Google Ads Calendly Buffer Metricool PostgreSQL SQL Server MySQL Any MCP server Any OpenAPI spec

    Your ERP, live

    Agents query part data, pricing, stock and purchase history straight from your ERP through the Model Context Protocol. They answer with your numbers, not guesses.

    Your inbox, both directions

    Gmail and Microsoft 365 with real-time push. Agents triage, draft, attach and send — and anything going out can wait for your approval first.

    Anything with an API

    Paste in an OpenAPI spec and Clovar builds the connector. Every connector runs isolated, code-signed, with its permissions reviewed — new integrations don't mean new blind spots.

    Ready-made roles

    Hire a role, not a chatbot

    Every role ships with the job description, the tools, the operating rules and the escalation path already wired. Pick one to see how its day goes.

    Also in the box: Support Escalation, Executive Briefing, Security Analyst, and five ingester roles that live on supplier feeds — price updates, datasheets, end-of-life notices, last-time-buy warnings and lifecycle bulletins. Or write your own: a role is just a persona, a toolset and a contract.

    Work that lands in real files

    Most AI tools give you text in a chat window and leave the job to you. Clovar agents finish it — and hand back the spreadsheet, the document or the report you were going to build.

    • Spreadsheets, filled. Two thousand rows looked up in your ERP and written back in one operation, anchored row by row so a value never lands on the wrong line.
    • Documents, written. Formatted Word reports with headings, tables and images, generated from live data.
    • Anything, read. PDFs, CSVs, scans and images — the datasheet, the invoice, the photo of the label.
    • Delivered where it's used. Files attach to the task, the case or the email that needed them, and pass between agents on their own.
    Stocking Levels 6.1.xlsx · Sheet1
    PartRevQtyUnit costLead timeLast sale
    46PN-20481C120$14.2012 d2026-07-30
    47PN-20482A40$3.855 d2026-08-11
    48PN-20490B600$0.9221 d2026-08-14
    49PN-2051115$212.0035 d2026-05-02
    50PN-20517D250$7.409 d2026-08-20
    51PN-20530A80$28.1514 d2026-08-26
    enrich-workbook 1,984 rows · 9,870 cells written · 0 errors
    What they do

    Everything a team needs to think, act and collaborate

    Clovar agents are not prompts in a loop. They remember, they own work across days, they hand off to each other, and they get better at the job.

    They show up on their own

    Agents run on a schedule, react to an event, or answer when spoken to. Work happens overnight without anyone prompting it.

    They work as a team

    Managers and direct reports. They delegate down, escalate up, brief their peers, and borrow a specialist from another department when a job needs one. Put several in one room with you and steer.

    They remember

    Facts and relationships persist in a knowledge graph; the relevant history is found by meaning, not keyword. Tuesday's agent knows what Monday's learned.

    They own the work

    Tasks carry dependencies, priorities and locks so two agents never fight over one job. Cases stay open across days, wake when a reply lands, and close when they're actually resolved.

    They show you the plan first

    For bigger jobs an agent lays out what it intends to do before it does any of it. Read it, change it, approve it — then watch it execute exactly that. When it's stuck, it asks.

    They get better, inside a budget

    Lessons from their own work are promoted into how they operate; A/B test two variants and keep the winner. Spend is tracked per agent against live rates, with a ceiling that stops work rather than surprising you.

    How it works

    From trigger to finished work

    Every turn follows the same seven steps — which is why it can be governed at every one of them.

    01

    Something kicks it off

    A schedule fires, an email lands, a workflow reaches its turn, a colleague delegates — or someone simply asks.

    02

    It gathers the context

    Memory, knowledge, open tasks and unread briefings come together into one picture, so the agent starts informed.

    03

    It decides what to do

    The model works through the job in the agent's role and persona — planning the steps, not answering a single question.

    04

    It takes action

    Every tool call is checked against what that agent is allowed to touch before it runs. Records, files and external systems update for real.

    05

    Your rules apply

    Anything with a consequence is weighed by risk, cost and how much trust this agent has earned. It proceeds, waits for approval, or is refused.

    06

    A human signs off

    High-stakes actions queue with the evidence and the reasoning attached. Approve, reject, edit the draft, or ask for more.

    07

    It remembers what happened

    Facts land in the knowledge graph. The conversation is summarised with the entities that mattered — so the next agent starts ahead.

    Trust & control

    Full control without slowing agents down

    Most teams won't let AI near anything that matters because they can't predict or prove what it did. Clovar is built the other way round: agents earn scope, every consequential action is weighed against your rules, and all of it is on the record.

    A written job description, enforced

    Each agent works under a versioned contract: its role, the systems it may touch, what it must never do, the evidence it has to produce, and what it may spend. Contracts move through draft, staging, certified and production, and become immutable once published — changing the rules means a new version and a new sign-off.

    Trust is earned

    Agents graduate by proving themselves, one level at a time.

    1. Observe only
    2. Draft only
    3. Recommend only
    4. Approval required
    5. Policy-bound autonomy
    6. Emergency stop

    Ask it why, get a real answer

    Every approved or rejected action carries a structured account: what triggered it, how the agent reasoned, which policy applied, what else it considered, and what actually happened. When someone asks why an agent did something six weeks ago, you have the answer rather than a log line.

    Rehearse before you go live

    Run an agent in simulation to see what it would have done. Certification suites test a contract before production, and past runs replay as regression tests.

    Nothing leaves unrecorded

    Every action that touches the outside world is written to a ledger before it happens. Secrets are referenced by name, never seen. One stop control halts everything an agent has in flight.

    Proof it's working

    Resolution rate, approval rate, value delivered and a health score — so whether this is paying off has a number attached.

    Built on .NET 8 · PostgreSQL · Qdrant · Redis · Claude, OpenAI & Azure AI · Model Context Protocol A conventional stack your IT and security teams can audit. Isolated tenant per business, encrypted secrets, and graceful fallbacks when a dependency has a bad day.
    In practice

    What this looks like on a normal Tuesday

    The 2,000-row spreadsheet
    A customer sends a stocking-level workbook with half the columns empty. An agent reads it, looks up every part in the ERP for cost, lead time and last sale, fills the columns, and emails the finished file back — a job that used to cost someone two days.
    The inbox that handles itself
    Mail is triaged in seconds. Routine questions are answered from your own documentation, quotes are drafted with live pricing, and anything unusual reaches a person with the full thread and the reasoning attached.
    Buying under control
    A buyer agent watches demand, prices against live ERP data and prepares the request. Anything over your threshold waits for a human — with the numbers, the alternatives and the reasoning already laid out.

    Fully managed. Ready when you are.

    We host it, run it, secure it and keep it current. You bring the work. Clovar Cloud is onboarding a limited number of businesses — tell us about yours.