# Ivy vs Lumigo

Ivy is an open-source (MIT) alternative to Lumigo for tracing AWS Lambda functions. Like Lumigo, it attaches a Lambda layer to the functions you choose, records every invocation with its payloads and AWS calls, and catches failures outside the handler. Unlike Lumigo, it is self-hostable, priced at €5 per million traces, and built for coding agents through an MCP server. Lumigo has announced that its platform shuts down on December 31, 2026.

## Lumigo's status

Lumigo was acquired by Dash0, announced on [February 4, 2026](https://dash0.com/blog/dash0-acquires-lumigo-to-expand-agentic-observability-across-aws-and-serverless). As of November 2026, [lumigo.io](https://lumigo.io/) says: *"Lumigo is now part of Dash0. The Lumigo platform shuts down on December 31, 2026."* Dash0's [acquisition FAQ](https://www.dash0.com/lumigo-acquisition-faq) says that all Lumigo customers have to transition to Dash0 by the end of 2026, and that the Lumigo platform will be sunset after they have migrated.

So every Lumigo user needs a new home for their Lambda traces in the next few weeks. Lumigo's own recommended path is **Dash0**, which also has a Lambda extension and an MCP server, with usage-based pricing per span. If you want the same team and a broad platform, that is a reasonable choice. Ivy is for teams that want something smaller: Lambda-focused, open source, cheap per invocation, and ready for coding agents.

## Feature comparison

As of November 2026, from Lumigo's public website and documentation.

| Feature | Ivy | Lumigo |
|---|---|---|
| Availability | Active, MIT licensed | Platform shuts down December 31, 2026 |
| Lambda instrumentation | Lambda layer with an exec wrapper (`/opt/ivy-wrapper`) | Lambda layer with an exec wrapper (`/opt/lumigo_wrapper`) |
| Auto-trace | Opt-in rules by CloudFormation stack, name pattern or tag; `ivy:trace` tag | Select functions in the UI, or the `lumigo:auto-trace` tag |
| Lambda runtimes | Node.js (Python next; others via OTLP) | Node.js, Python, Java, Go |
| Payloads | Events, responses, AWS SDK and HTTP bodies, redacted in the function | Yes |
| Failures outside the handler | Init errors, out of memory, crashes, timeouts (Telemetry API), throttles | See Lumigo's docs |
| Alerts | Slack per error group, weekly email digest | Broader alerting |
| Logs and metrics | Invocation logs and failure log tails only | Log management and metrics products |
| Kubernetes and containers | No | Yes |
| AI assistant | Your own agent, through an MCP server, MCP Apps views and an HTTP API | Lumigo Copilot |
| LLM spans | Vercel AI SDK, OpenTelemetry GenAI | AI agent observability |
| Self-hosting | Yes, `docker compose up` | No |
| Open source | Yes, MIT | No |

Where Lumigo is stronger: more runtimes, Kubernetes, log management and metrics, more mature alerting, and years of production use. Where Ivy is stronger: open source and self-hostable, a lower price per invocation, an agent-first workflow, and a future past December 2026.

## Pricing

| Pricing | Ivy | Lumigo (until December 31, 2026) |
|---|---|---|
| Free | 100,000 traces a month per workspace | Basic: 150,000 traces, 14-day trace retention |
| Paid | €5 per million traces beyond the free tier | Standard: $119 a month ($99 billed annually) for 1M traces; Plus: $359 a month ($299 annually) for 5M traces; Custom above that |
| 5 million traces a month | €24.50 | $299–$359 a month (Plus) |
| Self-hosted | Free | Not available |

Dash0, Lumigo's successor, prices per span and log record rather than per trace (see [Dash0 pricing](https://www.dash0.com/pricing)).

## Migrating

Moving from Lumigo to Ivy takes a few minutes per AWS account: untrace the functions in Lumigo (or remove its layer and variables), connect the account to Ivy, and choose what to trace. Your coding agent can do most of it. The [migration guide](https://ivytrace.dev/migrate/lumigo) has the steps and a concept map:

| Lumigo | Ivy |
|---|---|
| Transactions | Traces (one per Lambda invocation) |
| Issues | Error groups |
| Alerts | Slack alerts per error group and the weekly digest |
| Projects | Workspaces and projects |
| Auto-trace | Auto-trace rules |
| Lumigo Copilot | Your coding agent with Ivy's MCP server |

## Sources

Checked in November 2026:

- [lumigo.io](https://lumigo.io/): site banner on the shutdown date
- [Lumigo pricing](https://lumigo.io/pricing/)
- [Lumigo docs: Lambda layers](https://docs.lumigo.io/docs/lambda-layers) and [auto-tracing](https://docs.lumigo.io/docs/auto-instrumentation)
- [Dash0: Lumigo acquisition FAQ](https://www.dash0.com/lumigo-acquisition-faq)
- [Dash0 blog: Dash0 acquires Lumigo](https://dash0.com/blog/dash0-acquires-lumigo-to-expand-agentic-observability-across-aws-and-serverless), February 4, 2026
- [Dash0 pricing](https://www.dash0.com/pricing)

Lumigo and Dash0 are trademarks of their owners. Ivy is not affiliated with either.

---

Source: https://ivytrace.dev/compare/lumigo · Updated 2026-11-14