Kanba

Kanba trims Trello down to what a solo developer or a small team actually uses. Boards, unlimited projects, team collaboration and dark and light modes are there; the process ceremony that usually arrives attached to them is not, and the whole thing runs on infrastructure you control.

The application is a Next.js project styled with Tailwind CSS and shadcn/ui, with Supabase for data and authentication and Stripe for payments. Billing runs through local Next.js API routes instead of Supabase edge functions, so a checkout route and a webhook route live in the same codebase as everything else and read their keys from a standard environment file.

Standing up an instance comes down to a handful of environment variables.

• Supabase: a project URL, an anonymous key and a service role key that never leaves the server.
• Stripe: a secret key, a publishable key and a webhook secret, all optional if you are not charging.
• Site configuration: the public site URL alongside a NextAuth URL and secret.
• Local testing: the Stripe CLI forwards webhook events to the development server on port 3000.
• Deployment: any platform that runs Next.js, with the webhook pointed at the deployed instance.

Keeping payments on framework routes rather than vendor functions is the decision that shapes the rest. Environment variables stay in ordinary dotenv files, debugging happens locally against a running dev server, and moving the deployment to another host later does not mean rewriting the billing path. Secrets stay server-side, and only variables meant for the browser carry the public prefix.