Replit, Inc., based in California, offers Replit Agent, which turns plain-English instructions into working apps with authentication, a database and hosting included.
Apps run on Google Cloud with a PostgreSQL database, and sign-in for your app’s users is handled by Replit Auth or Clerk. We aren’t connected with Replit, and everything below comes from its public documentation and published reporting, as we read them on 6 November 2026.
Whose job is security?
Replit’s security page says “Secure by default” and “You’re already covered”. Its shared responsibility document puts it differently:
Both can be true, because they’re about different things. Replit looks after the platform: servers, encryption and backups of its managed databases. These are marked as your job:
- reviewing the code and managing secrets;
- managing users and access control;
- privacy notices and regulatory compliance, including GDPR;
- penetration testing of your app.
Replit also has a useful way of putting it: “Agent produces working code, but ‘working’ and ‘correct’ are different things.” Its Security Center offers scans at three levels, but it says plainly that “no scan guarantees that your app is secure”.
A few marketing lines need reading alongside the documentation. Auto-Protect is promoted as watching round the clock, but the documentation says both of its settings are off by default.
Who holds the keys
This may be the single most important point on this page for a business:
- In a personal workspace, one person is the sole admin. Others come in project by project as guests.
- Core and Pro have a single account admin, typically the account owner. Separate workspace admins are an Enterprise feature.
- A business handoff means contacting support. That’s the route Replit documents. We found no published process for an owner who has died, left or won’t co-operate.
- Moving to a team workspace is one way. Replit says this transfer is irreversible, and you have to be a member of the team already.
- Collaborators can usually get at secrets. Replit’s documentation says members without the Owner role can’t view secret values directly but can reach them by printing environment variables. So anyone who has had edit access should be treated as having seen your keys. Replace them when someone leaves.
- A private join link gives anyone who holds it edit access, along with the project’s chat history.
The practical fix is to put your apps in a team workspace, on an account that the business controls, using a role email address such as systems@ and not somebody’s personal one. Do it before you need it. Why this matters.
Three defaults to check
- Visibility. “Apps in your personal workspace default to Public.” Changing access on a live app means unpublishing it first, according to the current documentation.
- Location. The geography of a published app can’t be changed after publishing. Free customers publish to North America. The nearest listed option to the UK is the EU, and we found no UK option.
- Backups. Point-in-time recovery of the production database is on by default for seven days, but any plan can turn it off, and daily scheduled backups are off by default.
Getting your things out
Replit is relatively open, as your code is standard code and your database is standard PostgreSQL. It’s manual, though, with a trap in it.
- Code: download a zip, or connect GitHub.
- Data: a database dump needs command-line work. Replit warns that the obvious route exports the development database, while your live data is usually in production. It’s worth checking any backup you think you have.
- Not copied: secrets, connectors, deployments, custom domains, collaborators and Agent history all need recreating.
- Rolling back: “Checkpoint rollback never touches your production database.”
- Sign-in: if your customers sign in with Replit Auth, they’re using Replit accounts. Replit itself advises that Clerk is the better fit for customer-facing or commercial apps.
What has gone wrong publicly
- A deleted database, July 2025. SaaStr founder Jason Lemkin reported that Replit’s agent deleted a production database containing data on more than 1,200 executives, during a code freeze, in a widely followed public experiment. The Register reported that the data was recovered by rollback, even though the agent had said that was impossible. Replit’s chief executive called it unacceptable, and the company began separating development and production databases. Today, Replit says Agent can’t modify the production database.
- Exposed apps across platforms, May 2026. WIRED reported that the security firm RedAccess found more than 5,000 apps with virtually no security across Lovable, Replit, Base44 and Netlify, with no split by platform. The companies pushed back, and WIRED couldn’t confirm that the data was as real or sensitive as it appeared. Replit’s chief executive said public apps being accessible is expected behaviour.
What you can check today
These are the menu names in Replit’s documentation, which can change.
Whose account is it?
Look at the account name, top right, and the workspace selector. If it says Personal workspace, one person is the sole admin.
Who’s in?
Settings, Workspace collaborators. On each app, the Invite button shows who has access, and setting someone to None removes them.
Is the live app public?
Tools, Publishing, then Sharing: Public, Password protected, Workspace only or Invite only.
Which database is live?
Database tool, then the menu next to All Databases, then Production. Look for a recent real record.
Are there backups?
Database, Production, Settings, Advanced, Point-in-time recovery. Make sure it isn’t Disabled.
Run a scan
Tools, Security Center, Run scan. Level 1 is free but covers dependencies only, so a clean result doesn’t say your own code is safe.
Is publishing blocked on critical problems?
Publish, then Advanced: Block publishing of critical vulnerabilities.
Are alerts on?
Settings, Personalization, Email Notifications, and Settings, Advanced for Auto-Protect. Both are off by default.
How we can help
Our audit looks at the parts Replit’s table marks as yours: who can reach what, how sign-in and access really work, and how much depends on one account. Replit lists penetration testing of your app as your job, and while our audit isn’t a certified test, it’s an independent, plain-English look at the things that matter most. See an example report.
Questions
Is Replit safe for a business app?
The platform has a SOC 2 Type II attestation, according to Replit. Whether your app is safe depends on how it handles access and data, and Replit’s own table says that’s your responsibility.
Can Replit’s agent delete my live database?
Replit now separates development and production, and says Agent can’t modify production. However, structural changes you make to the development database are applied to production when you publish, with warnings for changes that remove data, so read those warnings carefully.
Sources
By Selwyn Doling, VibeTend. Last updated 6 November 2026.
