Security · Governance · Privacy
Built for teams that answer to someone
NYO puts every model your people and agents use behind one set of keys, one set of rules and one record of use. This page says exactly how it protects you - and what it does not do yet.
Security
Access is earned, keys are never kept in the clear, and every check fails closed.
Keys stored as hashes, shown once
API keys are stored only as SHA-256 hashes. The full key is shown once, when it is created; after that only its prefix is visible, to you or to us.
Approved accounts only
A new account cannot call the API until it is approved - by an administrator, a pre-approved email list or an invite code. Approval is re-checked on every request.
Row-level security on every table
The database enforces who sees what. Users see only their own keys, request records and credits; model backends and platform settings are visible to administrators only.
Provider credentials never leave the server
The credentials NYO uses to reach model providers stay server-side. Users, their applications and their keys never see them.
Fail closed
If NYO cannot verify an account's approval, its limits or its key's guardrail, the request is refused - never waved through.
Rate limits per account
Requests per minute and tokens per hour are capped per account, so one runaway script cannot flood the service or run up usage unchecked.
OAuth for assistants
Claude and other assistants connect through OAuth with a consent screen. The assistant receives a revocable token, never your password.
Governance
One place to decide who may use AI, for what, and to see what it cost.
Guardrails per key
Give each application's key a role - concierge, support, coding or your own. Allow or block tool calls, cap request size, and check that each request is in scope before it reaches a model.
Usage you can account for
Requests, tokens, latency, errors and cost by key, by model and by your own end-user ID, in the dashboard - and for administrators across the whole platform.
Exports for your own audit
Export your request records as CSV, JSON or JSONL for audit, finance or your BI tools.
Changes with a name on them
Account approvals record who decided and when; every credit grant records who made it. Paid plans cannot be switched on by the account holder.
A price on every model
Prepaid credits, and a published price per model. Spend follows what you load, not an invoice you discover later.
One catalogue of approved models
Applications reach only the models an administrator has routed. Add or retire a provider in one place, without touching a single application.
Privacy
What we keep, where it goes, and who processes it - no fine print.
Request records hold metadata, not your words
The request history kept for you records the model, tokens, cost, latency, status and tool names - not the text of prompts or answers.
Tracing, disclosed
To run and improve the service, the full text of API requests and responses may be sent to our tracing provider. We tell you here and on the consent screen. If your traffic must not be traced, talk to us before you send it.
Your request goes to the model you chose
Each request is sent to the provider that serves the model you called, and nowhere else besides the services listed below.
The Data Privacy Act, worked through with you
For organisations in the Philippines, we work through your obligations under the Data Privacy Act of 2012 with your data protection officer as part of onboarding.
Who processes your data
The services NYO relies on to run the hosted platform. A private deployment uses only the ones you choose.
- Cloudflare
- Application hosting and network
- Supabase
- Database and sign-in
- Nebius Token Factory
- Model inference
- Featherless
- Model inference for selected open models
- OpenRouter
- Model access for selected models
- LangSmith
- Request tracing
Where it runs
Hosted
llm.nyolab.ai: sign up, get approved, mint a key. The quickest way to put your teams and agents behind one governed endpoint.
Private deployment
For data that must stay on your network: NYO on your own cloud account or your own GPU servers, with your identity provider and no traffic to ours. Scoped with you.
Compliance support, included
We do not claim certifications we do not hold. What we offer every organisation that evaluates NYO instead:
- Your security questionnaire, answered by the engineers who built the system
- An architecture and data-flow walkthrough for your security and privacy teams
- A written description of the controls on this page, as they stand on the day you ask
- Your data processing terms, discussed and agreed before you go live
On the way
Controls we are building next. They are not live until this page lists them above.
- A per-account switch to turn content tracing off
- Teams with shared balances, roles and per-member limits
- Private deployment packaged for your own infrastructure
Bringing NYO to your security review?
Tell us what your reviewers need - a questionnaire, a walkthrough, or a private deployment - and the engineers who built NYO will answer.