AI that runs across every module, not next to one.
Generative answers grounded in your own graph. Agents that take action across Sales, projects, support, docs, and financials in one move. A model abstraction that never locks you to one vendor.
What AI does for you
Generative answers, grounded
Every entity exposes an `ai_context` serializer. Agents read the actual record, not a vector summary, when grounding matters.
Agentic actions
Agents create records, draft documents, send messages, and move work. Permissions and the JWT roleId scope what each agent can do.
Model abstraction
Anthropic Claude is the primary; OpenAI is the secondary. Add or swap providers in one place — callers never know which model answered.
Audited and reversible
Every agent action is logged and reversible. Customers see exactly what the AI did and why. No silent automation.
AI agents need context. Cyril gives them all of it.
An agent that can only see a CRM has thin context. An agent that can read Sales + projects + support + docs + financials in one query has the context to actually decide. Cyril’s graph is what makes the AI useful.
- Single auth model across modules
- `ai_context` on every entity — never just an embedding
- MCP server (`packages/mcp`) exposes tools to external agents too
Common AI questions
The model abstraction layer is designed for it. Adding a new provider is a single adapter file. At launch we ship Anthropic Claude as primary and OpenAI as secondary; self-hosted (Llama, Mistral) is on the roadmap.
Permissions and the JWT `roleId` scope every agent action. Risky actions require human approval. Every action is logged, auditable, and reversible. Customers see what the AI did and why.
Be one of the first to use Cyril.
Join the waitlist for early access. We'll only email you when there's something real to share.