HEADLESS AGENTIC CRM

A CRM you never
have to open.

State comes in through connectors. Agents react. Records write themselves. Caelion is the CRM as an API, and the screen is optional: when you want one, it talks back like an assistant, not a dashboard.

Get early access See how it runs

In development. Everything on this site describes the system being built.

caelion · Acme Industrialheadless · console attached
  1. catalystStripe

    A subscription invoice just got paid. 48,000, right on time.

    event: invoice.paid
subscription: sub_9K2f
amount: 48000
customer: cus_AcmeInd
  2. foundryreading the payment

    That payment is Acme Industrial's. Their Q4 renewal is won and closed today, and the promise to renew by October 15 is kept.

  3. reactionyour seller agent

    I wrote Priya Natarajan a thank-you, mentioned the Houston plant coming online, and suggested a check-in the week of November 3. It is ready when you are.

THE IDEA

Your CRM is an API.
Everything else is a client.

Dashboard CRMs are a database with a screen in front of it, and every fact inside was typed by someone who would rather have been selling. Caelion removes the screen from the critical path. Signal arrives, gets forged into records, and agents act on the result. A human is in the loop exactly where you put one.

That is why Caelion ships headless first. The console exists, and it is good. But if the product only worked with the console open, it would be another dashboard. It works with nothing open at all.

THREE NOUNS

Catalysts change state. Foundries forge records. Reactions act.

That is the whole model. Learn three words and you understand every part of Caelion.

  1. 01

    Catalyst

    Anything that changes state.

    A webhook. A YAML file dropped in a watched folder. A JSON document published to the API. A semantic search that suddenly matches. A calendar invite, a transcript, a paid invoice. If it carries signal, it is a catalyst, and Caelion treats every one of them the same way: state changed, agents wake up.

  2. 02

    Foundry

    Where raw signal becomes CRM state.

    A foundry is a typed pipeline you declare, not a form you fill in. It takes whatever a catalyst brought, resolves it against what Caelion already knows, and forges records: accounts, people, deals, commitments, documents. Matching, enrichment, deduplication and history all happen here, on every signal, without anyone typing.

  3. 03

    Reaction

    What agents do when the state moves.

    Reactions are the agents. They subscribe to state, not to a screen. A deal goes quiet: an agent researches the account and drafts the nudge. A commitment lands: an agent books the follow-up. A record contradicts a source: an agent flags it and asks you. Every reaction publishes back out through the same connectors that fed it, so the loop closes without a human in the middle unless you want one there.

The full model, with the YAML

CONNECTORS

Anything in. Anything out.
No marketplace required.

Anything that can emit or accept state is a connector. The list below is where we started, not where it stops.

Signal in

  • Webhooks
  • YAML and JSON files
  • API publish
  • Semantic search
  • Email and calendar
  • Meeting transcripts
  • Forms and chat
  • Databases

Action out

  • Email send
  • Slack and Teams
  • Webhooks out
  • Documents
  • Task systems
  • Billing

Both ways

  • MCP
  • REST and GraphQL
  • Warehouse sync
  • Other CRMs
  • Files
  • Your code

Every connector, with what it does

VERSUS

Dashboard CRMs added agents. Caelion started from them.

Lightfield, Attio, HubSpot and the rest ship a screen first and bolt agents onto it. Caelion is the other way round: the agents and the state are the product, and a screen is one of several clients you may or may not want.

Dashboard CRMsCaelion
Where the truth livesIn a database behind a UI. Agents get an API to it.In a state ledger. Agents subscribe to it directly. The UI reads the same ledger you do.
How data gets inPeople type. Some integrations sync fields.Catalysts. Files, webhooks, searches, transcripts, publishes. Typing is allowed but never required.
What “automation” meansRules: if field X changes, do Y.Reactions: agents with judgment, subscribed to state, publishing back through connectors.

The full comparison

THE OPTIONAL SCREEN

When you want a screen, it talks back.

The console is optional, and it does not look like a CRM. It looks like the assistants you already use: one conversation, the state of your business behind it, and every answer backed by a record you can open.

See the console
caelion · Acme Industrialheadless · console attached
  1. catalystStripe

    A subscription invoice just got paid. 48,000, right on time.

  2. foundryreading the payment

    That payment is Acme Industrial's. Their Q4 renewal is won and closed today, and the promise to renew by October 15 is kept.

  3. reactionyour seller agent

    I wrote Priya Natarajan a thank-you, mentioned the Houston plant coming online, and suggested a check-in the week of November 3. It is ready when you are.

DEVELOPERS

The API is the product. Start there.

Everything the console can do, the API can do, because the console is just a client. Publish state, declare foundries and reactions in YAML, subscribe to changes, and read the whole model back.

API surface and examples 
curl -X POST https://api.caelion.app/v1/publish \
  -H "Authorization: Bearer $CAELION_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "kind": "meeting.transcript",
    "account_hint": "acme-industrial.com",
    "body": "..."
  }'

EARLY ACCESS

Build it with us.

Caelion is in development and taking early-access teams now. The best partners are the ones already annoyed at typing into a CRM.

Get early access Read the API first