yea how did you get it over to the Apple Store lol
I had to make a project on Xcode, then submitted it to Apple connect 
I keep hearing this, no one seems to share an answer on why it’s not where you should be running a prod app. What’s your take on why it can’t?
No one seems to “point out” a reason, just says it can’t, which I’m always reluctant to trust because when I’ve heard that in my SaaS selling career, it always was coming from people whose jobs were at risk.
I’m not saying that’s the case or you’re wrong - failover, managing the development lifecycle (dev/test/prod), isolating code so the agent doesn’t touch it, and the agent messing with Prod would all be things I’d be nervous about; but I have yet to see a reason why my app wouldn’t work if I clicked “deploy.”
It would be cool to use ‘Deploy’ to push out to GCP/AWS/Azure to run prod in like you’re saying though. If you’ve identified gaps, you should share so the Replit team can consider them as part of their roadmap to make others feel confident it could run prod apps.
If you read my other posts, I run multiple prod microservices. I have an extensive programming background, so I can naturally identify gaps and holes, which there are some, but not many. I do love the push button deployment…. that’s full GCP…. I was a key systems architect for 1800-FLOWERS and FTD…. we rocked out gcp hard.
What are the gaps and holes?
1 Like
How much load do you expect your app to get? How many concurrent users do you expect? Will you be processing large datasets, complicated processes, etc.?
Replit recently announced:
- Partnership with Azure
- Added the dev and prod database split as you mentioned
- Shared customer examples of people making real money with their SaaS apps: GenAIPI — Customer Story - Replit
I am not here to convince you that your app should be in production on Replit - however, IMO other people are doing that already and running production loads. The code and data is always portable and could be migrated - if someone has to do that, kudos, they have a good ‘problem’ on their hands! 
1 Like
Great share @mark, thank you! What I was trying to say is it’s helpful if people are sharing what they’re experiencing for limitations (instead of just saying ‘I have credentials, trust me I know there are gaps’, which is usually what I see, or maybe I’m not digging through the forums enough). The last company I helped build, we scaled from $1M-$170M (a leading integration platform) in a very fast period of time where we were doing billions of API calls, running processing in Kubernetes, etc.
We would always be asking the questions you list to a potential customer, because that determines when something is the right tool for the job or not. I know the answer is usually going to be “it depends” in tech 
, but I’d rather people say “I ran into my app crashing when we hit 10k concurrent users” or “Latency on my API slowed significantly when we did X” than "Trust me, there are limitations.”
Giving examples helps the community start to plan for scenarios and help the product team make improvements when it comes up enough - similar to the improvements you point out, and thanks for that! The resources are awesome, and I probably need to do more digging in docs to understand limits.
@kbdub16 - totally get if you’ve posted about limitations in other places and don’t want to state them again.
2 Likes
ok, so what is your point?
Hi, I haven’t made a single dollar from Replit yet, I’ve only spent money so far. That said, I’ve built an MVP that I’d describe as semi-stable. It’s currently being used by around 20 users, so I’d say the product is in a potential pre-revenue phase.
Why do I say “potential”? Because I don’t fully trust what I’ve built yet, and I’m still figuring out how to make the product stable enough to scale.
What I’ve developed is a browser-based game that I promoted through a “build in public” approach on Replit. The game immediately gained strong traction on Reddit, resulting in tens of thousands of views and hundreds of users joining the waitlist. Right now, I’ve onboarded about 20 beta testers who are actively playing. The feedback has been mostly positive, but the game clearly needs some refinement.
One major issue I’ve noticed is the lack of a proper staging environment. Every change I make to the database is pushed live instantly, which often causes serious conflicts and bugs. That’s been a major blocker.
So now I’m stuck in a bit of a limbo. I’m not yet confident that the app is stable or valuable enough to monetize, and at the same time, I’m hesitant to open it up to everyone because I’m afraid of ruining its momentum.
What would you do in this situation?
And how can I make the app more stable and production-ready?
1 Like
Congrats on the beta launch @saveriobucciant! Also well done on getting 20 beta testers. It is always helpful to get a feedback loop for product, game, improvement!
Regarding the question:
Did you see the recent announcement about the dev/prod database environment?
Doc: Replit Docs
Announcement: Replit — Introducing a safer way to Vibe Code with Replit Databases
I launched this for a client last week: www.thewickbook.com. It’s a simple, single-product store taking pre-orders for a coffee table book. Fully built using Replit with Postmark for transactional email and Stripe for payment processing. I worked on it for a month (a few hours here and there). Sales are rolling in. This is one of 5 apps I’m building fully via Replit (actually…with lots of riffing in/with ChatGPT).
This one, www.checkyourfuel.com, will relaunch with a paid plan this/next week. I’ve been building this one, also a few hours every other week or so, over a 3 month stretch. Easily the most complex of the apps I’ve built so far.
2 Likes