Beta — early access is invite-only right now. Request access →
Security

How nostackai keeps your data safe.

What is in place today. Each item is something the platform does, not a promise on a roadmap.

isolation

Partitioned per org and workspace

Every org's and workspace's data sits in its own partitions, and the server checks the scope on every request. Enterprise gets a dedicated stack.

access

Server-enforced access policies

IAM-style Allow and Deny policies, checked on the server for every call, from the app, an agent or MCP.

sign-in

SSO for your team and your customers

Console SSO with Okta or Google, and workspace sign-in with Okta, Google or a password, with domain verification.

encryption

Encryption

AES-256 field-level encryption for sensitive fields, encrypted workspace secrets, TLS in transit.

backups

Point-in-time recovery

Every table has point-in-time recovery turned on, so data can be restored to any second in the recovery window.

ai data

AI records with a short life

AI requests are redacted and stored encrypted for 30 days, then deleted. The billing ledger keeps numbers and hashes, never text.

traces

Redacted, expiring traces

Delivery traces are redacted before they are stored and expire automatically.

code

Sandboxed custom code

Glyphs are hash-checked before every run, limited to allowed domains, and keep secrets out of logs.

ai builders

AI builds in dev only

MCP calls are checked against the caller's policy and audited. Only a person publishes to production.

uptime

Health checks and status page

Health heartbeats from every stack feed a public status page.

Ready when you are

Describe it once. Run it forever.

Connect your AI client, build your backend, ship to production.