u/SuccotashWooden1375

Hi everyone,

I’m building a SaaS app with Supabase and Vercel, and I’m still in the testing stage with no real customers yet.

Recently, my Supabase free-tier project hit 100% of the daily CPU/IO limits. I expected it to recover automatically after the daily limits reset the next day, but it didn’t.

Even after almost two days, the project was still unhealthy. I also tried restarting the project, but that didn’t fix the issue either.

On the third day, I tried purging, and after that, the project suddenly came back and all services showed as healthy again.

The important part for me is that I assumed a daily resource limit would recover after the next daily reset. But in my case, it stayed stuck for much longer, and neither waiting nor restarting helped.

One good thing that came out of this was that I finally set up Supabase locally for testing. Until now, I had been testing mostly in the cloud, but this issue pushed me to try the local Supabase setup, which turned out to be a useful experience.

One of the biggest takeaways for me was that the free tier may not be enough to support even a small number of real customers, depending on the app’s usage pattern.

I originally thought the free tier would be enough while I had no customers and was only testing. But after seeing how quickly CPU/IO usage can be exhausted, I started to realize that even a small production workload could hit the limits faster than expected.

Has anyone else experienced this on the Supabase free tier?

Is this expected behavior after hitting CPU/IO limits, or can a project sometimes get stuck in an unhealthy state even after the limit window resets?

For those running early-stage SaaS apps on Supabase, when did you decide to upgrade to Pro or move part of your stack elsewhere?

Any advice would be appreciated.

I'm building a small SaaS app with Vercel + Supabase.

The dev experience has been nice overall, but I was a bit surprised by how quickly the free-tier limits started getting used up, especially Supabase IO and Vercel function CPU.

To be fair, I'm still in development and I do run a lot of testing. I refresh pages often, check different flows, trigger auth, API routes, cron-like calls, etc. The app also has some dashboard/statistics features, so it probably makes more queries than a very simple CRUD app.

So it's not exactly zero usage, but even with no real customers yet, the limits seem to get consumed faster than I expected.

Curious how other solo founders are hosting early-stage SaaS apps.

What are you using when you have:

• No customers yet
• Around 10 users
• Around 50 users
• Around 100 users

Do you usually just upgrade to Supabase Pro / Vercel Pro, or move to Lightsail, EC2, or another VPS?

I'm trying not to over-engineer too early, but I also don’t want infra limits to become a problem before the product even has traction.

Would love to hear what worked for you and what you’d avoid.

I applied to Polar after getting rejected by Lemon Squeezy and Paddle, and it was approved much more easily than I expected.

That was a relief, but now I’m realizing approval is only the first step.

As a solo SaaS founder, I’m still nervous about the operational side: refunds, cancellations, failed payments, monthly credit grants, signup credit abuse, and making sure users actually understand how the credit system works.

My plan for now is to keep it simple: a free tier with limited credits, paid plans with a fixed monthly credit allowance, and very clear refund/cancellation terms.

Polar solved the MoR approval problem for me, but I still need to be careful not to overcomplicate billing too early.

Hi everyone,

I’m a solo founder based in Canada. I started building this product after managing my own job search in spreadsheets and realizing how messy it gets once you’re tracking applications, resumes, cover letters, interviews, notes, and follow-ups across many companies.

After building it, I also realized that there are already similar services in the market. In a way, that gave me some validation that this is a real problem, but it also made me think more seriously about positioning, trust, payments, and compliance.

The product is a web app and browser extension for job seekers. It helps users manage job applications, resumes, cover letters, interviews, notes, and follow-ups in one place.

I have already built some AI-assisted features, but I haven’t opened them to users yet. Since AI usage has real costs, I need a proper subscription or credit system in place before making those features publicly available.

I recently applied to Lemon Squeezy and Paddle as Merchant of Record providers, but both applications were rejected. I’m planning to try Polar next week.

I’m not selling physical goods, coaching, job placement, financial services, adult content, gambling, crypto, VPN/proxy, medical advice, or anything related to deepfakes or impersonation. It’s essentially digital software access, with optional AI writing assistance.

For founders who successfully got approved by Paddle, Lemon Squeezy, Polar, FastSpring, or another Merchant of Record provider:

1. What did you have ready before applying?
2. Did you need live users, revenue history, or an incorporated company?
3. What pages or policies helped with approval?
4. Are AI-assisted SaaS products harder to approve now?
5. If MoR approval is difficult at the MVP stage, would you recommend starting with Stripe and limiting sales to Canada/US first?
6. Is it better to reapply later after getting more users, clearer policies, and some traction?

I’d really appreciate practical advice from people who have gone through this recently.

Thanks.