Fizzy is 37signals’ kanban tracker for issues and ideas — from the company behind Basecamp and HEY, and built explicitly as an answer to what it calls boring, sluggish, corporate issue-tracking software. It runs as a free hosted service at fizzy.do, and the same application can be downloaded and run on your own server. A board is a set of columns, a card is a thing to track, and the whole application is deliberately small: a Ruby on Rails app with an API and webhooks instead of a plugin ecosystem.
The hosted product is free, subsidised by Basecamp and HEY, with file storage capped at 1 GB. Self-hosting is a supported path rather than an afterthought: 37signals publish a pre-built image at ghcr.io/basecamp/fizzy:main, and the docs/docker-deployment.md guide covers the whole setup — mount a persistent volume at /rails/storage so the database survives restarts, set SECRET_KEY_BASE, add TLS_DOMAIN if the container terminates TLS itself, and configure SMTP so sign-up and notification email works. Their ONCE installer (curl https://get.once.com/fizzy | sh) sets up a single-machine instance and keeps it updated automatically, and a Kamal guide covers deployments where you want to change the code and ship your own version. The licence is the O’Saasy License: source-available rather than OSI-approved. You can run, modify and redistribute it, but you may not offer it to third parties as a hosted service competing with Fizzy itself.
Good for small teams and solo developers who want a fast board without sprints, story points and a configuration tree. Because storage lives in one mounted directory, backup is a copy of that directory rather than a database export, and the API and webhooks are enough to wire a board into existing chat and CI tooling. Self-hosting matters when cards hold customer data, or when you want to change how the thing works.