Google. OpenCode. Anthropic. Github. Supabase. Vercel. 6 accounts to create a free online app...


I wanted to take this AI vibe coding adventure a step further.

Remember my Setlistplanner.com idea? So far - after 2 years - it has only one paid subscriber. Long story short: it's a failure. By the way, I'm 99% sure the same is going to happen with FlowDent.be. I'm not even going to make enough money with it to pay for the 2 domains I bought for it.

So I asked AI to rebuild SetlistPlanner. But this time I wanted a ZERO-cost hosted solution. No monthly payments for hosting, storage, database, or backups. And no advertising in my app or on the landing page.

This came out of it: https://ai.setlistplanner.com/ (I can even add my own domain, it's free!)

Opus 4.6 built this in minutes. Cost: $17.24.

I did not specify any technical details and let Opus decide on the stacks. Opus chose the following and explained why each time:

Layer Choice Why
Frontend React (Vite) Fast, great ecosystem
Backend/DB Supabase Free Postgres, built-in auth, realtime, RLS
Hosting Vercel or Netlify Free tier, auto-deploy from Git, works great with React SPAs
Chord Transposition chord-transposer (npm) MIT, transposes chords in arbitrary text, TypeScript support
QR Codes qrcode.react (npm) 4.2M weekly downloads, mature, simple API
Styling Tailwind CSS (or your preference) Fast to build UIs, great with React

 

Just to make things clear: I don't know, nor have I used, any of the above technologies. I'm a good old Classic ASP guy, remember... I do know one thing though. Using frameworks like React brings my "development skills" to 2026. I can now deploy applications that do not need "refreshes" to get the latest updates. This is very interesting in the case of a setlist planner. When I play with the band, I often decide at the last minute to skip a song, add one on the fly, or change the sort order. That makes my band members crazy. They use tablets during a live performance. Now I can be sure that when I do so, their setlists get changed without any hard refresh (F5). 

Another thing. The time between me prompting for a change or a bug fix - or why not, a new module - and the deployment on the live site is only minutes, sometimes less. I prompt for a code change in OpenCode, Opus 4.6 takes care of it, and it automatically pushes the changes to the GitHub repository (through Shell). Seconds later, Vercel automatically deploys the changes from the GitHub repo. Just like that. No manual uploads. No human interventions. I can literally speak to OpenCode and be sure that minutes later a new module or a bug fix is deployed. 

So far so good. However...

I need the following accounts to get this done:

  1. I'm using OpenCode.ai. I need an account there, as I only use paid AI, mainly Opus 4.6.
  2. I need an account at Claude to create the necessary API keys for OpenCode to use.
  3. I need a GitHub account where the code repo is stored.
  4. I need a Supabase account to deploy databases.
  5. I need a Vercel account to deploy the codebase (so Vercel needs to be linked up to GitHub).
  6. Actually, I've used my Gmail account just about everywhere I could. Makes life easier.

So this little app requires 6 accounts for 6 independent cloud-based services (OpenCode (Zen), Claude (Anthropic), Google, GitHub, Supabase, Vercel). That's a lot of dependencies. How sure can I be that in 2 years from now, this little web application will still be available? And for free? It's a long shot.

On the other hand, once you get used to this complex architecture... you can deploy dozens of such SaaS-based apps a day. There are no limits. And the only company that makes money out of this, is Anthropic (Claude). Maybe that's why Anthropic has crashed the software stock market.

To be continued.

© QuickerSite webCMS 2026

backtotop