Skip to content

Security

Your code, your keys, your machine.By design.

Nexora is local-first. The engine runs beside your editor, talks only to the platforms you approve, and records everything it does so you can undo it.

Local engine on loopback

The Nexora engine runs on your machine and binds to 127.0.0.1 only. It is never exposed to your network.

Per-install access token

Every engine call except the health check requires a token generated for your installation and held by the IDE.

Bring your own keys

Model and platform keys are stored in your operating system's secret store through the editor — never in plain files.

Encrypted platform tokens

OAuth tokens for GitHub, Vercel and others are encrypted at rest. Without its encryption key the engine refuses to start.

Approval before side effects

Deploys, pull requests, payments and connected-platform calls wait for an explicit human yes. Approvals survive restarts.

Rollback and audit trail

Every live action is recorded on a timeline with its cost, and recorded actions can be rolled back.

Guarded terminal

Agent commands run in a visible terminal behind a denylist, under the run mode you choose.

Allowlisted MCP servers

Only approved commands can launch MCP servers, and vendor-hosted servers connect through their own sign-in.

Secrets stay out of logs

Keys and tokens are redacted from engine logs and never displayed back in the interface.

Data flow

Where your data goes.

Your code & project memory

Stays on your machine, under your user profile.

Model requests

Sent from your machine to the model provider you choose, with your key.

Platform actions

Sent directly to GitHub, Vercel, Stripe and others — only after you approve.

Nexora servers

None in the loop. This website only stores early-access requests.

Honest limits

What we don't do yet.

Trust comes from being specific. Here is what Nexora does not offer today.

  • Nexora is in private beta; the current build targets Windows.
  • Nexora does not yet hold third-party certifications such as SOC 2. We will not claim them until we do.
  • Rollback covers actions Nexora recorded; changes made outside Nexora are not tracked.
  • Workspace memory is keyword-based today, not a semantic index of your repository.

Responsible disclosure

Found a vulnerability?

We take every report seriously and will respond as quickly as we can. Please don't publish details before we've had a chance to fix the issue.

Report a security issue