Platform & developer experience
Your keys, your projects, your control.
A shared AI layer needs real tenancy. VernaOne stores your own provider keys encrypted and scoped per project, isolates prompts, models, and usage per project with environment scoping and roles, and lets you issue scoped API keys for your apps and partners.
Try VernaOne free → ← All features
~15 providers & tools behind one API — LLMs, media, search & scraping
Shared keys and no isolation don't scale to a team
Passing one provider key around means no per-team billing control, no blast-radius isolation, and secrets in too many places. And without project boundaries, one team's prompts, models, and usage bleed into another's.
Handing an app or partner access safely requires scoped, revocable credentials — not your master key.
How tenancy works in VernaOne
- 1
Bring your own keys
Connect your own provider accounts and keys, stored encrypted and scoped to your project, so you keep control of billing and rate limits.
- 2
Projects with environment scoping
Isolate prompts, models, keys, and usage per project, with environment scoping so dev and prod stay separate.
- 3
Team roles
Assign roles so people have the access they should — owners and admins manage, others use.
- 4
Scoped API keys
Issue scoped x-api-keys for your apps and partners, so external callers get exactly the access you grant and nothing more.
Highlights
Encrypted BYOK
Your provider accounts, encrypted and project-scoped — you keep billing and rate-limit control.
Project isolation
Prompts, models, keys, and usage isolated per project with environment scoping.
Team roles
Owner/admin/user roles gate who can manage versus use.
Scoped API keys
Issue revocable, scoped keys for apps and partners.
Alert recipients, model health, and analytics are all project-scoped too — governance is consistent from keys to alerts.
Ship on this — free to start.
Author a prompt once and call it by name. VernaOne handles the model, the fallback, the cost, and the alerting.
Launch VernaOne →Frequently asked
Does VernaOne use my provider keys or its own?
Your own. VernaOne is bring-your-own-key: you connect your provider accounts and keys, stored encrypted and scoped to your project, so you keep control of billing and rate limits.
How is one team's work isolated from another's?
Each project isolates its prompts, models, keys, and usage, with environment scoping and team roles, so access and data stay contained per project.
Can I give an app or partner limited access?
Yes. You issue scoped API keys that grant exactly the access you choose and can be revoked, so external callers never use your master credentials.