Inngest is $50/mo (Pro). Wrangler is a self-hosted alternative at $1.99/mo. Here's when each makes sense.
| Wrangler | Inngest | |
|---|---|---|
| Hosting | Self-hosted, your infra | Managed SaaS (cloud only) |
| Data location | Your server, your disk | Inngest's cloud |
| Free tier | 2 pipelines | Paid only |
| Pro pricing | $1.99/mo | $50/mo (Pro) |
| Dependencies | None (single binary + SQLite) | N/A (managed) |
| Setup time | ~30 seconds | Account signup |
| Dashboard | Built-in at /ui | Cloud dashboard |
| License | BSL 1.1 | Proprietary SaaS |
Wrangler is a single Go binary with embedded SQLite. Install it with one command, and you are running in under a minute. Your data stays on your server.
curl -fsSL https://stockyard.dev/wrangler/install.sh | sh
The pricing math between Wrangler and Inngest changes depending on team size. Inngest at $50/mo (Pro) is reasonable for a solo user. At ten seats, the difference compounds. Wrangler is a flat $1.99/mo regardless of seats — the binary does not count how many people use it. For growing teams, this makes Wrangler progressively cheaper while Inngest gets progressively more expensive.
Wrangler runs as a single static binary with an embedded SQLite database. There is no application server, no cache layer, no background worker. One process handles HTTP requests and reads from and writes to the database file directly. This simplicity is the entire point — fewer moving parts means fewer things that can break at 2 AM.
Moving from Inngest does not have to be all-or-nothing. Some teams run Wrangler for new data while keeping Inngest as a read-only archive of historical records. The API makes it straightforward to build a sync script if you need both systems to reflect the same data during a transition period.
Single binary. Free to start. $1.99/mo for Pro.