ReadMe is $99/mo (Startup). Viaduct is a self-hosted alternative at $0.99/mo. Here's when each makes sense.
| Viaduct | ReadMe | |
|---|---|---|
| Hosting | Self-hosted, your infra | Managed SaaS (cloud only) |
| Data location | Your server, your disk | ReadMe's cloud |
| Free tier | 1 API spec | Paid only |
| Pro pricing | $0.99/mo | $99/mo (Startup) |
| 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 |
Viaduct 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/viaduct/install.sh | sh
The pricing math between Viaduct and ReadMe changes depending on team size. ReadMe at $99/mo (Startup) is reasonable for a solo user. At ten seats, the difference compounds. Viaduct is a flat $0.99/mo regardless of seats — the binary does not count how many people use it. For growing teams, this makes Viaduct progressively cheaper while ReadMe gets progressively more expensive.
The operational difference is significant. ReadMe requires you to trust their infrastructure, their security practices, and their business continuity. Viaduct requires you to run a process and keep the data directory backed up. If your server dies, restore the binary and the SQLite file to a new server. The entire recovery procedure fits in a single paragraph because there is nothing else involved.
If you are currently using ReadMe and considering Viaduct, start by running both in parallel. Install Viaduct on a test server, point your workflow at it for a week, and compare the experience. Viaduct's data directory is isolated — running a trial costs nothing beyond the compute. If Viaduct does not fit, delete the binary and the data directory. There is nothing else to clean up.
Single binary. Free to start. $0.99/mo for Pro.