# Replit Buyer's Checklist: Spend, Data, Security and Exit > Before paying for Replit, check budgets that cap all usage, what rollback won't restore, who trains on your prompts, Enterprise-only SSO and refunds. _Source: https://professionalstoolkit.com/articles/replit-buyers-checklist — The Professional's Toolkit · updated November 2026_ --- Is Replit safe to pay for? For most small teams, yes, provided you set it up on purpose. Replit says it holds SOC 2 Type II certification, its development and production databases have been separate since July 2025, and its Agent can only read live data. The risks you carry sit elsewhere. Usage beyond your monthly credits is billed pay-as-you-go unless you set a budget, code rollback never restores production data, and only Pro can opt out of AI training. SSO, SCIM and audit logs are Enterprise only. Each area below comes with a setting or a plan gate you can verify in minutes, before you leave the free Starter plan. **7 / 28 days** — Production database restore window: 7 days by default; Pro can choose up to 28 days - **Hard cap** — A met budget suspends all usage-based services, hosting included - **Pro only** — AI-training opt-out; Enterprise content handled under its agreement - **Enterprise** — Lowest plan with SSO, SCIM and audit logs ## Put a ceiling on Agent spending first Replit prices Agent work by effort: the longer it works on a request, the more credits it spends, and there is no fixed price per prompt. Core includes $20 of usage credits a month, and Pro starts at $100 per month, billed monthly. Once credits run out, Replit keeps billing at pay-as-you-go rates up to whatever budget you have set. Without a budget, nothing stops it. Charges land whenever usage crosses a billing threshold, so two charges in one month can be normal, and your collaborators' Agent work plus your app's visitors all draw on the owner's credits. A budget is a hard cap. Once it is met, Replit emails you and temporarily suspends every usage-based service, including the hosting and databases behind your published apps [1]. That trade-off deserves thought: a tight cap protects your card but can take a live app offline. Usage alerts are the gentler tool, warning you at a spend level you choose beyond your credits. The usage dashboard can lag by up to 30 minutes, so treat it as a recent snapshot rather than a live meter. After a billing hold, deployments do not restart on their own; you publish again. - Set a monthly budget and at least one usage alert on the Billing page before the first prompt. - Stay in Free Mode for chatting and ideas: it is an allowance on Starter, Core and Pro, and on Core and Pro it resets every five hours with a weekly limit. On Core and Pro, when a request needs a paid mode, Replit asks you to approve that one request; Starter must upgrade first. - Remember that Plan Mode is billed too, although Replit says planning uses fewer tokens than writing code. - For an organization, monthly budgets come in steps of $500 a month, and per-user spend limits exist only on Enterprise. - Check the cost each checkpoint shows in the Agent tab. > 💡 **Set the budget before building:** Add a monthly budget and a usage alert on Replit's Billing page before your first Agent request. Without a budget, usage beyond your credits keeps billing pay-as-you-go. ## Know what a rollback will not bring back Replit's post on secure vibe coding says that in July 2025 SaaStr co-founder Jason Lemkin had the Agent delete database data before development and production were separated, and that he restored it fully using Rollback. The same month, separate development and production databases launched in beta for new apps, with existing apps migrated automatically. Today Agent builds against the development copy and reads production only through a replica. At publish, schema changes are applied to production, and Replit warns when a change will drop data in the affected tables. **Code rollback is the trap.** Checkpoints capture files, Agent context and database state, yet a rollback leaves the database untouched by default, can include only the development database, and never restores production data. That takes a point-in-time restore, on by default with a 7-day window, while Pro can choose 28 days [2]. A restore replaces the whole database and cannot move forward again. Moving from Pro to Core cuts the window back to 7 days, and Replit states plainly that recovery is not guaranteed. - Read every data-loss warning at publish; an approved migration cannot be recalled, and renaming via a new column drops the old one with its data. - Turn on scheduled daily backups, which are off by default: Core keeps them 7 days, Pro 7, 14 or 28, and backups use billed storage. - To return code and data to the same moment, restore the database, roll back to the matching checkpoint, then publish again. - A deleted production database sits in a 7-day soft delete, recoverable only through Support. More in our [Replit database guide](/articles/replit-database). > ⚠ **Rollback skips production data:** Rolling Replit code back to a checkpoint never restores the production database; that needs a point-in-time restore within the window (7 days by default; Pro can choose up to 28). ## Decide who may learn from your prompts Replit uses content such as prompts, instructions, context and responses to develop and improve its models and AI features [3]. Pro users can opt out in settings, and that choice covers new content only. We found no opt-out described for Starter or Core. For Enterprise, Replit says it does not use customer content to train its models, subject to the Enterprise agreement, and its Enterprise page adds that handling depends on the agreement, the features used and the model providers enabled. If prompts will carry client data, that gap alone justifies pricing Pro. Two smaller layers deserve a look. Through OpenRouter inside AI Integrations, free model providers may train on prompts and completions. Replit may also share data with advertising partners for personalized ads unless you use its Do Not Sell opt-out, and it reserves the right to access private apps for troubleshooting and safety. Its listed sub-processors for AI models include Anthropic, OpenAI, Google, Baseten and Fireworks AI. - On Pro, switch off Model Improvement on day one. - Keep free OpenRouter models away from sensitive app data. - On Enterprise, read the agreement's data clause, not the marketing page. ## Match the security tooling to your compliance needs Every builder gets Package Firewall, built with Socket and on by default since June 2026, which blocks malicious packages at install time for npm, yarn, pnpm, pip and Go. Level 1 dependency checks cost nothing, and a security scan always runs before publishing, with a setting that blocks critical findings. Paid plans add Agent security scans, billed as Agent work, and Security Agent. Auto-Protect, which prepares patches for new critical dependency vulnerabilities, is off by default, and its fixes are billed like other Agent work. Replit itself says a passing publish check is no guarantee of secure code. Compliance needs a careful reading. Replit says its SOC 2 Type II attestation covers Replit's own controls and does not certify apps built on the platform. Under its shared-responsibility model, your app's compliance with GDPR, HIPAA or PCI DSS is your job, and we found no business associate agreement in the pages we read. Access control is better than older pages suggest: private and password-protected publishing has been open on every plan since May 2026. SSO, SCIM, audit logs and organization-wide rules such as banning public apps remain Enterprise only. - Choose Password protected or Invite only for internal tools at first publish; changing access later means unpublishing. - After publishing, check the published app's secrets in the Publishing pane. - Need SSO for your own staff? Price Enterprise; since May 2026 it can be bought online with an annual credit commitment. > 💡 **Lock down internal tools early:** Choose Password protected, Workspace only or Invite only when you first publish; on Replit, changing access later requires unpublishing first. ## Plan the exit before you need it Code can leave. The Git pane connects a GitHub repository with two-way auto-sync, every app keeps an automatic Git backup, projects download as a ZIP, and the production database is standard PostgreSQL reachable from any compatible client with its connection string. What stays behind is the Replit-managed layer. Replit Auth users are Replit accounts, while secrets, App Storage buckets, connectors and AI Integrations must be rebuilt elsewhere. Even a copy inside Replit leaves secrets, storage, connectors, collaborators and Agent history behind, and the database moves with pg_dump and pg_restore. Hosting the app elsewhere is the thinner part. Only Enterprise Image Exports, in early access, are documented as producing a Docker image, a Terraform file and an SBOM for an app that needs no connection back to Replit. We found no self-hosting guide for Core or Pro apps. Mobile has its own limit: Replit publishes iOS apps through your own Apple Developer account, and Google Play publishing is not supported yet. - Connect GitHub sync on day one, so history lives outside Replit. - Keep a written list of every secret and connector the app uses. - For customer-facing apps, use Clerk Auth, which Replit recommends and Agent picks by default on Starter, Core and Pro. ## Read support, refund and cancellation terms Support scales with the plan. Every builder gets the Community Hub; Core adds AI-powered help for technical and billing questions, with billing escalations to staff; Pro and Enterprise add prioritized access to a support engineer, and Replit's support policy staffs Premium Support Engineers Monday to Friday, 6 am to 6 pm PT. We found no phone or live-chat support for self-serve plans. Support will not debug your application code either, and complaints on Trustpilot cluster around costs and credits, Agent loops, support and locked accounts. Replit's Terms of Service cover Starter and Core and allow full refunds of subscription payments made within 30 days of purchase, limited to the most recent subscription charge. Pro and Enterprise sit under a separate agreement: Pro refunds are handled case by case by Support, and Enterprise fees are non-refundable. Agent and AI usage, other usage charges and domain registration fees are non-refundable on every plan [4]. Never dispute a charge with your bank first. That can lock the account. - Canceling keeps features until the period ends; on Starter afterwards, published apps may go offline and custom domains are disconnected. - There is no trial of Core or Pro, so test on Starter before paying; see our [pricing guide](/articles/replit-pricing). - A free account unused for a year can be terminated with its data; paid accounts are exempt. ## FAQ **Is there a free trial of Replit Core or Pro?** No. Replit offers no time-limited trial of Core or Pro; the free tier is Starter, which is Lite build only and publishes one app whose link goes down after 30 days unless republished. **Can I keep a Replit app's hosting in Europe?** Core, Pro and Enterprise can choose a publishing region, Europe included; free accounts publish to North America. The region is permanent once published, so moving means remixing the project. **Do Replit collaborators need their own paid plan?** No. Collaborators do not need a paid plan, and their Agent work counts toward the project owner's credits. Core invites up to 5 builders; Pro allows up to 15 with pooled credits, and Replit says there are no per-user fees. **Where does Replit run its infrastructure?** Replit says it runs on Google Cloud Platform, with services primarily hosted in the United States and every customer, even on the free tier, in an isolated GCP project. ## The bottom line Replit is a sound purchase for a small team willing to treat it like a cloud bill rather than a flat subscription. Set a budget and an alert, choose the restore window your data deserves, and connect GitHub before the first real user arrives. Pick Pro over Core when prompts carry client data, since only Pro can opt out of training, or when 28 days of restore history matter. Teams that need SSO, audit logs or contractual data terms should price Enterprise from the start. ## Sources [1] Replit plans and pricing — https://replit.com/pricing (2026-11) [2] Replit docs: Data recovery — https://docs.replit.com/features/data-and-storage/data-recovery (2026-11) [3] Replit docs: Model improvement — https://docs.replit.com/legal-and-security-info/model-improvement (2026-11) [4] Replit docs: Billing and refunds — https://docs.replit.com/help/billing-and-refunds (2026-11) [5] Replit documentation — https://docs.replit.com/billing/plans/starter-plan [6] Replit Terms of Service — https://replit.com/terms-of-service [7] Replit Privacy Policy — https://replit.com/privacy-policy