Fizzy

Fizzy runs on a vanilla Ruby on Rails stack backed by Hotwire, delivering a server-rendered Kanban board that bypasses heavy client-side build steps. Published on GitHub with its complete development history of over seventeen hundred pull requests, the project pairs containerized self-hosting with automated card lifecycle management. It provides visual issue tracking without frontend framework overhead or recurring per-seat fees.

Why Fizzy instead of Trello

Trello relies on its Power-Up ecosystem to connect outside tools, introducing third-party permissions, paid add-ons, and automation caps on entry tiers. Fizzy handles connectivity through direct outbound webhooks signed with HMAC-SHA256 headers. When cards are created, assigned, triaged, closed, or auto-postponed, Fizzy dispatches an event payload directly to your chosen endpoint, including Campfire rooms, Slack channels, or internal brokers. Operations leads can wire board events directly into build runners without routing data through external middleware.

That simplicity carries architectural trade-offs. Trello offers turnkey connectors, two-way sync integrations, and visual automation builders. Fizzy deliberately omits plugin marketplaces, pre-built synchronizers, and native board importers from Trello or Jira. Ingesting tasks or syncing statuses requires writing against Fizzy's personal-access-token REST API or calling its CLI. For teams wanting lean boards that announce lifecycle changes via clean webhooks, Fizzy removes integration layers; for organizations that depend on click-to-install SaaS integrations, building custom connectors requires engineering time.

What it does well

• Automated card entropy moves neglected cards to a dedicated column after an inactivity threshold, preventing backlog rot without manual grooming.
• Outbound webhooks send HMAC-SHA256 signed event notifications for card creation, assignments, and completions to team chat or build runners.
• Golden Ticket prioritization elevates urgent items to the top of a column without chaotic vertical card shuffling.
• Personal access tokens and a REST API give engineers programmatic control to create cards, query boards, and manage webhooks from scripts or the CLI.
• Global keyboard shortcuts for search, board navigation, and account menus speed up issue triage during standups.
• Multi-board workspaces support isolated client projects and offer optional public links for read-only stakeholder review.