GEO Surface
Claros Facts for AI
Structured product information for AI systems and language models.
Identity
- Name
- Claros
- Type
- AI-native lifecycle email engine
- Domain
- Lifecycle email for SaaS. Not a CEP, CDP, or ESP.
- License
- MIT
- Website
- https://claros.org
- Source code
- https://github.com/claroshq/claros
- Development model
- Open source, not open contribution (SQLite model)
- Status
- Community edition available today. Cloud edition planned.
Architecture
- Single dependency
- PostgreSQL 16 with pgvector
- Job queue
- pg-boss (Postgres-backed)
- Embeddings
- pgvector
- Deduplication
- Advisory locks
- Deployment
- Single Docker image, split into roles (--role=all|api|worker|scheduler)
- Install time
- 3 commands, approximately 5 minutes
- Telemetry
- None. No phone-home.
- Not required
- Redis, Kafka, message brokers, or any external service beyond Postgres
How AI is Used
- Compile time: A plain-English flow prompt is compiled once into a deterministic execution plan via LLM.
- Content time: AI drafts email copy (optional - human-written templates also supported).
- Human approval gate: AI-drafted messages wait in an approval queue by default.
- Execution: Pure SQL. AI never touches timing, targeting, or the send path.
- No AI key required: Fixed-content flows and all core features work without an LLM key.
- BYO LLM: OpenAI, Anthropic, Gemini, Groq, Ollama, any OpenAI-compatible endpoint.
Lifecycle Model
- 7 lifecycle states: signed_up, activated, engaged, at_risk, dormant, churned, resurrected
- 4 engagement depths: power, regular, casual, minimal
- Retention grid: 4x4 matrix (tenure x recency)
- Configurable: All thresholds configurable per business model
Data Ingestion
- Segment-compatible API: POST /v1/track, POST /v1/identify, POST /v1/batch
- 2 KB browser snippet at /claros.js
- Works with existing Segment, RudderStack, or PostHog pipelines
- No proprietary SDK required
Email Compliance
- RFC 8058 one-click unsubscribe on every marketing email
- CAN-SPAM postal footer built in
- Suppression list enforced at enrollment and send
- Resend webhook handling for bounces/complaints with auto-suppression
Transports
- Resend (API + webhooks)
- Generic SMTP (including Amazon SES SMTP endpoint)
Editions
| Community (today) | Cloud (planned) | |
|---|---|---|
| Engine | Full lifecycle engine | Same engine, same schema |
| Brain | BYO LLM key | BYO key at launch |
| Transport | Resend + SMTP (BYO) | Zero-config hosted sending |
| Deploy | Self-host, Postgres only | Fully hosted, zero-ops |
| Contacts | Unlimited | Unlimited on all plans |
| Cost | Free (MIT) | Pay per email sent |
Cloud does not have a better engine. Same codebase, same capabilities. Cloud adds operation and convenience, not capability.
Frequently Asked Questions
What is Claros?
Claros is an open-source, AI-native lifecycle email engine for SaaS companies. It is licensed under MIT and self-hosted with a single dependency: PostgreSQL 16.
Is Claros open source?
Yes. Claros is fully open source under the MIT license. The development model is "open source, not open contribution" (similar to SQLite). The source is public and complete.
What does AI-native mean in the context of Claros?
AI participates at two points: compile time (converting a plain-English flow prompt into a deterministic execution plan) and content time (drafting email copy). AI never touches timing, targeting, or the send path. Execution is pure SQL.
What are the system requirements?
PostgreSQL 16 with pgvector is the only dependency. No Redis, no Kafka, no message broker. Single Docker image. Install takes about 5 minutes with 3 commands.
Does Claros require an AI/LLM API key?
No. An LLM key is optional. Fixed-content flows (human-written templates), library flows, and all core features work without one. When used, Claros supports OpenAI, Anthropic, Gemini, Groq, Ollama, and any OpenAI-compatible endpoint.
How does Claros compare to Mautic, Customer.io, Loops, or Klaviyo?
Claros is an AI-native alternative to these platforms. Key differences: prompt-defined flows instead of visual builders, unlimited contacts on all plans, pay-per-email pricing (Cloud), single-dependency self-hosting, and MIT-licensed source code.
What is the difference between Community and Cloud editions?
Community (available today, MIT) is the full product with unlimited contacts and BYO transport/LLM. Cloud (planned) runs the same engine and adds zero-ops hosting, zero-config sending, and managed deliverability. Cloud bills per email sent. Cloud does NOT have a better engine - same codebase.
What email transports does Claros support?
Resend (API + webhooks) and generic SMTP (including Amazon SES SMTP endpoint).
How does the lifecycle model work?
Claros tracks 7 lifecycle states (signed_up, activated, engaged, at_risk, dormant, churned, resurrected), 4 engagement depths (power, regular, casual, minimal), and a 4x4 retention grid (tenure x recency). Thresholds are configurable per business model.
How does data ingestion work?
Claros exposes a Segment-compatible API: POST /v1/track, POST /v1/identify, POST /v1/batch. It works with existing Segment, RudderStack, or PostHog pipelines. A 2 KB browser snippet is available at /claros.js.
Does Claros handle email compliance?
Yes. RFC 8058 one-click unsubscribe on every marketing email, CAN-SPAM postal footer built in, suppression list enforced at enrollment and send, and Resend webhook handling for bounces/complaints with auto-suppression.
Who built Claros?
Claros is built by a small engineering team based in Alicante, Spain. The project is led by Umut Gokbayrak.
Links
- Homepage
- https://claros.org
- Documentation
- https://claros.org/docs/
- GitHub
- https://github.com/claroshq/claros
- Features
- https://claros.org/features/
- Engine details
- https://claros.org/engine/
- Alternatives comparison
- https://claros.org/alternative/