Skip to content

CLOUD

Terms for hosted cells.

These terms apply if we operate a Sveda Cloud cell for you. They do not change the Apache 2.0 license on software you self-host.

Operator draft · Last updated 19 September 2026

Two licenses, two contracts.

The JS client, protocol, and sveda-server remain Apache 2.0 in the public repository. Self-hosting that software is governed there, not here. These Cloud Terms apply only when we operate a cell for you.

This page is an operator draft, not a substitute for counsel. A signed order or DPA, when issued, controls if it conflicts with this brochure.

What we provide.

A dedicated cell: sveda-server from the public GHCR image, Postgres, and Redis, reachable at a hostname we assign (typically <project>.runtime.sveda.dev). We issue a host API key. The public hostname is the embed runtime, not a settings console.

Cloud is coming soon. Public signup and an SLA are not offered on this draft. The docs copilot at runtime.sveda.dev is not a Cloud cell and is not covered here.

Your keys, your host.

You supply model provider keys (BYOK). You keep using the OSS host SDK from your backend. You are responsible for CORS origins you allow, for what your tools and MCP servers do, and for lawful use of the cell.

We may suspend a cell for abuse, non-payment (when billing exists), or a security risk. We may pin or roll the GHCR image. We do not claim copyright over your prompts, tool results, or product data.