SOLUTIONS
Same runtime. Different jobs.
Sveda is not a vertical SaaS. These pages map the stack onto the jobs it actually does.
One runtime, many jobs
Sveda is not vertical SaaS. These pages show how the same client and runtime back product copilots, code agents, host MCP, and model failover.
USE CASE
Product copilot
Your app keeps routes and auth. SvedaClient talks to sveda-server. The visitor gets a scoped token. The stream carries text, tools, and MCP events.
USE CASE
Code agent
When a workspace index is attached, search_code and read_code_file are in the catalog. The agent searches, then reads, then answers — in one stream.
USE CASE
Host MCP
Host MCP is not a second client you wire by hand. URL and token go on POST /sveda/embed/token. The runtime lists tools and calls them during the turn.
USE CASE
Model failover
Failover is an ordered list on the runtime, not a rewrite of the UI. The same session.send, the same event types, the next model in line.
Map the runtime to your job.
Product copilot, code agent, host MCP, and model failover share one stream and one sidecar.