Anela

Trust & Security

The promises we run on, in plain language. Last updated September 15, 2026.

Your code is yours

Everything you build on Anela belongs to you. Download your full project as a zip at any time, sync it two-way with your own GitHub repository, and take it anywhere: it is a standard web project. A site that keeps data with us takes its database structure along, not the rows, and connects to a database of your own. There is no lock-in, and keeping it that way is a promise, not an accident.

How we protect your work

Every project runs isolated from every other project. Secrets (API keys, integration credentials) are stored encrypted, and we mask them in logs and in the history we keep. To be clear about the limit: the secrets you add to a project are placed in the environment the AI builder works in, because that is what lets your app actually reach your payment provider, your email sender, or your database. Assume any key you paste can be read by the agent building that project, and use keys you can rotate. Your prompts, your projects, and your secrets are never used to train models. Billing is prepaid credits: a build that runs out of them stops, so there is no such thing as a surprise bill.

Reliability

Current availability of the app, builds, and published sites, plus honest incident history, lives on the status page . Published sites are served from a global edge network independent of the build platform, so your live site stays up even if the builder has a bad day.

Certifications

We are not yet SOC 2 or ISO 27001 certified: those audits are on our roadmap as the company grows, and we build to their standards today (access control, encryption in transit and at rest, tenant isolation, limited internal access). If your organization needs a security questionnaire answered in the meantime, email us and a human will do it.

Questions

Write to [email protected] . Security reports get priority handling.