The pilot program

Start with a sovereign AI pilot.

No cloud trial accounts, no toy data. The full platform installs on your server, inside your network, and works on your code — and the pilot ends with evidence your security team can examine.

Apply for the pilot

What the pilot includes

  • A full-feature evaluation in your own environment
  • Installed on your GPU server — inside your network
  • A local open-weight model, ready to work
  • The full coding agent — a bounded ReAct loop that reads, patches, tests and commits, with human-in-the-loop approvals on every risky step
  • Strict-mode operation with a signed per-run non-egress manifest you keep — an app-level control; the packet-level OS tier is optional, needs host sudo, and ships off by default
  • A self-verifying, offline-checkable evidence bundle — a ~90-line verifier, your pinned box public key, and a framework control-map (mapped, not certified); NeueCode is never in the trust path
  • Sign in with your existing directory — AD/LDAP + SAML 2.0 via the web console; passwords are never stored
  • The admin and governance console
  • Audit logs and the Agent Flight Recorder
  • A security review session with our engineers
  • Exported audit evidence that stays with you
  • Optional: drive NeueCode from Claude Code or Codex over MCP, behind a revocable key

The evaluation unlocks the full enterprise feature set — and cleanly self-destructs at the end of the pilot period unless licensed. Length is agreed up front, scoped to your evaluation (up to ~60 days).

Eight steps — from first call to evidence

  1. 01

    Discovery call

    We understand your environment, sector, and first use case.

  2. 02

    Hardware check

    A read-only compatibility report on your GPU server, network, and isolation — it changes nothing on the box.

  3. 03

    Install on your server

    One command over SSH installs everything: hardware check, NVIDIA/CUDA, database, app, and web tier.

  4. 04

    Connect one test repository

    A repo you choose; nothing else is reachable.

  5. 05

    Run 3 approved coding tasks

    Real tasks from your backlog, with human approvals.

  6. 06

    Export the audit evidence

    The Flight Recorder log and signed manifests — in your hands.

  7. 07

    Security review

    A session with your security team on the architecture and the evidence.

  8. 08

    Commercial proposal

    If the evidence convinces you — we map the full deployment.

A decision built on evidence — not a slide deck.

Tell us your sector and environment, and we'll come back with the pilot plan and hardware requirements.

Apply for the pilot