Documentation Index
Fetch the complete documentation index at: https://docs.svantic.com/llms.txt
Use this file to discover all available pages before exploring further.
When to Use Svantic
Svantic is built for a specific class of problems. Here’s how to know if it fits.Good Fit
Use Svantic when you have:
- Multiple systems that need to work together — CRM, ticketing, billing, monitoring, internal tools
- Workflows that cross service boundaries — a task that touches 3+ systems
- Processes with conditional logic — “if X, then do Y, otherwise do Z”
- Human-in-the-loop requirements — approvals, reviews, escalations
- Compliance or audit needs — every decision needs to be traceable
- Customer support that pulls data from multiple sources
- Document processing that routes to different handlers based on content
- DevOps automation that monitors, diagnoses, and remediates
- Data pipelines that adapt based on what they find
Not a Good Fit
Skip Svantic if you have:
- A single, well-defined task — just write code
- No existing services to integrate — you’d be building from scratch anyway
- Simple CRUD operations — a REST API is simpler
- Real-time, sub-100ms requirements — agent orchestration adds latency
- No need for tracing or governance — the overhead isn’t worth it
Decision Checklist
Ask yourself:
If you answered yes to 3+, Svantic is probably right.
If you answered yes to 1-2, consider whether the orchestration overhead is worth it.
If you answered no to all, you probably don’t need an agent platform.
The Tradeoff
Svantic Adds
- A registration step for each service
- A mesh layer between services
- Telemetry overhead on every call
You Get
- Automatic routing and discovery
- Full traceability
- Knowledge that compounds over time
- Human-in-the-loop when you need it