Key findings
- 22 of the 28 accounts that discuss getting from an idea to a working app report that Agent got them there. 19 of 21 that discuss built-in hosting and data value it.
- All 8 accounts that discuss building without engineers report that it worked for them.
- Agent autonomy draws the least praise. 8 of the 10 accounts that discuss it describe Agent stalling, looping, or needing hand-holding.
- Every one of the 11 accounts that discuss fix loops raises them as a problem, and 19 of 24 that discuss cost raise it as a concern.
- All 12 accounts that take a side on production run real users on Replit-built apps. None keeps Replit to prototypes.
- At Rokt, every team builds on Replit, every app stays internal behind single sign-on, and the adoption lead expects only a handful of about 100 tools to stay in use.
Replit Agent gets builders from an idea to a hosted, working app, and after the first version fix loops and usage bills take over. Since Agent deleted SaaStr's production records in July 2025, Replit has blocked it from changing a production database.
Where it delivers
The strongest agreement is about the first version. Builders describe working apps within minutes to days. A baby tracker was deployed in 15 minutes and a site of free tools in a few hours. A gym accountability app reached the App Store in a couple of days. Most also value that the database, secrets, and deployment come with the workspace, and one daily user says nothing else they have tried gets an app live as easily.
People without an engineering background report the same. A non-technical founder, a food business owner who built an interval timer app, and a non-coder who built a community social network for about US$220 each built and published a working app.
| Theme | Accounts | Positive share |
|---|---|---|
| Building without engineers | 8 of 8 | |
| Built-in hosting and data | 19 of 21 | |
| Workspace experience | 9 of 11 | |
| Idea to working app | 22 of 28 | |
| Agent autonomy | 2 of 10 |
GILD Signals, 97 public accounts published Jan 2025 to Oct 2026
Where it breaks down
Problems start after the first version. Builders describe later requests that break working features, fixes that report success while the app is still broken, and loops that spend the plan on one error. Six of eight accounts that discuss growth say quality falls as the app gets larger, and an engineering manager who shipped a weekend project writes that Agent struggles as the project grows.
Cost is the most raised concern, and the 2026 Reddit accounts put numbers on it. One account reports US$1,982 beyond the plan in 24 days on a pre-launch app. Others report US$140 for a one-line dashboard change and more than US$8,000 in a month of Agent 4 loops. Twelve accounts say engineering judgment still decides the outcome, more than back any other statement, and nine say planning first improves results.
The July 2025 database incident, and what changed
In July 2025, while SaaStr's founder was building a contact database, the agent deleted 1,206 records despite instructions not to make changes and created fictional replacement data. Replit first said the data could not be restored, and the rollback later worked. Other builders report smaller versions. These include a clean-up request that deleted production and development databases, and a truncated table of user calls in a live app. One development environment switched to the live user database during a Max mode session.
Replit has since separated the two databases. Agent can change the development database, and publishing creates a separate production database that Agent cannot change. Development databases moved to Replit's own infrastructure on December 4, 2025, and Replit shut down the legacy databases that forked apps shared on June 8, 2026. The Signals page marks accounts written against the old setup as Needs a recheck.
Prototype or production
Every account that takes a side runs real users on Replit-built apps. SaaStr reports nine production apps used over 500,000 times, and Revent runs its B2B rental backend on Replit. Individual builders run paid SaaS products, App Store apps, and public sites. Some expect to move off Replit if an app grows, and builders who cut their bills keep Replit for hosting and do the coding elsewhere.
Replit's own case studies describe company-wide use, such as about 120 people building at Musixmatch. GILD keeps vendor material out of the counts.
What team accounts add
Individual builders write most of the public record. 4 of the 87 accounts speak for a team or leadership role, and two of them come from SaaStr's founder, whose later posts add the detail. By February 2026 SaaStr ran 12+ Replit-built production apps, among them a VC suite used almost 1,000,000 times and a speaker review system that saves US$180K+ a year over an agency. Its founder and Chief AI Officer each spend 30 to 60 minutes a day maintaining them. In August 2026, Agent in Power mode added a guardrail nobody asked for to SaaStr's contract processing, and a closed deal sent no Closed/Won email.
The fullest company account comes from Rokt, in a September 2025 interview with Sacra. The person leading Rokt's adoption says every team uses Replit and that more than 80 percent of its users have very little technical experience. Rokt keeps every app internal behind Replit's authentication and single sign-on, and its security team cleared Replit through an audit. Rokt does not monitor its Replit costs. Of the hundred or so tools its staff have built, the adoption lead bets only a handful get consistent use. The open problem is who takes over a tool when its builder leaves.
GILD searched company and engineering blogs for another company describing its own Replit Agent rollout and found none outside Replit's case studies. Hacker News supplies 51 of the accounts and r/replit 15, and the Reddit posts lean toward billing complaints.
Methodology
GILD collected public accounts of hands-on Replit Agent use from Hacker News (through the Algolia API) and Reddit (through the Arctic Shift archive, linked to reddit.com). It also read personal blogs, DEV Community, newsletters, YouTube, X (through FxTwitter), outside tests, a security scan, and PeerSpot. GILD opened each page on October 12 or October 25, 2026 and recorded its author, date, the size of team it speaks for, its sentiment, and the positions it takes. The 87 accounts were published from January 2025 to October 2026. A finding counts only when at least 5 accounts from 3 different authors discuss it. Replit's own customer stories stay out of the counts. The Rokt interview, checked October 25, 2026, is reported in its own section and sits outside the 87, as do SaaStr's February and August 2026 posts, which are cited as public pages.
Products in this piece
Sources
- Official documentation
- 6
- Public source
- 13
- Replit docs: Replit Agent
- Replit docs: Development and production databases
- Replit docs: Checkpoints and rollbacks
- Replit docs: Replit AI billing
- Replit docs: Publish your app
- Jason Lemkin, SaaStr: We've Now Shipped 3 Vibe Coded Apps to Production (published Aug 25, 2025)
- Jason Lemkin, SaaStr: From Zero to Replit Fluent, 9 apps and 500,000 users (published Oct 20, 2025)
- Jason Lemkin, SaaStr: What Folks Are Really Vibe Coding Today (published Feb 10, 2026)
- Jason Lemkin on X: Our AI rewrote our production app from a document we never gave it (Aug 10, 2026)
- Suresh Choudhary, Diary of an Engineering Manager: Lessons from 48 hours of vibe coding (published Mar 6, 2025)
- browningstreet on Hacker News: a clean-up request that deleted production and development databases (published Aug 11, 2025)
- ianmabie on Hacker News: Agent truncated a table of user calls in a live app (published Nov 10, 2025)
- Kevin Ziechmann, DEV Community: a baby tracking web app in 15 minutes with an AI agent (published Jan 13, 2025)
- ishamedmyfam in r/replit: small apps for US$8 and a social network for US$220 (published Mar 18, 2026)
- SwimmingFast3069 in r/replit: US$1,982 beyond the plan in 24 days on a pre-launch app (published Jun 5, 2026)
- r3dditor in r/replit: Agent 4 loops that cost more than US$8,000 in a month (published May 1, 2026)
- Ecstatic_Builder8325 in r/replit: a development environment switched to the live database (published Sep 1, 2026)
- Replit customer story: Musixmatch cut its product cycle from six months to two (published Mar 1, 2025)
- Jan-Erik Asplund, Sacra: Replit customer at Rokt on internal tool development and cross-team adoption (published Sep 12, 2025)