Kanba

Key features

• Kanban projects and tasks Projects break into tasks on boards in the Trello shape of lists and cards. The README allows unlimited projects, so a maker juggling several side projects keeps each on its own board without hitting a project cap.[1][2]

• Notes beside the work Notes live in the same workspace as boards and tasks, so meeting records and reference material sit next to the work they describe instead of in a second app.[1]

• Calendar view A calendar shows dated work across the workspace, giving deadlines and scheduled items one shared surface next to the boards.[1]

• Deployment tracking Deployments are tracked inside the project workspace, which suits solo developers and small teams who ship from the same place they plan.[1]

• Integrations including Stripe billing The workspace connects to outside services, and the hosted service runs its checkout and billing through Stripe with local Next.js API routes for checkout sessions and webhooks.[1][2]

• Team collaboration Boards support team use rather than solo use only, so a small team can plan together in one workspace instead of splitting across personal boards.[1]

• Dark and light modes The interface ships with dark and light themes, a small but real comfort feature for people who live in the app all day.[1]

• Self-hosting on Supabase with full data ownership Teams can run the MIT-licensed code on their own infrastructure with their own Supabase project, keeping every record in their own Postgres database. Deployment uses environment-file configuration with Vercel as the documented host, plus local development from the same files.[1][2][3]

Who will love it

• Solo makers and indie hackers: the product is explicitly designed for them, with unlimited projects, simple boards, and a one-time payment instead of another monthly seat charge.[1][2]

• Small subscription-averse teams: a team that wants Trello-style planning without per-seat billing gets boards, notes, and calendar in one workspace for a single lifetime payment or free self-hosting.[1][2]

• Technically operated teams wanting data ownership: a team comfortable running Supabase and a Next.js host keeps its tracker data in its own Postgres database under an MIT licence, with no vendor lock-in.[1][2]

Who should avoid it

• Teams needing a finished managed service: a young 2025 project with thin independent review coverage cannot promise the polish, uptime history, or support apparatus of an established hosted tracker.[1][2][3]

• Organisations requiring SSO or a public API: no single sign-on and no public developer API are documented, so identity-managed or integration-heavy buyers should verify these before committing.[1][2]

• Non-technical teams planning to self-host: self-hosting means provisioning Supabase, managing Stripe keys, and configuring environment files, which assumes an operator the team may not have.[1]

Alternatives and compatibility