How Echidna is built, in the open.

Transparency is part of the manifesto: here are the map, the isolation, the life cycle of your data and the journey of a question. No trade secrets, no unnecessary jargon.

1. The service map

The public site lives on Cloudflare. The product (your account, your space and the engine) lives on our servers. The model providers are behind a router of our own; web search goes out over a private network between servers.

FIG. 01 · SERVICE MAP

2. Isolation: your space and no one else's

Every person works inside their own container, with memory and CPU limits. There is no shared folder and no door between spaces: isolation does not depend on a password, it is the architecture itself.

FIG. 02 · ISOLATION BETWEEN SPACES

3. The life cycle of your data

What you write and attach exists to serve you the answer. Afterward, each thing follows its own path: attachments purge themselves, your conversations live in your space until you decide, and the account and plan are kept so we can charge and invoice.

FIG. 03 · DATA LIFE CYCLE

4. The journey of a question

Your request leaves your space, passes through the router with your private key, reaches a model provider and comes back turned into an answer. If the answer is on the web, the search goes out over our private network and comes back with cited sources.

FIG. 04 · JOURNEY OF A QUESTION

What we do not publish (and why)

Here is everything needed to understand and trust: the map, the isolation, the data life cycle and the journey of your question. We do not publish internal addresses, ports, versions or exact configurations, because that information helps those who seek to attack us, not those who want to understand. It is the same reason a bank shows you the cameras and not the vault's floor plan.

If you are interested in the security detail, continue to Security; if you want the story and the reasons, continue to the Manifesto.