Admin console
Models, MCP servers, policies, appearance, prompts, and limits in a browser. Change them when the product changes, without a deploy.
Coming soon
The control plane for the sidecar.
Coming soon. A console, included model tokens, and a private runtime for every project. The Sveda agent, chat, and tools you already use, run as infrastructure.
Less to operate
Cloud is the convenient layer around the Sveda tools you already know: the agent, the chat, and the host SDK. A console instead of a config ritual, model tokens on the plan, and a private runtime for each project, so the team spends the time on the product.
Tokens on the plan
A monthly model allowance is part of the subscription and metered per project. The bill covers the runtime and the included usage.
Your own provider key
A project can attach an OpenAI, Anthropic, or DeepSeek key when the allowance is the wrong contract. The key stays sealed in the control plane.
Orgs and projects
An organization has members, roles, and projects. Each project is one sidecar with its own settings, histories, and quota.
Hosted for you
We run the runtime, the database, and the network. You get a hostname, a quota, and a console. Capacity, backups, and updates stay with us.
In your product
Web, iOS, and Android embed the same chat. Your backend mints a short-lived token. The host key stays on the server, including inside a mobile app you already ship.
How it is built
Organizations, billing, and a runtime per project, already wired. Your app keeps minting the embed token. The console, the quota, and the network are part of the infrastructure.
-
CONSOLE
Admin
acme / billing owner- Models2
- Policiesreader
- MCPdocs
-
PROJECT
One cell
billing.runtimesveda-server
Postgres · Redis
Sveda runtime
-
APP
Your host
app.exampleCHATweb · iOS · Android SDK
-
PLAN
Tokens
INCLUDED
62%
metered per project
PROMPT
Email ada@acme.test about invoice 1842
REDACTION
Email email about invoice id
PROVIDER
ChatGPT or Claude sees the masked turn. The project store keeps the original.
For teams and companies
Directory sync, separate environments, a key you control, and a chat inside the iOS and Android apps you already ship.
SSO and directory
Members sign in with SAML or OIDC. SCIM keeps owners, operators, and viewers in step with your company directory.
Environments
Dev, stage, and production are projects under one organization. Each has its own runtime, settings, and quota.
Audit and SIEM
A record of who changed models, policies, MCP servers, and keys. The same stream can leave for the system your security team already watches.
Prompt redaction
Mask emails, phone numbers, and account identifiers before a provider call. The project can keep the original in history under the retention rule you set.
Your encryption key
A project store can be sealed with a key you hold. Revoke the key and the histories are no longer readable.
Region and network
Pin a project to a region. For stricter networks, the runtime listens on a private address and your app reaches it without a public hostname.
Spend caps
Set a ceiling per project and per organization. The console warns when the token allowance is running out, before the month ends.
Retention and deletion
Choose how long chats and tool traces stay, then delete a project and its stores.
No training on your chats
Prompts and tool results stay in the project store for the agent. They are not a training set for a Sveda model.
Use Sveda in your product today
The host SDK and the docs are public. The console, the token allowance, and hosted projects are coming soon.