Pricing
Pricing
Ivy costs €5 per million traces, and the first 100,000 traces each month are free for every workspace. One trace is one Lambda invocation, however many spans it contains. Every feature is in every plan, and self-hosting is free under the MIT license.
Free
€0 per month
- 100,000 traces a month per workspace
- Every feature: tracing, alerts, MCP, API, LLM spans
- Unlimited projects and team members
- At the limit, new traces wait for an upgrade or the 1st
Pay as you go
€5 per million traces
- First 100,000 traces each month still free
- Never blocked: no quota, no plan tiers
- Billed monthly through Stripe
- Upgrade in Settings → Usage
Self-hosted
Free MIT licensed
- Unlimited traces, workspaces and users
- Same images as ivytrace.dev
- Runs with docker compose up
- Your data stays on your servers
Cost calculator
Enter how many Lambda invocations you trace in a month. The cost is (invocations − 100,000) ÷ 1,000,000 × €5.
- Included free
- 100,000
- Billed traces
- 9,900,000
- Cost per month
- €49.50
One trace is one Lambda invocation, however many spans it has. Per workspace, per calendar month (UTC).
| Traced invocations per month | Cost per month |
|---|---|
| 100,000 | €0 |
| 1 million | €4.50 |
| 10 million | €49.50 |
| 50 million | €249.50 |
| 100 million | €499.50 |
What counts as a trace
- One trace is one Lambda invocation. The AWS SDK calls, HTTP calls, logs and LLM spans inside it are free.
- Usage is counted per workspace, across all its projects, per calendar month. It resets on the 1st at 00:00 UTC.
- Only functions you choose to trace count. Connecting an AWS account traces nothing by itself.
- Failures outside the handler (an init error, a crash, a timeout) are one trace each, like any other invocation. A healthy invocation never gets extra traces.
What's included in every plan
- Lambda tracing with payloads, AWS-aware spans and logs
- Auto-instrumentation and opt-in auto-trace by CloudFormation stack, name or tag
- Failures outside the handler and throttles, grouped into error groups
- Alerts: Slack messages per error group and a weekly email digest
- MCP server and HTTP API, across all your workspaces
- LLM spans from the Vercel AI SDK and OpenTelemetry GenAI
- OTLP ingest for anything else that speaks OpenTelemetry
- Workspaces, projects and team members, with sign-in through OIDC
Frequently asked questions
What happens when a free workspace reaches 100,000 traces?
New traces for that workspace are rejected until you upgrade or the month resets on the 1st (UTC). Nothing already stored is lost. The dashboard warns you at 80% and 100% of the quota, ingest answers with HTTP 429 and an upgrade link instead of dropping traces silently, and your functions keep running normally.
How do I upgrade?
In the dashboard, open Settings → Usage and click Upgrade. Checkout and invoices go through Stripe, and you're billed monthly for the traces beyond the free 100,000. Manage or cancel billing from the same page.
Is a paying workspace ever blocked?
No. A workspace on pay as you go has no cap. You pay €5 per million for the traces beyond the free 100,000 each month.
How is a trace different from a span?
A span is one operation, such as a DynamoDB query or an HTTP request. A trace is everything one Lambda invocation did. Ivy charges per trace, so instrumenting more calls does not cost more.
Can I set a budget?
Stay on the free plan to cap usage at 100,000 traces a month per workspace. On pay as you go, choose which functions to trace with auto-trace rules; nothing else is counted.
Does self-hosting cost anything?
No. Self-hosted Ivy is MIT licensed and has no limits and no payment code. You pay only for the server you run it on. See self-hosting.
Do I need a credit card to start?
No. Sign up (your coding agent can do it for you) and use the free tier. You add billing details only when you upgrade a workspace to pay as you go.