A neutron star doesn't outshine the field — it out-binds it. neutron collapses a whole agent platform into one small, dense core, then holds N configured agents in orbit with gravity: roles, approval gates, and rules that never let power escape.
The physics is the architecture. Everything a neutron star does with mass, neutron does with configuration.
A star collapses into a core a few kilometres wide — matter at its densest.
The whole platform is a thin chrome around the Claude Agent SDK — a core small enough to read, dense enough to run everything.
Immense gravity holds the star together. Nothing escapes it.
Approval gates, roles, and non-escalation rules hold every agent. No tool call, no config change, no privilege moves without them.
One spinning core sweeps many beams across space.
One image, deployed once, presents as many branded agents — each with its own persona, tools, channels, and repos. All of it is data.
A neutron star is layered — each shell a different state of matter.
Three seams, independently swappable. Chat surfaces, the agent engine, and your capabilities plug in — they're never welded in.
Most agent stacks treat governance as a safety valve. neutron treats it as the point — the binding force that makes autonomous agents safe to hand real access.
Risky tools stop at a human card in the chat — command, cost, and blast radius spelled out before anything runs.
Approvals can require a role, and the requester never approves their own action. Approvers get a cross-thread inbox.
Agents can manage agents — create them, tool them, scope them — but can never grant more privilege than they hold.
Read-only by default, approval-gated in the middle, read-write when you mean it. Per instance, per tool.
Token-streamed answers, a live activity trace of every tool call, rich markdown, and per-turn cost — running on your infrastructure, against your data.
The web UI is one surface. @mention the bot in a GitLab or GitHub comment and it investigates and replies inline — same memory, same gates.
One conversation per merge request or issue, with full thread memory. Configure providers, allowlists, and write-only secrets entirely from Settings — no restart.
A container, a database URL, an auth token, and one config file. That is the whole install.