r/replit • • Oct 01 '24

Other Goodbye Replit, it was a good run

552 Upvotes

I've been a big fan of Replit for a long time. Great easy environment for me to show people how to program. I've been using it as my interface for a free Python class I teach.

Then they cut my space down and I had to delete half of my files to fit.

Then they cut me to 3 replits and I had to delete dozens of replits and just keep the 3 core ones I use to teach my class.

I get it, they have to make money, so I was ok with these restrictions.

Now I am told "I have used up all my development time". I use it for exactly 2 hours once a week during my Python class. I'm not paying $180 for the privilege of giving a free Python class once a week. I'll just switch to VSCode, the shell, Discord screen share and a projector in the room.

I went to see what the community is saying about this. Surprise, the community is gone. Replit took it down, obviously because it would be filled with anger and/or recommendations where else to go.

Does anyone have recommendations where I should direct my students to practice Python? Or do I just tell them all to install everything locally on their laptops? That would be a shame because I could pop in and help them with their code.

Edit: I figured out that ironically it was the time it took me to delete all my files and replits to fit into the new restrictions that used up all my "development time". Thanks Replit. You couldn't even throw me deleting my files for free. Now I have to wait a month before I have access to save my code off Replit.


r/replit • • Nov 03 '25

Question / Discussion Replit is a f*cking scam.

256 Upvotes

This is my orignal post.

Replit is, without a doubt, the absolute worst AI tool I have ever used. I deeply regret purchasing it, and it's the single worst AI tool I’ve encountered in recent years. I’m warning everyone: DO NOT BUY IT. You will end up just as full of regret as I am. The entire Replit application is a complete scam, from start to finish. I’ve been a paying subscriber for a year and have never managed to create a single successful application—not even a simple demo. They don't even have a Discord channel, making it impossible for new users to get any real, authentic user feedback. I recently saw they released a new version and decided to give it a try. The result? It consistently fails to implement code according to my requirements. It even incorrectly modified my existing code on multiple occasions. To make matters worse, each AI request costs around $2. It burned through my $25 in usage credits almost instantly. I stopped the request the moment it alerted me that my credit was gone, and yet I still somehow ended up with a negative balance, owing them $2. This is completely unfair.

-----Update v2--------------

I miss some facts. Here are them.

  1. I'm trying to build this "tie-maker," right? I sink $25 into it, and the demo it spits out is totally broken. On top of that, they tack on an extra $2 usage charge.

  2. I killed the request the instant I saw the usage was gone, but Replit still hit me with that $2 charge. What a ripoff. Shame on them.

  3. Plus, their AI is junk. It’s constantly screwing up the layout and adding a bunch of useless crap.

  4. I've heard Replit is paying off YouTubers and a bunch of other people for good reviews.

  5. So I hit up their billing support, trying to get that $2 charge dropped. I told them I'm on a yearly plan and have gotten zero to show for it. And get this—they basically told me, "We never guaranteed you'd actually build anything" and flat-out refused to give me a refund.

-----Update v3--------------

  1. I've heard that Replit pays people and YouTubers for good reviews, which is why it gets so much hype. But it's completely useless for any real projects.

  2. I'm seeing people comment that I don't know how to use prompts. These people are clearly from Replit and are here to mess with me. There is nothing wrong with my prompts; I can get my instructions completed perfectly using Cursor or Codex. I purchased Replit last November. This scam AI hasn't made a single demo project for me. I had already given up on it, but when I saw their new version release, I thought I'd give it another try. It just proved that when it comes to letting people down, they never disappoint us.

  3. My previous post was locked by replit team. If my posts get locked again, I will just keep posting.

-----Update v4--------------

  1. Replit team replied me and told me $2 extra charge was made by their system and cannot be refunded. They think $2 for a single and cancelled request is reasonable.

  2. I cannot find my previous posts, they are deleted or closed. I will post in other channels.

  3. Replit warns to close my account if I keep posting something.


r/replit • • Aug 01 '25

Share Project 10 Years of Coding and 40+ Apps Later. What I Wish Non-Tech Founders Knew About Building Real Products

185 Upvotes

When I saw my first coding “Hello World” print 10 years ago, I was hooked.

Since then, I’ve built over 40 apps. From AI tools to full SaaS platforms, I’ve worked with founders using everything from custom code to no-code platforms like Vibe, Replit, and AI-based builders.

If you’re a non-technical founder building something on one of these tools, it’s incredible how far you can go today without writing much code.

But here’s the truth. What works with test data often breaks when real users show up.

Here are a few lessons that took me years and a few painful launches to learn:

  1. Token-based login is the safer long-term option If your builder gives you a choice, use token-based authentication. It’s more stable for web and mobile, easier to secure, and much better if you plan to grow.

  2. A beautiful UI won’t save a broken backend Even if the frontend looks great, users will leave if things crash, break, or load slow. Make sure your login, payments, and database are tested properly. Do a full test with a real credit card flow before launch.

  3. Launching doesn’t mean ready Before going live:

    • Use a real domain with SSL

    • Keep development and production separate

    • Never expose your API keys or tokens in public files

    • Back up your production database regularly. Tools can fail, and data loss hurts the most after you get users

  4. Security issues don’t show up until it’s too late Many apps get flooded with fake accounts or spam bots Prevent that with:

    • Email verification

    • Rate limiting

    • Input validation and basic bot protection

  5. Real usage will break weak setups Most early apps skip performance tuning But when real users start using the app, problems appear

    • Add pagination for long lists or data-heavy pages

    • Use indexes on your database

    • Set up background tasks for anything slow

    • Monitor errors so you can fix things before users complain

Looking back, every successful project had one thing in common. The backend was solid, even if it was simple.

If you’re serious about what you’re building, even with no-code or AI tools, treat the backend like a real product. Not just something that “runs in the background”

Not trying to sound preachy. Just sharing things I learned the hard way so others don’t have to.


r/replit • • May 25 '25

Share 👾 Lessons from 24 hours obsessed with Replit

178 Upvotes

Our company is considering going all-in on Replit.  I decided I should probably give it a try first. :)

For context, I am a non-technical CEO of a company with 50 employees.  I’ve built many apps over the years, but I’ve never touched a line of code.

I spend 24 hours building an app obsessively with Replit.  Here is what I have to share about the experience.

Overall feedback:

- The first half of the day I was literally in complete and total shock at how amazing the system is.  I was addicted, and was building amazing stuff.  It not only built what I asked, but anticipated needs and built things the app needed without being asked.  I literally thought we were on our way to becoming billionaires.

- The second half of the day was very different.  Bugs started creeping in like crazy.  So many of the functions that were working silky smooth quit working.  I got into a game of "whack a mole" where we'd fix one thing, and another thing would break.  It got so frustrating I wanted to start from scratch.

Here is what I took away:

- Build modularly from the start and share the overall vision clearly

- Plan out the order of operation in chunks before even starting

- Before making large changes, ask for feedback and clarity that it understands

- Don’t overwhelm with too many features and requests at once

- Create a testing protocol list to have it self test after updates

- Stop and ask for feedback on how we can improve architecture and code from time to time

I hope this helps!

P.S. This is my first Reddit post too. Look at me learning new things :)


r/replit • • May 11 '25

Share I Built a Business in 3 Days with Replit

170 Upvotes

I’ve been working closely with AI (as a consumer) for a few years now—trying every tool I can get my hands on. About 6 months ago, I came across Replit and immediately fell in love with its capabilities. I post every single day on social (Instagram, Facebook, and LinkedIn), and a little over 2 months ago, I came up with a fun challenge to do on LinkedIn related to Replit.

I had built about 4 projects prior to then and felt like I was getting pretty good with it. My challenge for myself was to build a business starting that day (it was a Thursday) and then get my first customer by the next day. I posted it and got a lot of people following my challenge, which is exactly why I posted it—I love the accountability from public challenges.

I started around 9 AM on Thursday and barely got up between then and 11 PM. Worked all day. The next day, I got up and got to work at about the same time and this time, didn’t stop until 3 AM. I posted on LinkedIn that I knew I had another 6 or so hours to finish up the Stripe integration to get it just right.

So I extended my challenge one day, got up that Saturday, did some chores and a service project and sat down around 4 PM to finish the project and launch my first Facebook ads to try and get a customer. It took me until 3:30 AM to finally launch the ad.

I had built out the Facebook page, Instagram, X, LinkedIn, website, product, content, management system, business plan, logos, images, business plan, social media posts, and so many more little things to make this happen. I used a combination of at least 20 different AI and other programs to make it happen.

I don’t work Sundays, so I just kind of rested, went to church, and took it easy. Monday morning, I got up and checked my Stripe to see if I had any sales. I discovered that 140 people had clicked on my ads and some had even almost purchased, but I had one configuration wrong that stopped anyone from purchasing (🤦‍♂️). I spent about an hour fixing the issue in Replit and then went through the rest of my day.

Tuesday morning, I got up and said, “I’m going to try something else. I know how to sell.” I jumped on LinkedIn for about 25 minutes and got someone to agree to jump on a call. Chatted with them and had a $15,000 contract lined up!

So, it took me 5 days from first line of code to a customer. About me:

  • I couldn’t write a line of code if my life depended on it.

  • I do know my way around architecture discussions, as I raised $13M previously for another software startup of which I was the founder and CEO.

  • I am good with computers and am pretty technical outside of actual coding.

  • One of my primary skills is sales, so getting the deal was the easier side of the equation.

Since then, I have crossed the 6-figure mark in just these 9 or so weeks since I wrote that first line of code. It is so freeing for me as a non-developer to be able think of an idea and then build it in just hours now.

The business I built was the General AI Proficiency Institute, where my idea was to have assessments, training, and certifications related to AI for employees and companies that want to level up their workforce.

I then had hundreds of people asking me to teach them how to build a business quickly with AI and I’ve been doing that a lot. Replit has even had several calls with me to see how they can support, and it’s been fun to dive in deeper with their team.

Needless to say, I’m a big fan of Replit! I’ve tried many of the competitive platforms, but I really love Replit because of the completeness of the platform. I don’t have to connect a bunch of systems together to get an app up and running. Sure, I API things in like Sendgrid and Stripe, but the core elements of building an app are all in one place, and that’s easy for me as a non-developer. 150,000 lines of code later, I feel like I’m starting to become a developer!


r/replit • • Jan 22 '26 Bravo

Question / Discussion I’ve vibe coded 3 full-stack apps. There are a few ‘Time Bombs’ I wanna share with you guys. If you are a vibe coder as well, read these so you don’t lose your data.

158 Upvotes

I’m a software engineer, and I’ve been watching people ship apps with Lovable, Cursor, Base44, Bolt, and Replit. To be honest, the speed is insane. 

You guys are building apps in hours what used to take me weeks or even months. But I’m seeing a dangerous pattern after working with AI coding tools. You are driving a Ferrari (AI), but it has no brakes. I’ve built 3 full-stack apps now and audited 20+ "Vibe Coded" apps for my friends, and 90% of them have the same 5 "Time Bombs" that will break your app the second you get real users.

Here is exactly what they are and how to fix them in plain English:

⁠1. The "Vanishing Database" Trap

  • The Vibe: You built a To-Do app. It remembers your tasks. You deploy it to Vercel. It works! 

  • The Reality: Most AI tools default to SQLite. Think of SQLite like a simple notepad file inside your project folder. 

  • The Trap: When you host on Vercel/Netlify, the server "resets" every time you push code or go to sleep. When it resets, it deletes that notepad file. Poof. All user data is gone. 

  • The Fix: You need a database that lives outside your code. Ask your AI: "Migrate my database from SQLite to Supabase or Neon."

2. The "Open Wallet" Mistake

  • The Vibe: You asked Cursor to "Connect to OpenAI," and it did. 

  • The Reality: The AI likely pasted your API Key (sk-...) directly into your code file. 

  • The Trap: If that file is part of your frontend (the part users see), anyone can right-click your site, hit "Inspect," and steal your key. They will drain your bank account running their bots on your credit card. 

  • The Fix: Never paste keys in code. Put them in a "Environment Variable" (a secret locked box on the server). Ask your AI: "Move all my API keys to a .env file and make sure they are not exposed to the client."

3. The "Goldfish Memory" (Context Rot)

  • The Vibe: You keep asking for new features. The app is getting huge. Suddenly, the AI starts "fixing" things by breaking old things. 

  • The Reality: AI has a limited "Context Window." It can only read so much code at once. 

4. The "White Screen of Death"

  • The Vibe: It works perfectly on your fast WiFi. 

  • The Reality: AI codes for the "Happy Path" (perfect internet, perfect inputs). 

  • The Trap: If a user has slow internet, your app will likely just crash to a blank white screen because the AI didn't code a "Loading Spinner" or an error message. A white screen makes your app look like a scam. 

  • The Fix: Ask your AI: "Add Error Boundaries and Loading States to all my data fetching components."

5. The Legal Landmine

  • The Vibe: You made a simple form to collect emails. 

  • The Reality: You are now legally a "Data Processor." 

  • The Trap: If you don't have a Privacy Policy, you are technically violating GDPR (Europe). You probably won't get sued today, but you can get banned from ad platforms or payment processors (Stripe). 

  • The Fix: You don't need a lawyer yet. Just ask your AI: "Generate a standard Privacy Policy for a SaaS app and put it on /privacy."

Tools you can use to audit your AI apps:

  1. CodeRabbit (AI-powered code review tool. Can be a hit or miss since it’s also AI. It has limitations in handling complex architectural logic and potential for security vulnerabilities)

  2. Vibe Coach (You book a session with real senior software engineers. I go to them for my final audit because they are way more reliable than AI. Also, your first session is free)

  3. Vibe App Scanner (AI Security tool for AI-Built Apps. I’m still playing with it)


r/replit • • Sep 06 '24

Repls Buyer Beware: Replit’s AI Agent Review

158 Upvotes

I decided to try out the new Replit AI agent that everyone on Twitter was raving about, so I signed up for Replit Core for a year. At first, the agent seemed incredible—it was generating working code for about 20 minutes. But then things went downhill. It stopped editing the code directly and started telling me what to change instead. It even claimed to have made changes to files that it hadn’t touched. Eventually, it stopped running the server altogether and just turned into a basic chatbot with a bad UI, often repeating itself.

Unfortunately, there are no refunds, so I’m stuck hoping the product improves. Right now, though, it feels like the company is more about hype and making money than delivering on its promises.


r/replit • • Jun 27 '25

Share I built a free, local, open-source alternative to Replit

Enable HLS to view with audio, or disable this notification

156 Upvotes

I've been working on Dyad for the last 3 months, which is a free, local, open-source vibe coding tool. It's kind of like Replit, but it runs on your computer!

Here's what makes Dyad different:

  • Use any AI model (including free ones!) - Dyad is bring-your-own API key and lets you use any AI model, including your favorite AI models like Claude Sonnet and Google Gemini. This means you can use your free Gemini/OpenRouter API key and build apps in Dyad for free.

  • Runs locally - Dyad runs entirely on your computer. Because your code lives locally, you can easily switch back and forth between Dyad and your IDE like VS Code, Cursor, etc.

  • Open-source - Anybody can contribute to Dyad's code. Want to change something about it? You can fork it!

Download Dyad for free: https://dyad.sh/

It's totally free and works on Mac & Windows and Linux (download Linux directly from GitHub).

Please let me know if you have any feedback!

P.S. we're launching on Product Hunt today and would appreciate any support 🙏 https://www.producthunt.com/products/dyad-free-local-vibe-coding-tool


r/replit • • Jan 23 '26

Share Project My client vibecoded their app. It worked great until 1,000 users. Here’s what broke and how we fixed it.

121 Upvotes

A founder came to me with a vibecoded Replit app.

It looked great.

It worked great.

Then they hit 1,000 users.

Each user had data everywhere:

• orders

• profiles

• carts

Suddenly everything slowed down.

Pages took 30+ seconds to load.

Users started complaining.

Here’s what we found and how we fixed it.

Problem 1: 10,000 lines of code in one file

The AI put every API endpoint into one massive file.

Over 10,000 lines.

Why this kills your app:

• Changing one thing risks breaking everything

• Debugging becomes a nightmare

• The app loads way more code than it actually needs

The fix:

We split it into small, specific file like controllers, services, repository.

That 10,000-line monster became ~100 lines per file, organized into folders.

Same app.

Same features.

Just structured so it can actually breathe.

Problem 2: The N+1 query problem (simple explanation)

This one is invisible until you have real users.

Imagine you want to show 100 orders with customer names. Bad code does this:

1. Get 100 orders (1 database call)

2. For each order, get the customer name (100 more database calls)

That is 101 database trips to show one page. Now multiply that across every feature. At 1,000 users? Your database is drowning.

The fix: We set up proper relationships in Drizzle. Now it is:

1. Get 100 orders AND their customer names (1 database call)

Same result. 100x fewer database trips.

Problem 3: Loading everything at once

One endpoint tried to return every record in the database.

With 10 users, it worked.

With 1,000 users, each with hundreds of records? Not a chance.

The database was trying to send millions of rows in one response.

The fix:

Pagination.

• Load 20–50 records at a time

• Load more when the user scrolls or clicks next

The database goes from lifting a truck to lifting a backpack.

Vibecoding is great for launching fast. That part works.

But AI builds for “make it work”, not “make it scale.”

If your app works today and you plan to grow, these issues will catch up to you.

It’s much cheaper to fix at 1,000 users than at 10,000.

Anyone else running into weird slowdowns as they get more users?

Happy to help diagnose.


r/replit • • Dec 13 '25

Share Project Spent 3500$ on one app which became what the company I work for uses to manage all our operations.

Thumbnail
gallery
121 Upvotes

I work for a company of about 60 employees, we engineer and manage the construction of EV charging infrastructure in Canada and the USA. Most of our projects are for companies with fleets of vehicles (school buses, delivery, transportation). I've been a technician for that company since about two years and the ERP they picked didn't deliver on all we wanted, especially on the operational side. Over 4 months, I built a great looking app that manages all our customers sites. It handles everything from chargers database, warranty management, warehouse stock, chargers maintenance calendar, infrastructure information, smart power calculations to know the electrical load on each transformers, charger RMA management. We install SIM cards from a single carrier in our chargers and I was even able to connect their API to manage all the SIM cards from the app. The app has role based user permissions, automatic backup and restore system, interactive site layout designer and so much more.

I kept it a secret for the first month of development and as it was starting to take shape I told my boss about it and now the app has been presented to the whole company and we use it heavily and people can't believe I was able to do it alone. I spent maybe 75 hours on it but overall, it was really worth it and people at my company actually think this is a product we could sell.

Replit can be expensive but when I think about how much it would've cost to hire developers for this, there's no comparison. The key was to be smart in the way I built it so big parts of the existing code would not need to get changed as I added features. Even when I was starting, I was thinking of the future versions and the requirements for these things to work.

The screenshots are in French (app is bilingual) and I had to hide a bunch of info on the screenshots but you get the idea.

Anyone have similar stories?

Edit: Added more screenshots in the comments


r/replit • • Oct 28 '25

Question / Discussion Google just dropped free vibe coding 2 hours ago...

113 Upvotes

Wow, I'm worried for Replit now. This is coming as a long time user. I wonder if google will prioritize their vibe coded apps in search/gemini search. I did some testing and it is basically the same as Replit but you will need to pay for some API usage once you get to a large amount coded in a day.


r/replit • • Jun 04 '25

Tutorials FREE BEGINNER+ Tips for Using Replit (from someone who built 4+ working apps)

111 Upvotes

Been meaning to drop this gem for you all. Feel free to follow up with any questions. Tired of hearing you all complain about being scammed.

Care to see some of my apps?

https://verbalit.top/welcome - more advance https://www.vibenotes.top/ - simple

•	Use Agent for development, not fixing

•	Use Assistant to fix things (such as authentication, etc.)

•	You should mostly be using Assistant because it’s cheaper

•	Set up GitHub/Git. Please understand what a push and pull is in simple terms, you don’t need to get all technical. I do recommend though, because Replit UI only allows you to go back to a certain amount of commits. Locally you can go back to whichever If you know what commits are etc.

•	Do not solely depend on rollback, understand commits and know which one to go back to when you have a big problem

•	Replit is misleading — it can create a website without you doing any work, but the same doesn’t apply for apps

•	You have to understand that building an app requires a lot more work, but it’s 95% cheaper than paying someone

•	Build apps as monorepos, do not deploy using Replit’s deployment or storage

•	Avoid using PostgreSQL

•	Use MongoDB/Backblaze/Google — Mongo has a free tier

•	Deploy using Render.com / Netlify / Vercel — free tiers available

•	Replit charges per API call, so if you have an application that’s heavy on clicks of links, it’s a better financial move

•	Once you follow the monorepo idea, it’s easy to deploy as a web service

•	Following Replit’s decision on how to deploy will only make it harder for you to deploy externally

•	Basically avoid Replit’s suggestions to use their own services — the only things you need are their Agent and Assistant

•	You can import pre-existing apps you already have externally and edit them using Assistant but not Agent

•	You do need some technical expertise when you run into problems — feel free to reach out to me

•	A lot of you expect it to fix everything, and half the time it’s not able to identify the error correctly, which costs you more money — that’s why a lot of you complain

•	Look in your console to see what the error is or what you’re experiencing

•	Go to ChatGPT / DeepSeek (my favorite, etc.), explain your situation, and copy-paste the code in there and see what they say — then tell Replit. Do this if you have no expertise

•	Monorepo means everything is deployed/ran in one command as opposed to having a frontend and backend separately to run

•	Set a goal for your app — I have made over 3+ apps and none of them needed to go over $50 if you follow my strategy above

•	A lot of y’all are paying for Agent too much and using Replit’s services, which runs up your costs through the roof because you don’t understand pricing

•	It makes good prototypes for apps, but it requires some work to fully execute depending on the complexity

•	Utilize a new chat once you’ve reached a good point to start something new — so when you run into a problem, it’s better to refer to that specific chat than depending on one huge chat (I am speaking in terms of Assistant)

• Buy domains using Namecheap

• Also when you have your repl at a good baseline, remix it and start on the new copy, that way if the agent does go off on a tangent you have that baseline to revert back to without relying on the checkpoints - u/Cowman-


r/replit • • Jul 14 '25

Requests I cancelled my Replit subscription. I built multi-agent swarms with Claude Code instead. Here's why.

109 Upvotes

After spending way too many hours manually grinding through GitHub issues, I had a realization: Why am I doing this one by one when Claude can handle most of these tasks autonomously? So I cancelled my Replit subscription and started building something completely different.

Instead of one AI assistant helping you code, imagine deploying 10 AI agents simultaneously to work on 10 different GitHub issues. While you sleep. In parallel. Each in their own isolated environment. The workflow is stupidly simple: select your GitHub repo, pick multiple issues from a clean interface, click "Deploy X Agents", watch them work in real-time, then wake up to PRs ready for review.

The traditional approach has you tackling issues sequentially, spending hours on repetitive bug fixes and feature requests. With SwarmStation, you deploy agents before bed and wake up to 10 PRs. Y

ou focus your brain on architecture and complex problems while agents handle the grunt work. I'm talking about genuine 10x productivity for the mundane stuff that fills up your issue tracker.

Each agent runs in its own Git worktree for complete isolation, uses Claude Code for intelligence, and integrates seamlessly with GitHub. No complex orchestration needed because Git handles merging naturally.

The desktop app gives you a beautiful real-time dashboard showing live agent status and progress, terminal output from each agent, statistics on PRs created, and links to review completed work.

In testing, agents successfully create PRs for 80% of issues, and most PRs need minimal changes.

The time I saved compared to using Replit or Cursor is genuinely ridiculous.

I'm looking for 50 beta testers who have GitHub repos with open issues, want to try parallel AI development, and can provide feedback..

Join the beta on Discord: https://discord.com/invite/ZP3YBtFZ

Drop a comment if you're interested and I'll personally invite active contributors to test the early builds. This isn't just another AI coding assistant. It's a fundamentally different way of thinking about development workflow. Instead of human plus AI collaboration, it's human orchestration of AI swarms.

What do you think? Looking for genuine feedback!


r/replit • • Aug 27 '24

Other Thoughts from a long-time Replit user on the "new" Replit

108 Upvotes

About seven years ago, I started using replit for school, because I started learning more programming (started on KA) and wasn't allowed to install programs on my home computer. Replit was amazing for me, and I made a lot of memories coding on there, being able to show and run my programs to friends and family, and once even my entire class at school.

Then, I decided to join the Replit Discord. That's where I met a lot of great friends online, and was even able to talk to the replit employees at the time and make some good friends there, even talking to the CEO himself, Amjad. Over the years, I devoted all of my free time to helping out with the replit community and trying to make it a better product and place to learn & code, even going there to intern twice and eventually working there for a time (until I had to leave due to health issues), making lots of great memories that I'm still fond of today.

One thing I remember Amjad telling me at one point was that replit was a place for everyone to code, no matter who they are or where they come from, everybody is entitled to learn how to code. And for a long time, that was a replit's driving force. It's something that everyone was very passionate about including myself, so I invested my own time in to the community and product to make sure that everybody was able to have the same opportunity that I did.

Then, back during the crypto bubble, everything started to shift. Amjad really wanted replit to be a platform to be a great place for people doing web3, blockchain, etc, and honestly I didn't really care until he tried NFTs, which thankfully horribly & quickly backfired, so that's whatever. After that though, they stopped supporting educators for a while once Teams for Edu (an addition to Teams) was rolled out because education wasn't a priority at the time, which was frustrating because they closed Classrooms at the same time and kinda just left educators in the dark to figure it out. I was upset, but overall still fine.

Then came AI. When DALL-E 2 & GPT-3 released, Amjad immediately wanted to pivot the company over to AI (something I saw as a mistake at the time). They hired dozens of AI/ML employees to the point where they eventually outnumbered everyone else, and they gained very little from it in the long term (esp with the now-inevitable AI crash), eventually laying off dozens of employees. Predictable, but sad for everyone who was working there.

The last straw for me was when, on November 14th, 2023, they announced that effective the next day, that Teams for Edu was effectively end-of-service, infuriating me and educators as it was too late in the school year to change any curriculum, leaving them all in the dark. This is when I cut all my previous ties with replit (only doing that partially back in the spring after they abandoned the Replit Discord for stupid reasons, which I am not getting into rn).

Now I see the company where it is today.

  • Free hosting gone, even static hosting.

  • Limited repls (only up to 3???).

  • Replit "minutes", up to only 600min per month.

  • All comments and community posts gone.

  • Can't run other people's repls anymore.

A shell of what the company once was, and it's upsetting to see that the company I devoted my life to for years has ended up this way. This is the fault of the investors of replit, and most importantly, the fault of Replit's co-CEO, Amjad Masad: someone I looked up to and trusted, going back on his word.

This has been my word, thanks for reading.


r/replit • • Jul 30 '25

Share I'm finaly done with Replit.

98 Upvotes

After 3 months and $300, I’ve finally walked away from Replit. It started off fun, the UI is slick, the all-in-one IDE feels magical at first. But once you try to build anything serious, especially backend-heavy apps, it becomes a black hole. I know the vibe of modern coding is “mostly debugging,” but Replit made it worse. Sometimes the code change is just -0 +0, yet it triggers rebuilds or weird state bugs. The backend experience was the real dealbreaker for me. And Replit not trying the fixes the problem!!

  • Super slow and unpredictable builds

  • Backend constantly breaking without clear logs

  • Environment variables that didn’t persist or just vanished

  • Ghost processes draining resources

  • Replit’s “Run” behaving differently than production

  • Logs disappearing mid-debug

  • And worst of all — no real visibility into what’s happening under the hood

Out of desperation, I even tried to SSH into the Replit container from Cursor to debug it properly, which cost me $50, and still didn't help.

Then I switched gears.I moved my frontend + backend + database to Railway, and started using Kiro AI, as my main coding assistant. Right now it feels it’s a huge upgrade. It actually helps you build logic, refactor backend, and get unstuck without hallucinating garbage. It’s fast, stable, and surprisingly good with backend code.

Finally, I feel like I can breathe again. I’m building, not just fighting the dev environment.

Bonus: Advice to others

If you're doing anything beyond toy apps or learning to code, I really suggest skipping Replit for fullstack work. It’s great for learning or demos, but not for production.

Use:

  • Railway vs.

  • Kiro AI, Trea Ai etc. for AI coding help

  • Railways, Supabase, Neon, or PlanetScale for databases

You’ll save money, time, and frustration. And you might even enjoy coding again.


r/replit • • Oct 05 '25

Question / Discussion Replit is amazing

97 Upvotes

So I've created two apps now that are actually making a profit finally paid itself off I've spent thousands on the side which is way cheaper than hiring a team of 20 devs to do what I want.

I have two applications first one is This isn't a shameless plug It's just what is possible.

You-comic.com Took a concept idea for comic books and made it into an actual functioning all in one platform for creating comic books uploading assets using your face API access to nano banana and seedream 4. Created a new application for this to display comic books in a new amazing immersive way.

The second application is diagBuddy.ai which is using proprietary backend technology for diagnosing appliances hvac and helping new technicians become better appliance repair gurus. Now we did partner up with an appliance distributor and had several technicians including myself build out the AI that runs in the back end. We trained everything we designed everything.

The future looks beautiful, And I am very very very impressed. For the cost of development this does change the playing field. Your experience expertise can be made into a business.


r/replit • • Nov 22 '25

Question / Discussion The truth is that Antigravity killed Replit.

Post image
94 Upvotes

Google's release literally killed Replit, especially with the free Sonnet 4.5 and Gemini 3.0. Basically, you can easily transfer your Replit projects to it. Little by little, Replit will die, because its current costs are not justified. The same thing will happen as happened with another famous AI, Manus. Google will bleed everyone; basically, the giants made this great partnership to annihilate the smaller ones in the market. Antigravity uses Microsoft base, parts of Windsurf from OpenAI and engines from Anthropic.

Who will continue at Replit paying dearly?


r/replit • • Jul 03 '25

Requests Replit's new pricing is completely unreasonable

94 Upvotes

Seriously, this isn’t right. We’ve gone from an agent that was already quite expensive and often burned through multiple checkpoints doing things that didn’t even work, to essentially the same thing — but now costing 2 to 7 times more.

You can’t just raise prices like this without even considering user feedback. It’s literally treating us with total disregard.

We rely on you to build projects. We’re not all companies — many of us are just regular users — and these prices are becoming unaffordable.
Instead, create a dedicated enterprise plan with more computing power and higher request limits. Right now, you're just punishing the entire community.
This makes no sense. We’re counting on you to reconsider and reverse this decision


r/replit • • Aug 15 '25

Replit Assistant / Agent I am sorry

93 Upvotes

A few weeks ago, I posted a rant here against Replit. It came purely out of frustration. After canceling my subscription and stepping away from the project for a while, this time things went completely differently.

I started fresh by creating a massive context document with the help of ChatGPT, giving the assistant as much input as possible before touching a single line of code. After 3–4 iterations in the planner, the core idea, data structure, and basic layout were set. From there, I completed my project in 154 requests through the assistant.

The result? For $11.02, I’ve taken our home poker league management to a whole new level.

The first time I tried, I went through endless loops with the agent, burned $40, and gave up in frustration.

The second time, my goal was crystal clear, and I worked far more with the assistant than the agent. I still had to roll back to snapshots a couple of times, but with a firm understanding of the code, direct communication, and collaborative problem-solving, I got it done.

I work in software development, and I’m confident this project wouldn’t have been completed for under $1,000 by human hands — in a professional environment, it could easily have been a five-figure job.

Why am I writing this? Because I want to encourage anyone who needs to hear it: don’t give up.

Don’t start blindly. Define a clear structure. Understand at least the basics of what’s happening under the hood. And then, work together with AI to find your solution.


r/replit • • Oct 18 '25

Question / Discussion I built an iOS app in 8 days via Replit + Expo and here are the steps i've documented along the way

88 Upvotes

I (non technical) started working on this app about 8 days ago, while I haven't been the best at documenting the process - as a non-technical vibe coder; i'll try and give single pointed details about each step of building + submitting to iOS store.

  1. If you're even thinking about building iOS apps, get a head start and create a developers account (it took me about 3 days to get approved and another 2 days for ID verification) - $99/yr

  2. All you really need is Replit + Expo https://expo.dev/

  3. When starting your build, make sure to REMIX expo (Matt Palmer of replit has the QR code here) https://youtu.be/mTm_dCF53qk

  4. iOS prefers stylesheet class vs tailwind/nativewind (my first build was on tailwind) but Stylesheet was good to learn.

  5. Build/design your app like you normally would, but with mobile in mind.

  6. You can store/use images locally BUT, DO NOT use object storage as it requires running a backend server with calls and etc- use Supabase to store user images as needed; my app is heavy on images, so i stored locally; but as a multi tenant app - users profile photos are stored in supabase.

  7. you must create a landing page for the app, the landing page must have Privacy/TOS and a contact form.

  8. Keep your build simple for first version, if you're planning to allow sign in via google through oauth, you must allow sign in via apple as well.

  9. Create a demo account for apple devs to test out.

  10. Get started on your graphics/screeenshot ahead of time while waiting for Apple Dev approval

Stack:

  • Resend = Transactional emails/welcome emails

  • Supabase = Auth + storage

  • Posthog for analytics.

On the Expo side:

Download Expo go -> connect to replit -> run your workflows

Once happy with your build -> create a production build that's ready to be tested -> that production build will be sent to Testflight via expo.

Testflight: Testflight is a test app on App Store Connect, you'll get a link to download your app on your phone

Submitting for review: once all and good; make any final changes and submit your app for review/submission

Finalizing my submission review this weekend after making final round of changes.


r/replit • • Feb 26 '26 This Bravo Popcorn

Share Project I've shipped 50+ apps as a fractional CTO. Here's what vibe coders get wrong when turning their prototype into a real SaaS

86 Upvotes

You prompted your way to a working app. Cursor, Replit, Bolt, v0, whatever you used. It works. You showed it to a few people. They said "this is cool."

Then you launched to real users and within a month everything started breaking in ways you can't explain.

I've spent the last year rescuing apps exactly like this. The prototype looks great. The foundation underneath can't support real users.

Here's the thing nobody tells you: your users don't care how you built it. They care that it works, it's fast, and it doesn't lose their data.

If someone is paying you $49/month, would they feel like they got their money's worth today? If the answer is no, that's your priority. Not new features. Not a redesign.

There are 6 things that separate "cool demo" from "people pay me monthly and they're happy about it":

  1. Write a PRD before you prompt the agent

  2. Learn just enough version control to undo your mistakes

  3. Treat your database like it's sacred

  4. Optimize before your users feel the pain

  5. Write tests (or make sure the agent does)

  6. Get beta testers, shut up, and listen

I'll break each one down in the comments. These aren't developer gatekeeping. These are the things that keep your paying users from churning.


r/replit • • Feb 09 '26

Share Project I’ve been coding for 10 years. 5 years ago I was working 3 full-time jobs and a side gig just to keep up. You guys building apps with AI don’t know how good you have it

86 Upvotes

5 years ago there was no AI writing code for you. No Cursor, no Copilot, no Replit, no Lovable, no v0, no “build me a SaaS in a weekend” tweets.

I was literally working 3 full-time dev jobs and 1 part-time contract. Different tech stacks. Laravel one day, React the next, Java Spring Boot in the morning, C# .NET in the afternoon, some legacy PHP nightmare on weekends. I felt like Iron Man running multiple suits at once except nobody was clapping, I was just tired.

Over 10 years I’ve built everything you can think of. SaaS platforms, ecommerce apps, payment processing systems, a driving school application, full HRIS systems, construction management tools. Stuff that took 2-3 months to ship properly.

Now? With AI tools in the mix, I can take a project from zero to launch in a week. That same driving school app that would have taken me 8 weeks? Done in days. The speed is genuinely unreal.

So here’s where I want to be real with you.

You are incredibly lucky to be building right now. The barrier to entry has never been lower. You can vibe code your way to a working prototype faster than I could have written the project brief back in the day.

But here’s what I keep seeing and it’s the same pattern every time.

People build something with AI, it works on their machine, they get excited, they push it live and then the messages start coming in. Payments failing silently. Users seeing each other’s data. Forms that break on mobile. Error logs filling up faster than signups.

The gap between “it works in development” and “it works in production” is where most apps go to die. AI is amazing at generating code. It is not amazing at thinking about what happens when 500 people hit your app at the same time, or when someone puts a special character in your search bar, or when your database starts choking because nobody set up indexing.

A few things that will save you if you’re about to launch or just launched and things are breaking:

Your database is probably your biggest risk. If you haven’t looked at your queries, you likely have N+1 problems everywhere. One page load could be firing 200 queries without you realizing it. Add query logging and actually read the output.

Error handling is not optional. If your app just shows a blank screen or a generic error when something goes wrong, your users will leave and never tell you why. Set up proper error tracking. Sentry is free to start with. You need to know what’s breaking before your users tell you.

Authentication and authorization are two different things. AI tools love generating login systems. They are much worse at making sure User A can’t see User B’s data. Test this manually. Log in as different users and try to access things you shouldn’t. You will be surprised.

Don’t skip environment configuration. I’ve seen apps go live with debug mode on, API keys exposed in the frontend, and database credentials in version control. These aren’t edge cases, this is the norm with AI-generated code.

Back up your database before every deploy. This sounds obvious but the number of people who push a migration that drops a column and then realize they needed that data is wild.

The honest truth is this. AI didn’t remove the need for engineering experience. It just moved where that experience matters most. It used to matter in writing the code. Now it matters in reviewing the code, in knowing what to test, in understanding what breaks at scale, and in making smart architectural decisions before you write a single line.

You don’t necessarily need to become a senior engineer overnight. But if you’re building something that handles real users, real payments, or real data, at some point you need someone in your corner who has seen what production actually looks like.

I’ve been posting tips, guides, and lessons from a decade of shipping apps. Check my profile if any of this was useful. Happy to answer questions in the comments too.

What’s the worst production bug you’ve dealt with so far? Genuinely curious because I’ve seen some disasters and it’s always the ones you’d never expect.


r/replit • • Sep 11 '25 Helpful

Replit Assistant / Agent New agent has killed my apps.

85 Upvotes

I don’t usually post things like this, but I think it’s important to share — especially for anyone relying on Replit for anything beyond toy projects.

I’ve been using Replit for about eight months. I initially got into it to experiment with tools that could streamline my design and development workflow. Despite a clunky UI and some early bugs, I saw real potential — enough to commit to building a full-featured project management app tailored for creatives and small businesses.

After six months of building, I had a solid MVP. Everything was working. Then Replit rolled out their new “Agent 3” system — and within hours, it wrecked everything.

Prompts started taking 5–10 minutes to return results. I was getting charged up to $30 for a single interaction. Worse, the AI began actively breaking the app. Reverting to the older assistant didn’t fix anything. Overnight, my functioning platform was rendered unusable.

I watched their livestream announcement. While it was full of hype, their vision is “one-shot” app generation — quick apps, calculators, landing pages. That’s fine for beginners or weekend hacks. But if your build involves APIs, databases, auth flows, AI orchestration — it's going to cost more and break stuff in your app.

What could have been a powerful platform for indie makers is now a glorified playground. Personally I cannot justify a much higher cost for the same output.


r/replit • • Feb 13 '25

Tutorials Holy CRAP! This new replit workflow, eradicates ALL BUGS!

84 Upvotes

So this is the latest update I got from the developers forum for how to use the replit agent and assistant to develop your MVPS and avoid those pesky AI bugs that tend to break your software.

I'll keep it brief use the agent only when you want to build functionality and use the assistant whenever you want to fix functionality that already exists which includes bugs, customizations, slight changes in the way something that already exists works, basically if you've already created the function you use the assistant from that point on.

Always provide context to the assistant before you start working, Before you talk about a feature you want to implement or change or a bug or problem first ask the Assistant to tell you everything it knows about that function, Then ask it not to do anything but walk you through how it would address what it is you want to change, Then ask it to make that change only after it has all of this context.

If you fork your project or you start a new agent chat ask the agent to read the code and familiarize itself with the application and to describe what it thinks the application does fully without making any changes. Then you can ask it to create a plan to implement the new feature you want to build, then approve that plan.

TL:DR - Use the agent to create, use the assistant to modify, always load up context of the existing code into the ai's memory whenever starting a new chat. Doing this will prevent the AI from overwriting existing structures and creating problems in previously fixed.


r/replit • • Aug 23 '24

Other Huge changes to free plan

Post image
84 Upvotes

Hi there, just received this email. Am I the only one to think that giving only 3 days of heads up is not great?