Fizzy is 37signals' kanban board app for tracking tasks, ideas, and projects. It gives teams boards with columns and cards, plus a calendar view, search, and saved filters, with free hosted accounts and a self-hostable codebase. It suits teams that want a calm, minimal board without per-seat pricing.[1][2]
Quick verdict
Fizzy fits small teams that want a calm, minimal kanban board without per-seat fees. Its concrete advantage is documented simplicity plus a real self-hosting path: free hosted accounts, or the ONCE installer, Docker image, or Kamal on your own server. Its material constraint is scope: no card dependencies, no card numbering, and no built-in analytics, so complex programs will outgrow it. If your work fits on cards with steps, assignments, and due dates, choose Fizzy; if you need dependencies and portfolio reporting, choose Trello or Asana.[1][2][3]
Key features
Kanban boards with columns and cards Work lives on boards where cards move across columns. This board model is the core tracking surface for tasks, ideas, and projects.[1]
Assignments, due dates, and steps Cards can be assigned to multiple people, carry due dates, and break down into steps that show progress at a glance.[1]
Labels, mentions, and followers Labels categorize cards while mentions and followers keep the right people notified without extra meetings.[1]
Comments and reactions Discussion happens on the card itself, with comments and lightweight reactions for quick agreement.[1]
Cross-board radar views Everything on your radar and Next up collect assigned work across boards, with a recently viewed list for fast return to context.[1]
Search with filters and saved team filters Search supports exclamation-mark filters, and saved filters can be shared with the whole team for repeatable views.[1]
Calendar views A calendar per board plus a combined view across all boards shows due dates in time order.[1]
Slide-open details, export, and API Card details slide open over the board, boards export including .ics calendar files, and a JSON API with personal access tokens, webhooks, and integrations connects Fizzy to other tools.[1]
Who will love it
Small teams drowning in heavyweight tools If issue trackers feel like administration rather than work, Fizzy's boards, steps, and due dates cover the essentials without the ceremony.[1][2]
Budget-conscious teams and nonprofits Free hosted accounts remove per-seat math entirely, and self-hosting removes subscription bills for teams that already run a server.[1]
Self-hosters who want boring infrastructure A prebuilt Docker image or Kamal deployment backed by SQLite keeps the operational surface small for teams that already operate services.[1]
Who should avoid it
Program managers who need dependencies Without card-to-card dependencies or linked cards, scheduling chains of blocked work has no native support.[1]
Teams that run on reports No card numbering and no built-in analytics mean status reporting and auditing need external tooling.[1]
Enterprises requiring SSO and compliance paperwork The documented surface covers boards and access control, not single sign-on, data residency statements, or enterprise support.[1][2]
What the reports suggest
One inspected firsthand press setup-and-use report (ItsFoss, self-hosted Cloudron install). No Reddit or G2 sample was accessible.
1 cited community source. One inspected firsthand press report only; no accessible Reddit threads or G2 reviews, so no independent user quotations are carried and nothing about reliability at scale can be inferred.
What the reports suggest The one inspected hands-on account values Fizzy's restraint: setup took about ten minutes on a self-hosted server and daily use stayed simple. That same restraint is the reported ceiling, with card numbering, dependencies, and analytics named as missing.[1]
Sample limits No original Reddit threads or G2 reviews were accessible, so no independent user quotations are carried. One press report is an anecdote, not a consensus, and says nothing about reliability at scale.[1]
Alternatives and portability
Incumbent alternatives Fizzy is positioned against Trello-style boards and heavier work managers such as Asana and ClickUp. Teams that outgrow its scope graduate toward those tools rather than sideways into another minimal board.[1][2]
Integration and portability surface A JSON API with personal access tokens, webhooks, and an integrations directory connects Fizzy to other tools, and board export including .ics calendar files keeps exit options open.[1]
Questions worth asking
What is the best Fizzy alternative for non-technical users?
Is Fizzy really no-code?
How much does Fizzy cost per month?
Can you self-host Fizzy?
Yes. The repository documents self-hosting with the ONCE installer, a prebuilt Docker image, or Kamal on your own server using SQLite storage. Sign-in on a self-hosted instance is handled over SMTP, so working mail delivery is part of the requirements.[1]
Sources and editorial review
Source research. Reviewed on October 9, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
One inspected firsthand press setup-and-use report (ItsFoss, self-hosted Cloudron install). No Reddit or G2 sample was accessible. One inspected firsthand press report only; no accessible Reddit threads or G2 reviews, so no independent user quotations are carried and nothing about reliability at scale can be inferred.
- Fizzy, by 37signals
official · Observed October 9, 2026
Official product site inspected October 2026. Establishes 37signals authorship, kanban positioning, do-one-thing-well philosophy, and free-for-everyone hosted accounts.
- basecamp/fizzy repository
official · Observed October 9, 2026
Public repository inspected October 2026, including the full README feature list, self-hosting documentation (ONCE installer, Docker image, Kamal), and the O'Saasy license terms.
- We Ditched ClickUp for Fizzy (ItsFoss hands-on)
community · Observed October 9, 2026
Firsthand setup-and-use report inspected October 2026. Self-hosted on Cloudron in about ten minutes; praised minimal UI, calendar view, group-by, import/export, and permissions; noted missing card numbering, dependencies, and built-in analytics. One report: an anecdote, not a consensus.