Skip to main content
NovaCore · the governed agent platform

Meet Nova, the enterprise‑ready AI engineer.

Assign it real work: a bug, an incident, the backlog. It comes back as a reviewed pull request, done on machines you own, under rules you set, with every action on the record.

evt 01 Why NovaCore

Other agents are built for the demo. Nova is built for the audit.

Approvals, agency limits and an append-only record of every action are not an enterprise tier bolted on later. They are the platform, and the reason a Nova pilot becomes a deployment.
evt 02 The difference

Why Nova, and not the others.

The gap is not the quality of the code. Most agents can write a good pull request in a demo; the gap is everything your organisation needs around it.

The work
Chat session Durable mission
Where it runs
Vendor cloud Your machines
Control
Prompt guardrails Enforced policy
The record
A transcript Append-only record
The AI
One bundled model Your AI accounts
evt 03 Staying in control

Nothing ships without you.

Anything that touches production arrives as a plain-English brief: what, why, blast radius, how to undo. Then it waits for a person, in the browser, on the pull request, or in Slack.

Waiting for you needs approval

Ship the fix for duplicate confirmation emails

What it wants to do
Ship a fix for duplicate order confirmation emails. 3 files changed.
Why
Ticket #2841. It reproduced the bug, wrote a test for it, and all 214 tests pass.
What it affects
The checkout service, in production. No spending involved.
How to undo it
Roll back to the previous release. It will watch error rates for 30 minutes after and undo it automatically if anything looks wrong.
Approve Reject Ask a question See the work
evt 04 How much rope

You decide how far it goes.

Five levels, set per team, per repository and per kind of work: tighter near production, looser for a dependency bump. A setting the platform enforces, not an instruction the model might ignore.

Agency level set per team · per repo · per kind of work
  1. L1 Watch only
  2. L2 Suggest
  3. L3 Draft it
  4. L4 Ask me first most teams
  5. L5 Go ahead
evt 05 Where it runs

Your code never leaves your network.

Nova works on machines you own, behind your own VPN. They reach out for work and nothing reaches in: no open ports, no vendor VPN account, nothing for your network team to sign off.

Runtime topology outbound-only below the line
Ingress & egress
GitHub Slack Jira webhooks egress

The only place external credentials live.

Control
mission kernel scheduler policy approvals API

Decides, records, schedules. Never executes.

Execution
engagement host your computers workspaces coding agents

Everything needing an environment runs on your hardware.

Substrate
event log read models memory knowledge artifacts

Row-level isolation, per-tenant encryption.

Outbound only

The machine is the boundary

Gone when you say so

evt 06 Fits your setup

Drops into the stack you already run.

Nova is a name your team already knows how to talk to: @nova in a Slack thread, an assignee in Jira, a reviewer on the pull request. The same agent, on the same mission, with the same record, in the tools you already use.

The AI underneath is your choice too, on your own accounts and at your own rates. When a better coding agent arrives, and one will, you switch it in settings rather than in a migration.

evt 07 The next entry is yours

See Nova run on your own code.

A working session rather than a slide deck. Bring a repository and a ticket you would otherwise assign to someone, and watch it go from the ticket to a pull request you approve.