Sveda is the pair you embed: @sveda-ai/core in the host, and sveda-server beside it. The stream protocol and MCP ride that pair. Source lives in the public repository.
It is not a chatbot you subscribe to. It is not a control plane you grow in a side repo. Product teams keep the app they already have; developers attach a client and run a runtime.
@sveda-ai/core is a universal JavaScript client. SvedaClient holds endpoints, headers, and tools. session.send posts a turn. Any host that runs JavaScript can attach.
sveda-server is an independent Axum process. It owns the agent loop, model catalog, tools, and host MCP. Your routes, auth, and deploy stay yours.
Tokens, tools, and MCP events travel one SSE pipe. Builtin tools, frontend tools, and host MCP share the same turn — without a separate orchestration repo.
The audience is people shipping a copilot inside an existing product — and the engineers who mint embed tokens, register tools, and run sveda-server on :8787.
Sveda is not a hosted chatbot SaaS. sveda.dev does not run your users' prompts. Sveda is not a Laravel package; the runtime is a Rust binary that sits beside the host. Sveda is not Vue-only; optional UI packages exist, but core is JavaScript.
Product
Each capability has its own page. Start with the client and the runtime — everything else hangs off that pair.
Docs
Reference for the client, host language SDKs, the runtime, and the wire. Copy is aligned to the source.
Solutions
Sveda is not a vertical SaaS. These pages map the stack onto the jobs it actually does.
Install the JS client. Run sveda-server beside the host. Stream the first turn.