r/replit

I hired a contract developer, and he recommended migrating production to:

- GitHub (source-of-truth code repository)

- Neon (DB)

- Render (hosting)

- Clerk (OAuth)

Why do you think that was? Is Replit not able to do it all?

We recently moved a production app (Vite frontend, Hono backend, Postgres) from Replit to Google Cloud. It works great now, but a few things bit us on the way that I wish someone had written down, so here they are.

1. You inherit a lot of invisible work. Replit quietly handles HTTPS, port binding, process restarts, and keeping the thing awake. None of that is in your code, so none of it moves with you. Make a list of everything Replit does for you before you start, because on GCP every item on that list becomes your job (load balancer or Cloud Run config, health checks, a process manager or container runtime).

2. Audit your secrets before you migrate, not after. Replit's secrets tab makes it easy to forget what your app actually depends on. We found API keys hardcoded in source that had been added "temporarily" months earlier. Moving platforms is the one moment you will actually look, so scan for hardcoded secrets first (even a dumb grep for api_key and token gets you far) and move everything into Secret Manager in one pass.

3. The database will hurt you in ways Replit never did. This was our biggest outage source. We started on the smallest Cloud SQL tier (db-f1-micro) which allows only 25 connections. The backend opened a connection per request under load, everything worked in testing, then production traffic hit the ceiling and the app went down twice before we understood why. Two fixes: connection pooling (PgBouncer or your driver's built-in pool) and knowing that the cheap Cloud SQL tiers have limits Replit's managed Postgres never surfaced to you.

4. Decide early: Cloud Run or a VM. Cloud Run is the natural Replit replacement (deploy a container, it scales, you mostly don't think about it) but cold starts are real if your traffic is spiky, and anything that assumes a persistent local filesystem breaks, because the filesystem is ephemeral. If your app writes files to disk, that's a rewrite to Cloud Storage, not a config change.

5. Costs are itemized now, and egress is the ambush. Replit is one flat number. GCP is forty small numbers, and the one that surprises people is network egress. Set a budget alert on day one, even a generous one. The first month's bill is your real baseline, not the pricing calculator.

6. You need a deploy pipeline, even a tiny one. On Replit, editing is deploying. On GCP nothing deploys itself, and "I'll just gcloud deploy from my laptop" lasts until the first time two people do it in the same hour. Even a ten line GitHub Action that builds the container and deploys on push to main saves you from yourself.

The migration is not hard because GCP is hard, it's hard because Replit hides how much production actually involves, and it all lands on you at once.

Curious what pushed others off Replit (or convinced you to stay). For us it was needing a real database and predictable uptime.

Hi

I built an app with replit. Now i wish to move to the railway because some of my developer friends suggested moving to the AWS or railway because the split cost will high when the scale more. Correct ✅ or wrong ❌?

Suggestion please 🙂

And, how to move to the railway via githib? Should i give some comments to replit to adjust the code for deployment of another platform

Or can i add move to github direct?

The ad said the app had 0 in app purchases (false)
And The ad said the app regenerated tokens every day.
Both are false
It only regenerates tokens 3 times a month

I made a project I wanted to publish it but away from Replit I have uploaded all the files on GitHub and i didn’t work idk what to do anyone can help ?

trying to add team onboarding to a small B2B app i'm building. Stack is Supabase + Next.js (frontend came from an AI builder, backend done by hand). got the demo, got the login, got the basic dashboard.
the second i started on "owner can invite teammates, invitee accepts and lands in the right org with the right role" that's where it cracked.
Friction chain i keep hitting:

1. invite link generation: token, expiry, single-use. Supabase has the table helpers but the actual link semantics, edge function, and email template glue is all on me.
2. email verify vs invite acceptance. the two flows step on each other depending on thier order. half my test users land in a half-onboarded state.
3. org binding via RLS. user_id → org_id mapping is what i have to write and test by hand. wrong org on the wrong row = data leak waiting to happen.
4. permissions after leaving the org. revoke flow + cached JWTs + "user can still see this project because its token isn't expired" is the silent broken bit.
5. audit log (who invited whom, when). nobody builds this for you. need it for any B2B sales convo.
   4-5 days of glue code that has nothing to do with my actual product.
   what does the normal stack for this part look like for solo founders landing in B2B? Clerk? WorkOS? roll your own on supabase RLS? is there a builder that doesn't fall apart at the team-onboarding step?
   i'm also checking whether tools like enter handle any of this closer to the backend layer. haven't fully verified it, just reading docs and trying to figure out what people actually use.

Hi everyone,

I’m trying to understand a Replit billing issue and would appreciate any advice.

I have an active Replit Core plan. On Jun 15, 2026, I paid a previous Replit invoice/receipt for $57.86. This payment happened exactly around the time my new billing cycle started and after my Core subscription had already renewed.

Now I received a new invoice for $297.55. The new invoice appears to cover usage starting Jun 15, 2026 and is calculated as:

- Overage charges: $250.04
- 19% VAT: $47.51
- Total due: $297.55

In my Replit usage dashboard I currently see:

- Usage this month: $277.93
- Overage charges: $250.04
- Total available credits: $0
- Billing period: Jun 15 – Jul 15

What confuses me is that I already paid $57.86 on Jun 15, exactly at the transition to the new billing cycle. I also have Replit Core, so I expected the Core credits/monthly allowance to be applied correctly before any overage is billed.

My questions are:

1. Could there be an overlap between the invoice I paid on Jun 15 and the new invoice starting Jun 15?
2. Is it normal that the invoice total is higher than the dashboard amount because of VAT?
3. How can I verify that my Core plan credits were correctly applied?
4. Could some usage from Jun 15 have been counted or invoiced twice?
5. Are “previously invoiced amount” and “pre-purchase applied” lines supposed to fully reconcile this?

The new invoice includes Agent Usage, Autoscale Compute Units, Deployments, Neon Compute Time, Object Storage, and AI integrations.

I already contacted Replit Support, but I’m posting here in case someone has experienced something similar and can help me understand how Replit calculates this.

Thanks.

I've been doing complimentary tech consulting calls with vibe-coders the last week. And I've noticed something:

• 70-80% of the people I've talked to are overbuilding.

Their apps/platforms are sprawling bigger and bigger: more features, more ideas, etc. And most of them still say, "I just have a few more things I'm going to add before I launch."

It's clear: one huge downside of vibe-coding is that it's so easy to just keep building. Not just easy, but addicting.

After 25 years of building and delivering SaaS products, let me tell you: more is not better. You think it is, but it's not. You don't need more features to succeed.

My calls this week were supposed to center on addressing vibe-coder's technical questions and roadblocks. But mostly I found myself giving the same advice over and over again:

You need to go narrower. You need to find the core value of your product, strip everything else away, and absolutely nail the user journey to receiving that core value. Users will land on your site/app with the assumption that they're going to be disappointed. That's the truth.

Within seconds, you have to show them something that creates a crack in that assumption. They have to react with, "Oh wow, maybe this thing is actually exactly right for me!"

Once they are open to that possibility, then you need to deliver on that promise as quickly as possible. You have a few minutes and a few clicks to do that.

That motion of "land -> overcome doubt -> deliver value" needs to be your sole focus. Strip everything else away, stop building, and start testing that flow with real users. You underestimate how hard it is to get that right, and how many iterations you need to get there. Everything else is a waste of time right now.

If you can't stick the landing on that simple flow, more features only makes it worse.

Once you get the core flow working, then you can look at adding adjacent value, features that will keep them coming back again and again, etc. You can add breadth and depth, but you won't know how to do it effectively until you've nailed the narrow flow.

What is going on here? This change was so minimal, just removing a title+paragraph text from a page completely. I even pointed to the exact container with the visual tool so it had a reference.

Look at the comparison between two agent usages.. this needs a transparent answer please.

Replit I'm trying to love you because you're making me more time efficient, but for the love of vibecoding.. transparency please.

This one was cheaper.. than the second one.

https://preview.redd.it/1ay6hhpznwah1.png?width=576&format=png&auto=webp&s=51c7bb1f84b592e39b4d1de74c683804e538816a

What just happened? Also, the second one says it spent 30 cents on "Chat" - what does it even mean by that..?

After almost a year using Replit, and a few months on the $100 plan, I think it’s time for me to say goodbye.

I will always be grateful to Replit.

It wasn’t my first vibe-coding tool, but it was the first one that actually allowed me to ship a product.

I still believe it’s one of the best tools out there if you’re totally new. It’s also great for companies and teams that need to build internal tools quickly.

At the beginning, I used it for everything: database, auth, coding, infrastructure, deployments. Everything.

Then Codex came out, and I started using it to reduce credit usage.

Then I moved DB, auth, and storage to Supabase.

Then I added Cloudflare R2 for storage.

Then Resend for emails.

For a while, I was still keeping Replit as my infrastructure layer. Basically, I was using Replit to handle the backend.

Then I started deploying on Vercel.

And now I’m migrating my first Replit project over to a VPS with Coolify.

None of this would have happened without Replit.

It paved the way for my vibe-coding journey. It helped me understand how things connect, how products are shipped, and how to move from “I have an idea” to “this thing is live.”

So this is not a complaint.

It’s more of a love letter, and a letting go.

Replit helped me start. Now I’m ready to move on.

And I’ll always be grateful for that.

I rent like a dollar per hour to do the same stuff replit does, but when I used to pay replit the prices never really came across as absurd to me. I feel like people are forgetting how much of a time saver replit is. Also most people need to learn how to prompt as stupid as this sounds lol