Every action your model takes is checked, scoped and logged.
One access policy governs every request, whether it arrives from a person or an API key. Keys carry no more authority than whoever minted them, and every change lands in a log with no delete path.
One policy, two actors
A person is judged on their organisation role, an API key on its scopes. The dashboard and the API call the same function.
Keys that cannot escalate
The scopes a key may carry are capped by the role of the member who created it. A member mints read keys and nothing else.
A log with no delete path
The audit repository exposes no update and no delete. Twenty-one actions, each one attributed to the actor that caused it.
Residency you can name
Data sits in ap-southeast-1, under Singapore jurisdiction. The platform lists only the regions it actually operates.
Four things every request meets
Four gates, always in the same order
Every resolver asks one function before it touches data. The organisation is tested first, so a request for another tenant's resource is refused before the policy looks at roles at all. Denials answer in one documented vocabulary across the API and the dashboard, and when a key is turned away for its scopes the response names the scope it needed.
Results from LLMs powered by Nucleus
systems on one thread, Field engineering
delays resolved without a call, Fleet operations
incidents past their four-hour SLA, escalated by name, IT operations
Where the model acts inside several systems
Cable survey readings processed while the crew was still on site
47 trucks rerouted while they were still moving
Every incident past its four-hour SLA, escalated by name
Everything Harness enforces
Access policy
- One function asked by every resolver
- Organisation tested first
- Three ranked roles: owner, admin, member
- Four named denial reasons
- A refusal names the required scope
Keys
- Four scopes: read, train, infer, admin
- Scopes capped by the minting role
- nk_live_ and nk_test_ prefixes
- Bound to one project
- Secret shown once, SHA-256 at rest
- Revoked on the next call
- Rate limits per key
Audit
- Twenty-one recorded actions
- Actor, target, address and time on every row
- Keys and the system as actors
- No update and no delete path
- Sign-in activity readable per address
- Rows leave at their retention deadline
Security controls
- AES-256 at rest, TLS in transit
- Multi-factor authentication
- Data region ap-southeast-1, Singapore jurisdiction
- Region pinned per project
- PDPA compliant
- Regular penetration tests
Included with the API
Included with the API
Your bill is computed from three quantities: the tokens you train, the tokens you serve and the storage you keep.
More of Deploy
On-Premise Deployment
Our GPU servers, your site
Tool use
Your private APIs as skills
MCP
Your model in your tools
RAG
Answers from your documents
Webhooks
Signed events to your systems
Read on
Start with a key that can only read.
Create an organisation, mint a test key, and widen its scopes when you are ready to let it write.