Security & Trust
Your code is the product. We treat it that way.
Evonx works on real, production codebases — so control, isolation, and reviewability are not features. They are the foundation the platform is built on.
Changes ship as pull requests
Evonx never writes to your main branch on its own. Every change lands as a pull request you can read line by line, approve, or reject — and revert with standard Git tooling.
Isolated preview environments
Each live preview runs in its own isolated container with its own database, separated from other customers and from your production systems. Previews are torn down when you're done with them.
Access you control
Repository access is granted through your Git provider and scoped to your workspace. You can revoke it at any time — Evonx keeps working only for as long as you allow it to.
Encryption in transit
All traffic between your browser, Evonx, and your repositories is encrypted with TLS. Credentials for connected services are stored server-side, never exposed to the browser.
Nothing hidden in a black box
The plan, the generated code, the test results, and the preview are all visible before anything merges. You approve working software, not a summary of it.
Workspace-level separation
Your organization's projects, data, and generated code live in their own workspace, logically separated from every other customer's.
How a change flows through Evonx
When you describe a change, Evonx analyzes your codebase, produces a technical plan, and applies the change in an isolated working copy — never directly on your repository's main branch. The result runs in a live preview environment you can click through. Only when you approve does the change become a pull request in your repository, where your normal review process takes over.
Where your data lives
Application data created inside Evonx — your projects, threads, and previews — is stored per workspace. Preview environments get their own short-lived databases, separate from other previews and other customers. Your source code stays in your repositories; Evonx reads it to do its work and contributes back through pull requests.
Report a concern
Found a vulnerability or have a security question? Contact us at [email protected] and we'll get back to you quickly.