Product overview
Replit brings project files, an AI development agent and cloud publishing into one workspace. Start with a description of the people using your app, the data it needs and the outcome you want. Agent can plan and implement changes, while the project remains available to inspect and edit. This is useful for prototypes and internal tools when you want more than a chat response or a generated code snippet.
An editor preview and a published app are separate instances. Publishing takes a snapshot of the project files and dependencies; later editor changes need another publish before they reach that deployed version. Choose a publishing option for the workload: a static site, a service that scales with requests, an always-running process or a scheduled task have different operating needs.
Access and spending depend on the feature and plan. Starter has capped Agent chat and Free Mode, while the current billing table reserves full builds and Plan Mode for Core and Pro. Paid Agent work uses effort-based pricing; credits can also be consumed by cloud services and Agent services using paid third-party APIs. A working preview therefore does not establish the final running cost or that an application is ready for public users.
What Replit offers
- 01Describe an application in natural language and work with the resulting project code in the browser.
- 02Use Plan Mode on an eligible plan to review tasks and approaches before code or data changes.
- 03Choose Free Mode within its allowance, or confirmed paid work in Power or Max; enterprise workspaces use their own Auto and administrator model controls.
- 04Inspect changes through Agent checkpoints, the visual Git pane, Git CLI and individual file history.
- 05Publish a separate application snapshot with domain, monitoring and deployment settings.
- 06Review checkpoint costs and combined AI/cloud consumption in the usage and billing views.
A practical workflow
- 01Define one user journey, the required data and a concrete acceptance test before asking Agent to build.
- 02On an eligible plan, review a plan first; check the selected mode, allowance and spending controls before approving paid work.
- 03Build one feature at a time, inspect its files and checkpoint changes, and test the actual inputs, error paths and permissions.
- 04Keep meaningful Git commits. Before rollback, check its scope and whether optional database restoration is intended.
- 05Review Publishing settings, sharing, runtime costs and dependencies. Publish the chosen snapshot and verify the separate public application.
Summary based on source material; product claims have not been independently tested.
What makes it different
Compared with an assistant attached only to an existing editor, Replit combines the project workspace and publishing workflow. That reduces the number of separate tools to set up, but it does not remove code review, application testing or decisions about data, access and operating costs.
Who should consider it
- A small team turning a clearly scoped internal workflow into an application.
- A founder or designer iterating on a prototype that needs editable code.
- A developer who wants browser access plus Git history and managed publishing.
What to verify
- Starter does not include every building feature; confirm full-build and Plan Mode access rather than assuming all Agent capabilities are free.
- Paid-path Plan Mode can incur reasoning charges without changing code; some Agent service APIs and cloud usage also draw from credits.
- The current publishing guide limits published-app access controls to Pro and Enterprise; private project access is a separate question.
- Checkpoints support optional database restoration, but are not evidence that every external service or production data system will be rolled back.
Frequently asked questions
Is Replit Agent free?
There is capped Starter access and Free Mode within plan allowances. Core and Pro also have Free Mode allowances, while confirmed paid actions use Power or Max and effort-based pricing. Check current usage and plan access instead of assuming an unrestricted free builder.
Can planning cost money even without a code change?
Yes. The billing guide says the paid path can charge for Plan Mode reasoning even when it changes no code. Agent services using paid third-party APIs and published cloud resources can contribute additional consumption.
Does saving an editor change update the live app?
Not by itself. Publishing creates a separate snapshot of the files and dependencies. Publish again to move later changes into that running version, then test the published URL.
Do checkpoints replace Git or restore everything automatically?
They complement Git and preserve more development context. Database restoration is optional during rollback. Keep manual commits and check the affected data and external integrations before choosing a checkpoint.
Is a private project also a private published app?
Do not treat those settings as equivalent. Review the published app’s Sharing settings. The current publishing documentation reserves published-app access controls for Pro and Enterprise.
Explore related tasks
Product facts were checked against the official product website or its first-party documentation on Nov 6, 2026.
