Trust
Governed agents, on an instance of your own.
Every request is checked against its organization, and keys stay hidden once saved. In Safe mode, a person approves each change before it happens. And every configuration change joins a log you can verify.
01·Isolation
Every request, checked.
A dedicated instance runs its own databases, event stream, storage, sign-in, and domain. Inside it, every request is held to the organization its user belongs to, on every route, before anything is read.
A request for any other organization is refused before anything is read. Firms on the shared NSTACK Cloud get the same checks.
02·Secrets
Keys go in once, and stay hidden.
An admin enters a key for each environment. Every read returns a mask, tests and runs use the key inside your instance, and records show it as [redacted].
03·Access and approvals
Agents work inside the access you grant.
Roles decide who changes what. Safe mode asks a person before any step that changes something, and every tool call stays on the record.
- Sign-in
Your own sign-in
Every part of the platform accepts sessions only from the sign-in your instance trusts.
- Roles
Admin, Builder, Member
Admins hold every permission, Builders do everyday work outside production, and Members can only read.
- Agents
Access you assign
An agent reads only the data an admin assigns it, in the run's organization and environment.
- Safe mode
Changes wait for a person
A step that confirms, submits, or moves money pauses until someone approves it. The server stamps who and when.
- Tool calls
Every call on the record
Each call records the tool and its arguments, with personal identifiers masked. An answer that cites a record outside the tool results is flagged.
- Machine access
Tokens for your systems
Your systems start automations with a token for each environment. Studio shows it masked, and a revoked token stops working at once.
04·Audit
A record you can verify.
Every run records what it did, how long it took, and what it cost. Each configuration change joins a log, sealed to the entry before it.
Change any entry and its fingerprint stops matching, along with every one after it. Studio recomputes the chain for you, and exports carry the fingerprints so your team can check them outside the platform.
- SHA-256 chain
- Append only
- Checked in Studio
05·Data handling
Environments keep work apart.
Test, staging, and production keep their own settings, agent versions, and search indexes. Production takes an admin and a typed confirmation, and deletes stay restorable for 30 days.
Every subprocessor, by name
06·Roadmap
Planned controls, labeled as planned.
Each one moves up this page when it ships. Certifications appear here once they are held, with the auditor, the scope, and the date.
- RoadmapSecrets
Envelope encryption for every credential
- RoadmapIsolation
Row-level security in every database
- RoadmapAudit
Daily anchors for the change log
- RoadmapData
Backups and restore drills
- RoadmapAccess
Entitlements per record
- RoadmapInstances
Vendor accounts per instance
Bring your security team.
We walk your team through each control in a staging instance, show the records each one writes, and answer your questionnaire.