Redirect.pizza is $3/mo (Basic). Crossroads is a self-hosted alternative at $0.99/mo. Here's when each makes sense.
| Crossroads | Redirect.pizza | |
|---|---|---|
| Hosting | Self-hosted, your infra | Managed SaaS (cloud only) |
| Data location | Your server, your disk | Redirect.pizza's cloud |
| Free tier | 50 redirects | Paid only |
| Pro pricing | $0.99/mo | $3/mo (Basic) |
| 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 |
Crossroads 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/crossroads/install.sh | sh
Teams evaluating Redirect.pizza alongside Crossroads tend to split on two axes: feature depth and data residency. Redirect.pizza wins on feature depth — it is a mature product with integrations, mobile apps, and a dedicated support team. Crossroads wins on residency — your url redirect manager data lives on your server in a SQLite file you can inspect, back up, and migrate without asking anyone for permission.
Crossroads 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 Redirect.pizza does not have to be all-or-nothing. Some teams run Crossroads for new data while keeping Redirect.pizza 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. $0.99/mo for Pro.