Open and under control.

What your technical team will check

• Fair-code licence

  The core is under a fair-code licence of the Sustainable Use License type: free to use and modify for your company’s internal needs. Hosting or operating it for third parties requires a partner licence.

• Source code meant to be public

  The source code is meant to be published, so your team can read and check what runs. Publication is being prepared.

• Self-hosting or our cloud

  The same software either way: on your servers with Docker, free for internal use, or in our cloud hosted in Europe by OVHcloud, one dedicated instance per organisation.

• REST API and webhooks

  A REST API described in OpenAPI 3.1, with scoped keys: everything done in the app can be done from your code. HTTP requests reach any CRM or ERP that has an API.

• MCP server

  An MCP server gives Claude, Cursor or your own assistant the same tools as the built-in assistant, on behalf of a member and within the rights you grant.

• Your AI model

  OpenAI, Anthropic, Mistral, OpenRouter, any OpenAI-compatible API, or a local model with Ollama. Keys stay on your instance.

• Security

  Tokens encrypted at rest, a dedicated encryption key per cloud instance, a scope that limits what the AI reads, a log of every run.

• Reliable runs

  Each email processed once, automatic retries, error workflows, replay from the failed step without duplicates.

• Full documentation

  Concepts, every node, the API, self-hosting: the documentation is public, in English and in French.