About
Why we built Claros.
Open source, not open contribution.
Story
We built it because we needed it.
We built Claros because we ran lifecycle email for our own SaaS. We started on Mautic, outgrew the maintenance burden, and refused platforms that tax contact count instead of emails sent. So we wrote the engine we wanted: prompt-defined flows, deterministic execution on Postgres, our own LLM key, and human approval before anything sends. Now we are opening it up.
Development model
Open source, not open contribution
The source is MIT licensed and complete. Bug reports and issues are welcome. Design and roadmap decisions stay with the core team, similar to SQLite. We do this so the engine remains coherent as it grows.
This means the engine you read today is the engine that will run in production. There is no enterprise fork, no commercial extensions, and no features held back for a paid tier. Community edition is a full product, not a demo.
Built in Alicante, made for the world.
We work from the Costa Blanca, the same sunlit stretch of the Spanish Mediterranean that has drawn builders and traders for centuries.
A focused, engineering-led team, shipping daily. When you write to us, a person who builds the product writes back.
Cloud
What comes after self-hosting
A Cloud edition is planned. It will run the same engine and schema, add zero-ops hosting and managed sending, and bill per email sent. It will not have a better engine. The open-source engine is the source of truth.
Cloud adds operation and convenience, not capability. Same lifecycle model, same Brain, same Postgres-backed queue. The only differences are that you do not have to run a server and we handle deliverability infrastructure.
Start with the engine we actually run.
Install Claros in about five minutes. No AI key required to start.