Question 1

What is an AI Pod?

Accepted Answer

The unit Snaga delivers. An AI Pod is a small team where humans and AI agents are co-executors: a Planning agent decomposes intent, Builder agents execute, a QA agent verifies, and a Knowledge agent remembers — running a closed Plan→Build→QA→Deliver→Learn loop with a human on every decision gate. You decide and sign; the agents do the work. A Pod runs in your own isolated cloud or on your own device, and gets sharper every loop.

Question 2

What is UARP?

Accepted Answer

Unified Agent Runtime Platform. It's the runtime, multi-tenant API, KV layer, MCP/A2A/ACP/OASF interop, billing, RAG and guardrails that Snaga is built on. Snaga is what you see; UARP is what runs underneath. The same runtime ships in our hosted product and in the self-host Docker image.

Question 3

How does Snaga Code relate to the platform?

Accepted Answer

Snaga Code is the Rust coding-agent CLI — and the Pod Connector: it signs in to the same UARP tenancy, sees the same agents, MCP servers and knowledge bases, writes its runs back into the same audit log, and is how a Pod reaches beyond the screen toward the physical world (MCP-reachable devices today; native hardware backends are Linux-first and rolling out). It ships free in every plan, including Free.

Question 4

Can I use the iOS app to manage agents in production?

Accepted Answer

Yes. The iOS app talks to the same SSE stream as Builder, so you see every step and tool call live. Push notifications fire on long-running run completion or failure. Sign in with Apple, GitHub or Google — same tenancy, no separate iOS account.

Question 5

Which models are supported?

Accepted Answer

Any OpenAI-compatible endpoint. First-class integrations for OpenAI, Anthropic, Together, Stels, Ollama and LM Studio. Primary/fallback chain is admin-managed at the platform level; agents inherit it automatically. Snaga Code can also point at fully local models for offline work.

Question 6

Which connectors ship today, and what's coming next?

Accepted Answer

21 OAuth integrations are live: Slack, Telegram, Email/SMTP, Webhooks, GitHub, Notion, Stripe, X/Twitter, LinkedIn, YouTube, Instagram, Facebook, TikTok, Google Calendar, Gmail, Google Drive, HubSpot, Shopify, Jira, Zendesk and the MCP-server bridge. Crypto exchanges (Binance, Coinbase, Bybit, OKX) are next — tagged "Soon" on the connectors grid until their backends ship. MCP servers cover anything in between.

Question 7

How does multi-tenancy actually work?

Accepted Answer

Every KV write is keyed under ["t", tenantId, …]. There is no cross-tenant data path — RBAC and the runtime enforce scope on every request and every tool call. Connector tokens are encrypted with AES-256-GCM at rest. Stripe customer mappings are per-tenant.

Question 8

Can I self-host?

Accepted Answer

Yes. The whole platform — API, runtime, builder — ships as a single Docker image with Deno KV bind-mounted to disk. Bring your own OAuth credentials, Stripe keys and SMTP. Caddy in front terminates TLS. We run the same image in production at snaga.ai.

Question 9

What about MCP servers I already have?

Accepted Answer

Bring them in. The platform speaks MCP as both client and server (stdio, http, streamable_http transports). Per-tenant scoping means you can wire a stdio server to one tenant without exposing it to others, and the runtime captures every tool call into the audit log.

Your Pod. Your AI team.

Sign in

Snaga

Pay for outcomes, not seats.

Free

Starter

Pro

Enterprise

FAQ