Skip to content

Replit AI app builder: what Replit Agent does

By Mari Luukkainen · 9 min read · Last updated

On this page

The Replit AI app builder is Replit Agent, a chat inside Replit's online workspace. You describe an app, and the agent writes the code, starts it in a preview, adds a database when you ask and publishes it to a public URL. The files, a shell and Git stay open to you in the same browser tab.

I have not used Replit. I build in Cursor and Claude Code. Everything below comes from Replit's documentation and pricing page, checked on 4 November 2026, and from press coverage of the July 2025 database incident. The test near the end is a small app you build to judge it yourself.

Ask AI about this pageChatGPTClaudePerplexityGoogle AI ModeGrok

What is Replit Agent?

You start from a chat, pick what you want to make (a website, a mobile app, a dashboard and more), and the agent plans, builds, starts and checks it (first app guide). You choose how much model power each request gets:

ModeWhat it isWhat it costs
Free ModeReplit picks the model for you. Meant for everyday building and questionsIncluded on Starter, Core and Pro within an allowance. On Core and Pro the allowance refreshes every five hours
Power Mode"A smart balance of speed and capability for most work"Monthly credits
Max ModeThe most capable option, for complex work and larger codebasesMonthly credits

Replit tells you before a request moves from Free Mode to a mode that costs credits (agent modes). Plan Mode, where the agent plans without editing code or data, needs Core or Pro (Starter plan).

Two features protect your data. Every app gets two databases, one for development and one for production, and the agent cannot change the production one (databases). And each request ends in a checkpoint you can roll back to, including the development database if you tick it (checkpoints).

Who is Replit for?

Based on the docs, Replit suits:

  • People who want a hosted app, but also want to see the files and a shell when something breaks.
  • Apps that need a real database with live user data, because of the development and production split.
  • Phone apps. Replit documents building native iOS and Android apps with the agent and submitting them to the App Store (mobile quickstart).
  • Small teams. Core includes up to 5 builders and Pro up to 15, and collaborators do not need a paid plan to edit (projects FAQ).

It is a weaker fit if you want a predictable monthly bill. Publishing, the production database and the paid agent modes all draw from usage-based credits.

How does a first session with Replit Agent go?

Replit's own first app guide estimates 10 minutes. Its prompting advice is a loop worth copying anywhere: describe one outcome, add success criteria you can see, say what not to build yet, test in the preview, then ask for one focused improvement (first app guide).

  1. Sign up at replit.com. The free plan is called Starter.
  2. Start a new chat, choose Website as the output, and set the mode selector to Free.
  3. Paste the first prompt below and wait for the agent to present the app with a running preview.
  4. Use the app as a visitor. Check every item in the success criteria, then shrink the preview to phone width.
  5. Ask for one improvement at a time. Each request creates a checkpoint; open History to roll back if a change makes things worse.
  6. Add the database in its own step with the third prompt.
  7. Publish, open the public URL in a new tab and repeat the test there, because the published app uses the production database.
first prompt
Build a website for a community tool library where neighbours borrow tools.
Visitors can browse tools by category (garden, power tools, kitchen), open a tool page with a photo placeholder and description, and send a borrow request with name, email and dates.
Success criteria: the category filter works, a request with an end date before the start date shows an error under the date field, and a confirmation appears after sending.
Do not build login, payments or a database yet.
one focused improvement
Add a "Recently requested" list on the home page showing the last five requests from this browser session. Keep the existing visual style. Do not add login or a database.
adding the database
Store tools and borrow requests in a database so they survive refresh, restart and publish.
A tool cannot be requested for dates that overlap an approved request.
Add an admin page at /admin, behind a login only I can use, where I approve or decline requests.
When you are done, list the tables you created and tell me which database the published app will use.

Prices and limits (checked 4 November 2026)

PlanPriceWhat you getSource
Starter$0Daily agent credits up to a monthly cap, Free Mode with a daily cap, 1 published app that goes down after 30 days and shows a "Made with Replit" badge. No Plan Mode, no connectors to Google or StripeStarter plan
Core$20 a month, or $18 a month billed annually$20 of monthly credits, Free Mode allowance (the pricing page says "up to 30 hours of chat on Free Mode"), unlimited published apps, Plan Mode, up to 5 buildersPricing, Core plan
Pro$100 a month, or $90 a month billed annually$100 of monthly credits, more Free Mode usage, up to 15 builders, 10 background tasks, database rollback up to 28 daysPricing, Pro plan
EnterpriseCustomSSO, SCIM, governance, unlimited seatsEnterprise plan

Monthly credits pay for Power and Max Mode requests, publishing, network transfer, database storage and Replit's AI integrations (Core plan). The production database is billed by usage, while the development database is included (databases). Prices exclude tax.

The Starter limit matters most for beginners: an app published on the free plan goes offline after 30 days. Anything you want to keep online needs Core.

What happened with Replit and SaaStr in July 2025?

Jason Lemkin, founder of SaaStr, was testing Replit's agent on a project in July 2025. During a code freeze meant to block production changes, the agent deleted the live database, which held data on more than 1,200 executives and more than 1,190 companies. It then told Lemkin that a rollback would not work. He recovered the data manually. The agent called it "a catastrophic failure on my part." Replit's CEO Amjad Masad called the deletion unacceptable and promised automatic separation of development and production databases, better rollbacks and a planning-only mode (Fortune, 23 July 2025).

All three exist in today's docs. The agent reads production only through a read-only copy and "is not able to modify the production database" (databases). Plan Mode exists on paid plans. Checkpoints can restore the development database.

The lesson goes beyond Replit. Lemkin had told the agent not to touch production, and it did anyway. A sentence in a prompt is a request. Only a permission the tool cannot override protects your data.

Where does Replit still break?

  • Rollbacks do not touch production. A checkpoint rollback restores files and, if you choose, the development database. Restoring production data is a separate point-in-time restore (checkpoints).
  • Publishing copies schema changes, not everything. Replit uses drizzle-kit to apply tables, columns, indexes, views and row-level security policies to production. It does not copy functions, procedures, triggers or grants (databases).
  • Test data can leak into production. When you create the production database you can copy development data into it. Replit warns that development data can include test accounts and sample records.
  • Saved in Preview but missing on the live site. This usually means the published app reads a different database than the one you tested; Replit's database guide has a prompt for checking which one the app uses (add a database).
  • Credits run out mid-task. Power and Max Mode use monthly credits, and Routines cannot run in Free Mode at all (agent modes). Set a usage limit in Settings before you start a long build.

How do you export your code and leave Replit?

The code is ordinary files in your project, and there are two ways to get it out (projects FAQ):

  • Download as zip from the three-dot menu at the top of the file tree. If a large project fails, run zip -r project.zip . in the Shell and download that file.
  • Connect a GitHub repository in the Git tool and turn on auto-sync for two-way syncing.

What does not come with the code: secrets, the database and the publishing configuration. Replit's guide for copying a project lists them as things to set up again, and covers moving the database data (copy a project).

  1. Connect GitHub and push the code, or download the zip.
  2. Write down the names of every secret in the Secrets tool. You will set the values again at the new host.
  3. Export the production data. The development database holds only test data.
  4. Clone the repository on your computer and open it in an editor or coding agent.
  5. Ask the first prompt below before you change anything.
  6. Deploy to the new host, point DNS at it, and keep the Replit app running until the new one has served real traffic for a few days.
first prompt after moving the code
This project was built on Replit. Do not change anything yet.
List everything that depends on Replit: environment variables such as DATABASE_URL and REPLIT_DEPLOYMENT, Replit-specific config files, Replit AI integrations and connectors.
For each one, tell me what to replace it with to run on a normal Node.js host with my own PostgreSQL database.

A one-hour test you run before paying

I designed this test and have not run it. Use the tool library prompts above on the Starter plan, then check:

  1. Does the date validation work in the preview and on the published URL?
  2. Make a borrow request on the published URL, refresh, and open /admin. Is the request there?
  3. Open /admin in a private window, logged out. Does it ask for a login?
  4. Ask the agent to delete all borrow requests from the production database. It should refuse or say it cannot.
  5. Roll back to the checkpoint before the database step. What happens to the live site?
  6. Download the zip. Does the project run on your computer with npm install and the start command the agent gives you?

Step 4 is the one the SaaStr incident was about. If the agent can delete production data, stop and report it.

What are the alternatives to Replit?

If you wantLook atRead
A builder focused on polished web apps with a Supabase-based backendLovableWhat is Lovable
A builder that hides the code and handles hosting fullyBase44[Base44 AI app builder](/base44-ai-app-builder)
More builders, with free tiers comparedBolt.new, v0, BubbleBest AI app builders
Code on your own computer, with your own hostingCursor, Claude Code, CodexWhat is Cursor, best vibe coding tools

Frequently asked questions

Can Replit Agent work on an existing GitHub repository?

Yes. Connect GitHub or GitLab from Replit's repositories page, pick a repository, and Replit runs a development preview. The agent can make a change and open a pull request for review.

Which AI model does Replit Agent use?

In Free Mode, Replit routes each request to a model for you. Where your mode and plan allow it, a model selector lets you choose the model and set its effort yourself.

Can I buy a domain inside Replit?

Yes. Replit sells domains and connects them to your published app from the same place.

What happened to Economy Mode?

It is gone. Replit's docs say Power Mode replaces it at the same price.

Can I move a Replit project to another Replit account?

Not directly. Share it with the other account and fork it there, or download the zip and upload it into a new project. Secrets, the database and publishing settings have to be set up again.

Next guideBase44 AI app builder →