> ## 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

> Is Svantic right for your use case? A quick checklist.

# When to Use Svantic

Svantic is built for a specific class of problems. Here's how to know if it fits.

<Columns cols={2}>
  <Card title="Good Fit" icon="check-circle">
    **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

    **Common scenarios:**

    * 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
  </Card>

  <Card title="Not a Good Fit" icon="x-circle">
    **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
  </Card>
</Columns>

## Decision Checklist

Ask yourself:

<Steps>
  <Step title="Service coordination">
    Do I have 2+ services that need to coordinate?
  </Step>

  <Step title="Decision-driven workflow">
    Does the workflow involve decisions, not just data movement?
  </Step>

  <Step title="Traceability requirements">
    Do I need to trace every step for compliance or debugging?
  </Step>

  <Step title="Evolving process">
    Will the process evolve over time based on what works?
  </Step>
</Steps>

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

<Columns cols={2}>
  <Card title="Svantic Adds" icon="plus-circle">
    * A registration step for each service
    * A mesh layer between services
    * Telemetry overhead on every call
  </Card>

  <Card title="You Get" icon="gift">
    * Automatic routing and discovery
    * Full traceability
    * Knowledge that compounds over time
    * Human-in-the-loop when you need it
  </Card>
</Columns>

For simple workflows, the overhead isn't worth it. For complex, evolving workflows across multiple systems — it pays off quickly.

**[Core Concepts →](core-concepts)**