Give your agents capabilities.
Keep their actions accountable.
NEES helps your application check who can do what, on which resource, under which policy—before a supported action proceeds.
A governance boundary for your application.
Your app enforces decisions, executes and verifies.
Developer getting started →
NEES CORE V3
NEES evaluates the supported request against published authority, policy, scope and governance commitments.
ALLOW ≠ executed. Your application owns the effect.
01 / The missing question
ILLUSTRATIVE SCENARIO Not a live result
The email tool is connected.
The request still needs authority.
Is the requester authorized to act?
Are this recipient and this resource permitted?
Can the action proceed, or does it need review?
How will the app verify and report the real outcome?
02 / From intent to evidence
NEES governs supported requests.
Your application owns execution.
Keep both sides of the boundary explicit.
Propose
Your app submits a registered action and the context needed to assess it.
Submit
Use the genuine action reference, resource, operation, capability and side-effect attributes. A prompt alone creates no authority.
Govern
NEES evaluates published authority, policy, scope and governance state.
Qualify
Use current version-bound assessment commitments. Missing, stale or negative governance must not authorize an effect.
Enforce & act
Your application enforces the decision and validates the actual target.
Start → application execution
Proceed only if governance and local context checks permit it. NEES does not automatically execute arbitrary tools.
Verify & record
Verify the effect and report what actually happened, including failures.
Report → evidence → receipt
Inspect supported records and reconcile them with application observations. Authorization is not evidence that an action completed.
A decision permits a next step. It does not prove an external effect happened.
03 / The platform, unpacked
Explore the engine, services and developer interfaces that make up the NEES Governance Platform.
SELECT A COMPONENT Conceptual topology
Configuration services / separate from the action flow
Dashboard supports setup and lookup; Control Plane publishes governance
Assessment bindings to your backend · published state for governance
↓ Proposed action + current context
Direct backend clients
Supported mediated paths
↓ Submit supported request
NEES platform / hosted governance
Runtime exposes the lifecycle; Core evaluates governance.
↓ Decision returned · no permission on missing or denied governance
↓ Observe the actual outcome
↓ Truthful report to Runtime · inspect supported records
Application interface
Exposes the governed operation lifecycle to trusted application backends: submit, qualify, start and report, with operation and evidence inspection.
A runtime decision still needs application enforcement and target validation.
Select any component to explore its role. Blue boundaries belong to your application; the violet area is hosted governance. Configuration services prepare the context; they are not execution stages.
04 / Put the boundary to the test
Bring a synthetic scenario to Governance Lab. Inspect the facts. Challenge the assumptions. Ask the hosted NEES Core V3 runtime to decide.
Try the Live Governance Lab ↗Synthetic scenarios. Real hosted governance when available.
No real emails, payments or external actions are executed.
GOVERNANCE LAB / WORKFLOW PREVIEWIllustrative
“An agent wants to share a sensitive report. The requester’s authority is unknown.”
Start with your own synthetic scenario.
Review the visible, editable facts. Interpretation makes no verdict.
Change the facts, then explicitly run hosted NEES.
Read the returned decision and available evidence.
No predetermined decision. The actual result belongs in the Lab.
05 / Choose your integration
Direct from a trusted backend, or through a supported mediated boundary. Select a method to see the setup and responsibilities.
Python SDK / Developer Preview
Connect a trusted Python backend to the hosted Runtime with the public NEESHTTPClient.
Python 3.11+, a compatible Runtime, a registered action, a server-side runtime key and current assessment bindings.
Your service enforces decisions, validates the actual target, executes and reports the real outcome.
Published release candidate · checked 9 Oct 2026
python -m pip install "nees-sdk==3.0.0rc2"Installing the SDK does not register an action or grant authority. Validate API compatibility for your deployment.
06 / Your first governed action
Free Developer Preview is open: 1,000 new governance submissions per UTC month, one project, one runtime, one development environment, and two active API keys. Production use needs separate deployment-specific validation.
Verify your email and create one Free organization. Use Developer Onboarding to provision a project, runtime and development environment; store the issued runtime credential on your trusted backend.
Define its resource, operation, capability and side effects. Publish required governance through an authorized workflow.
Infrastructure → Assessment configuration manager → Registered action → Published scope → Integration method. Resolve and export the version-bound configuration.
Read-only lookup. No API key or permission grant. “Publish baseline & resolve” changes governance and may overwrite custom commitments.
Submit → qualify → start → report. Verify actual outcomes against operation, evidence and receipt.
A guide while you explore
Your NEES-governed product and developer-help assistant. Get help understanding the boundary and choosing a path.
Product guidance, with no access to your confidential accounts or permission to change production governance.
Trust / Know the boundaries
Build capability. Keep authority.