Team connections, individual keys

Administrators configure provider credentials and model IDs. Members create their own keys, within the administrator’s provider, model, request and token allowances. Provider credentials stay encrypted on this server.

Request controls

Every API request checks key validity, member access and model permissions before forwarding. Concurrent requests reserve allowance together. Final reported usage settles the reservation; when usage is unavailable, the conservative reservation remains charged. These local allowances do not divide a provider’s subscription quota.

Provider support

API connections support the formats their provider implements. Subscription connections use separately configured private adapters. Antigravity and Cursor adapter support does not imply vendor approval or verified live compatibility. The Connections page names each integration and its requirements.

Your data

The local database stores members, hashed API keys, encrypted connection credentials, request metadata and audit events. Your requests go to the provider endpoints configured by an administrator. Back up the database together with its encryption secrets.

Jatevo 0.1.0. Documentation.