Skip to content

Inference infrastructure for AI teams

Serve every model on GPUs that never sit idle

Sirvich deploys your models to the clouds and clusters you already pay for, scales them with real traffic, and shows what every request costs. Your engineers ship models instead of tending machines.

Runs on the stack you already use

  • Kubernetes
  • PyTorch
  • vLLM
  • Triton
  • Ray
  • Terraform

Built for teams serving

  • Chat assistants and agents
  • Search and embeddings
  • Speech to text
  • Vision models
  • Fine-tuned open models
  • Batch scoring
  • Code completion

Production is a different job

The model works on your laptop. Production is where it breaks.

  • Cold starts add eleven seconds to the first request.
  • A traffic spike runs the cluster out of GPU memory.
  • Reserved GPUs sit idle all weekend, and bill all weekend.
  • A new checkpoint ships and p95 latency doubles.

The model is ready.The infrastructure is not.

Needs attentionsupport-agent · us-east-1

GPU memory at 94% on three replicas

Long prompts are queueing. Two replicas from the warm pool bring p95 back under 400 ms.

Autoscaler · 2 min ago

View traceAdd replicas

Scaling, handled

Traffic spikes. Your replicas are already warm.

Sirvich watches queue depth, not CPU graphs. When traffic climbs it adds replicas from a warm pool, routes around slow nodes, and hands the GPUs back when the rush is over.

Deploymentssupport-agent-v3

Deployment

support-agent-v3

  • Modelassistant-70b · fp8v3.2
  • ReplicasH100 80GB · us-east-16 running
  • Latencyp95 over the last hour312 ms
  • ThroughputTokens per second18.4k
  • Recent eventsWaiting for your review3
Traffic monitor/v1/chat

Requests up 3.4x in six minutes

Autoscaler responds

Scaling plan3 steps
  • Add 4 replicas from the warm pool
  • Send new requests to fresh replicas
  • Release them after 15 quiet minutes
Stays inside the team's budgetView plan

Meet your control plane

Every model and every GPU, accounted for

Sirvich keeps a live map of what you serve and where it runs, so you can go from a slow request to the GPU that served it in two clicks.

  • ModelsEvery version and checkpoint.
  • EndpointsWhere requests go, and why.
  • GPUsWhat you have and what it is doing.
  • BudgetsSpend limits for each team.
  • TracesEach request, prompt to last token.
  • RolloutsWhat changed, and when.
Production · us-east
Models14Endpoints22GPUs48Budgets6Traces1.2MRollouts3

How it works

Connect once. Deploy on every push.

  1. 01

    Connect

    Link the cloud accounts and clusters you already have. Sirvich runs inside them, with your keys.

  2. 02

    Deploy

    Push a model from your registry. Sirvich picks the runtime, precision, and GPU that fit it.

  3. 03

    Scale

    Replicas follow queue depth, with a warm pool for spikes and scale to zero at night.

  4. 04

    Observe

    Every request is traced. When a rollout hurts latency, Sirvich rolls it back and tells you which check failed.

Features

One control plane for everything you serve

1.0Autoscaling

Autoscalingsupport-agent-v3
Replicas, last 24 hours12 max
  • Target queue depth4 requests
  • Warm pool2 replicas
  • Scale to zeroAfter 30 quiet min

Scale on queue depth, not guesswork

Set a target for waiting requests. Sirvich adds and removes replicas to hold it, and keeps a warm pool so new replicas serve within seconds.

1.1Safe rollouts

Rolloutsv3.3 canary
  1. 1%
  2. 10%
  3. 50%
  4. 100%
  • p95 latencyvs 312 ms298 ms
  • Error ratevs 0.03%0.02%
  • Eval scorevs 0.900.91
All checks passingPromote

Ship a checkpoint without holding your breath

Every new version starts as a canary and is compared with the live one on latency, errors, and your own evals. If one slips, it rolls back on its own.

1.2Every GPU you have

FleetAll regions
  • AWS us-east-1H10034 / 40
  • GCP europe-west4A10012 / 16
  • Azure westus3H1006 / 16
  • On-prem rack 12L40S8 / 8

Rack 12 is full. New requests go to Azure westus3.

Use capacity wherever it is free

Pool GPUs across clouds, regions, and your own racks. When one region runs short, requests move to the next one that meets your latency target.

Cost per request

Know what every request costs before the invoice does

Sirvich meters GPU time per request and per team, then points out the jobs that would run as fast on cheaper hardware.

Tokens served today
412M
Average GPU utilization
78%
Spend this month
$18,240
Idle hours avoided
1,312 h
Deployments this week
9
BudgetsSearch team

Monthly budget

$4,180of $6,000

  • query-embed-v2H100$2,310
  • rerank-smallL4$1,120
  • nightly-backfillH100$750

Suggestion

Move nightly-backfill to L4 GPUs. It finishes in the same window and saves about $510 a month.

DismissApply

Works with your stack

Keep your stack. Plug Sirvich into it.

Sirvich connects to the clouds, registries, and tools your team already runs, so there is nothing to migrate and nothing to rewrite.

Add integrations

Connect the places your models live and the tools your team watches.

Skip for nowContinue
  • AWSPopularRun replicas on GPU instances in your own account.
  • Google CloudPopularUse A3 and G2 GPUs in your own projects.
  • KubernetesPopularBring any cluster with GPU nodes.
  • AzureDeploy to GPU virtual machines in your subscription.
  • Hugging FacePull open models and your private repos.
  • GitHubDeploy a new version on every push to main.
  • TerraformKeep deployments and budgets in code.
  • DatadogSend traces and GPU metrics to your dashboards.
  • GrafanaChart latency and utilization next to everything else.
  • PagerDutyPage the on-call engineer when a rollout pauses.
  • SlackPost scaling events and rollouts to a channel.

Built for production

Infrastructure you control. Not the other way round.

  • Runs in your cloud

    Models and data stay in your accounts, behind your network rules, with your keys.

  • Nothing ships unchecked

    Every rollout starts as a canary and rolls back on its own if latency or errors slip.

  • No lock-in

    Standard containers and plain config files. Export everything and leave whenever you like.

Pricing

Pay for the GPUs you use, not the ones you reserve

Every plan bills GPU time by the second. Higher plans add seats, regions, and support.

Hobby

For side projects

$0/ month

$10 GPU credit each month

Get started
  • Included: 1 seat
  • Included: 2 deployments
  • Included: Shared L4 GPUs
  • Included: Autoscaling
  • Not included: Canary rollouts
  • Not included: Your own cloud account
  • Not included: SSO and audit log
  • Not included: Engineer on call

Team

For small teams

$49/ month

$50 GPU credit each month

Get started
  • Included: 5 seats
  • Included: 10 deployments
  • Included: L4 and A100 GPUs
  • Included: Autoscaling
  • Included: Canary rollouts
  • Not included: Your own cloud account
  • Not included: SSO and audit log
  • Not included: Engineer on call

Scale

For production teams

Recommended

$399/ month

$400 GPU credit each month

Get started
  • Included: 20 seats
  • Included: Unlimited deployments
  • Included: Every GPU type
  • Included: Autoscaling
  • Included: Canary rollouts
  • Included: Your own cloud account
  • Included: SSO and audit log
  • Not included: Engineer on call

Enterprise

For regulated companies

Custom

Committed use discounts

Talk to us
  • Included: Unlimited seats
  • Included: Unlimited deployments
  • Included: Every GPU type
  • Included: Autoscaling
  • Included: Canary rollouts
  • Included: Your own cloud account
  • Included: SSO and audit log
  • Included: Engineer on call