Security for the layer under every agent.
Nasiko sits on the path between your agents and your models. It’s built to see as little as possible and to fail safely. Bring your own provider keys (BYOK); your data stays in your deployment.
Powered by
Where we stand on compliance.
Nasiko does not hold SOC 2 or ISO 27001 today; both are in progress. For privacy compliance, GDPR and CCPA data processing addenda are available now.
-
SOC 2 Type 2
In progress
Controls monitored in Vanta, readiness work underway with Cognisys.
-
ISO/IEC 27001
In progress
Information security management system established, aligned to the standard.
-
GDPR / CCPA
Available now
Nasiko acts as a processor for customer data; data processing addenda available on request.
Selected for GitHub’s Secure Open Source Fund.
GitHub chose Nasiko for its Secure Open Source Fund. GitHub wrote about what the projects in the program learned; we wrote about what it changed in how we build.
What we store and where it lives.
Data privacy by default: Nasiko keeps only the usage metadata it needs to show cost and activity. You bring your own provider keys (BYOK), and your prompts are never our training data.
- What we storeUsage metadata
- Which agent, which model, how many tokens, when: what Nasiko needs to show cost and activity for A2A-compliant agents.
- Prompts and responsesOff by default
- For coding-agent harness sessions, prompt and response content is off by default on Cloud and Enterprise, and syncs only with your explicit, per-user consent. Self-hosted operators can enable it for their own deployment.
- Where it livesGoogle Cloud, or yours
- Cloud plans run on Nasiko-managed clusters on Google Cloud. Enterprise runs single-tenant on your choice of cloud provider, or on-prem. Durable state is Postgres, Redis, and S3-compatible object storage.
- EncryptionEncrypted at rest
- Data at rest is encrypted with cloud-provider-managed keys. Credentials and secrets are additionally encrypted per user with AES-256-GCM. Customer-managed encryption keys (CMEK) aren’t supported yet.
- Model keysBYOK
- Bring your own key: model calls use your own provider keys, on every plan. Model usage is billed by your provider, not by Nasiko.
- Your dataNever used for training
- We do not use your prompts, responses, code, or traces to train models. We don’t sell your data or share it with other customers.
What you can review, and how to get it.
Nasiko maintains a written information security program, reviewed by leadership as part of our ISO 27001 and SOC 2 Type 2 readiness work, across both Nasiko Inc. (US) and Nasiko India Private Limited.
Documents
- SOC 2 Type 2 report In progress
- ISO/IEC 27001 certificate In progress
- Information security policies Under NDA
- Architecture diagram Under NDA
- Completed security questionnaire Under NDA
- Data Processing Addendum On request
- Privacy Policy and Terms of Service On request
Request the security package
Software bill of materials
Every component in the Nasiko server, with its version and license. CycloneDX 1.5.
- components
- 1,067
- direct dependencies
- 78
- Nasiko crates
- 55
- licenses
- 43
Subprocessors
Who handles data on our behalf.
- Google Cloud PlatformHosting
- GitHubSource control and CI
- Google WorkspaceCorporate systems
- VercelWebsite hosting
- MintlifyDocumentation hosting
- Reo.devVisitor analytics
- PostHogProduct and website analytics (US)
- SentryError and performance monitoring (US)
- StripeBilling and payments
- NeonDatabase for website enquiries
- ClayEnrichment of website enquiries
- CalendlyDemo booking
- ResendTransactional email (invitations)
Read our Privacy Policy and Terms of Service. Our Data Processing Addendum is available on request from your Nasiko contact.
Found a security issue?
Report it privately. Good-faith security research against systems you own, or are authorized to test, won’t result in legal action from us.
Full policy: SECURITY.md-
Report on GitHub
GitHub Private Vulnerability Reporting
On our public repository.
-
Email the security team
Email
- 2business days
- to acknowledge your report
- 7business days
- to share a triage verdict
Questions security teams ask first.
Can Nasiko break my agents?
No. A routing miss falls back to the best candidate rather than failing the call, and if billing is temporarily unavailable, paid workloads keep running (with an alert) rather than stopping. Authentication and access checks are the exception: those always fail closed.
Do you support SSO?
Yes. Google or GitHub sign-in today; OIDC single sign-on and SCIM provisioning on Enterprise.
How do I get your SOC 2 report?
We’re in progress on SOC 2 Type 2 and ISO 27001, not yet certified. Request our security package for our current controls and timeline.
Do agents ever see our credentials?
No. Credentials are encrypted per user and can be used but never read back. They’re added only as a permitted call leaves for the tool, and each request carries an identity that expires within minutes.