WordPress is $4/mo (Personal) / Free self-hosted. Post is a self-hosted alternative at $0.99/mo. Here's when each makes sense.
| Post | WordPress | |
|---|---|---|
| Hosting | Self-hosted, your infra | Self-hosted requires PHP, MySQL, and ongoing security maintenance |
| Data location | Your server, your disk | Your server (if self-hosted) |
| Free tier | 10 posts | $4/mo |
| Pro pricing | $0.99/mo | $4/mo (Personal) / Free self-hosted |
| Dependencies | None (single binary + SQLite) | Docker, Postgres, etc. |
| Setup time | ~30 seconds | 15-30 minutes (self-host) |
| Dashboard | Built-in at /ui | Web UI |
| License | BSL 1.1 | Open source |
Post 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/post/install.sh | sh
The decision between Post and WordPress usually comes down to one question: do you need the breadth of features that WordPress offers, or would a focused tool that stays out of your way be a better fit? WordPress has spent years building an ecosystem around blog engine. Post does one thing well and gives you complete control of the underlying data.
The operational difference is significant. WordPress requires you to trust their infrastructure, their security practices, and their business continuity. Post 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.
Both Post and WordPress offer self-hosted options, but the operational requirements differ. Self-hosted requires PHP, MySQL, and ongoing security maintenance Post is a single binary with embedded SQLite — no containers, no external databases, no orchestration. The practical difference: Post runs on a $5 VPS with no configuration. Self-hosting WordPress typically requires a more substantial infrastructure investment.
The migration path from WordPress depends on how much history you need to bring over. If you only need active records, a manual re-entry through Post's dashboard might be faster than writing a migration script. If you need full history, export from WordPress and use Post's POST API to import records. Either way, the process is measured in hours, not weeks.
Single binary. Free to start. $0.99/mo for Pro.