Introduction

Hardalion Nexus is where teams build and run production AI agents.

If Nexus says no, the action does not happen. Before a tool call or a write leaves, Nexus decides. Allow, stop, or a person. Then it writes the record.

Nexus is not an LLM. Your model can still propose. The gate decides whether the action may leave.

What Nexus does

Beat	What happens
Check	Every consequential action is decided before it leaves. Allow, or stop.
Person	When it matters, a person sits on the path. The action waits.
Record	The decision is written. You can export it. You can prove it.

How the gate is built

Developers integrate against these surfaces:

Surface	Role
Agent identity	Who is allowed to act
Gateway	Inspection of tool calls and writes before they leave
Audit trail	Append-only record of each decision
Shadow mode	Watch the gate on live traffic before you enforce

Same input, same decision: allow, stop, or a person.

Request flow

flowchart LR
  A[Agent] --> B[Nexus]
  B --> C{Check}
  C -->|Allow| D[Action leaves]
  C -->|Stop| E[Action does not leave]
  C -->|Person| F[Action waits]
  B --> G[Record]

Product surfaces

Surface	URL
Hardalion	hardalion.com
Nexus dashboard	nexus.hardalion.com
Sandbox	sandbox.nexus.hardalion.com
API	api.hardalion.com
Developer portal	developers.hardalion.com

Who this documentation serves

Developers connect an agent, put the gate on the path out, and read the record.

Operators sit on the path when it matters, and export the record when they need to prove what happened.

Next step: Connect your first agent.