Security

Built for security teams before developers.

Most AI tools are designed to delight developers, then argued past security. NeueCode is built the other way around: an architecture your security team can diagram and verify — that developers then get to enjoy.

In hybrid and open modes, you decide what crosses the boundary — and every crossing is recorded and signed.

No required vendor cloud

The agent, models, memory, and audit all run on your servers. No core path depends on an external service.

Deny-by-default egress broker

Every outbound call passes a broker that blocks anything not explicitly allowed and signs a per-run manifest. In strict mode, egress is locked off entirely.

Human approval where it matters

Plan mode shows the steps before work starts, code changes ship as reviewable diffs, and risky commands wait for human sign-off.

Identity & least privilege

SSO via Active Directory / LDAP and SAML 2.0 with any IdP — Okta, Entra, ADFS, Ping, Keycloak, Google — with group-to-role mapping; passwords are never stored. Capability tokens cryptographically gate every privileged client action, with least-privilege checks on every tool call and fail-closed policy.

Prompt-injection defenses

Defense against instructions injected through external content, poisoning-resistant memory, and a deterministic verifier that checks claims against what tools actually returned.

Secrets stay secret

Secret scanning to keep credentials from leaking, plus an admin-managed settings vault: keys entered once, write-only, and masked.

Tamper-evident audit trail

Every step, tool call, and approval lands in the Agent Flight Recorder — a hash chain any later edit breaks, with offline verifier tools the auditor runs themselves.

Air-gapped deployment

A repeatable install that doesn't phone home, offline license validation, and internet-reaching apps auto-locked in strict mode.

Proof, not assurances

In strict mode, every run emits signed manifests plus a signed, integrity-tiered non-egress attestation — proof that nothing left the network, independently verifiable.

Built for regulated environments. Auditable like it.

“Verify it yourself” beats “trust our badge.”

Blocks outbound traffic by default

A deny-by-default egress broker stops anything not explicitly allowed — in strict mode, cloud egress is locked off entirely.

Signs a manifest of every run

Each session emits a signed record of what was reachable and what left — if anything left at all.

Records every action in a tamper-evident chain

The Flight Recorder hash-chains every step, tool call, and approval — any later edit breaks the chain.

Verifiable by your auditors — offline

Verifier tools the auditor runs themselves; neither we nor your operators sit in the trust path.

Compliance evidence export mapped to EU AI Act Articles 12 & 14, DORA, NIS2, SOC 2 CC6 controls, ISO 42001, and SAMA/NCA.

NeueCode is not certified against these frameworks — we give you the evidence to make your case.

Documents for your review

Sent to your work email on request.

Security Architecture Brief

Data flow, trust boundaries, and the governance model — for your security team's review.

Request it

Air-Gapped Deployment Checklist

What it takes to install and operate the platform with no internet path at all.

Request it

Audit Evidence Sample

A sample of the Flight Recorder log and signed manifests as an auditor sees them.

Request it

Put your security team in front of our architecture.

A direct technical session with the team that built the platform — bring your hardest questions.

Talk to our security team