Replit for Teams: Seats, Pooled Credits and Enterprise Controls

Replit sells team building by the account, not the seat. Core costs $20 per month billed monthly or $18 per month billed annually^[1], and it lets one account invite up to five builders into a workspace with no separate team subscription. Pro starts at $100 per month, billed monthly, for $100 of credits, and raises the ceiling to 15 builders who draw on one pooled balance. Past 15 builders, or once you need SSO, SCIM and audit logs, the answer is Enterprise, custom priced and sold online to any organization since May 2026. For most small teams Pro is the working plan, while Core suits up to five people who can live with one background task and no viewer seats.

The old per-seat Teams plan is gone, folded into Pro from March 2026. One rule shapes every team budget on what replaced it. Collaborators' Agent work, plus everything a published app consumes, comes out of the account owner's credits and then pay-as-you-go usage. Nobody on the team gets a separate bill. That single fact explains most of the settings below, from budgets to who is allowed to pick the expensive Agent modes.

Five builders, fifteen, or the whole company

The step from Core to Pro is mostly a step in team capacity. By our arithmetic, Pro with $100 of credits costs $80 a month more than Core on monthly billing and $72 a month more on annual billing, for $80 more in monthly credits. What the money really buys is room: ten parallel tasks instead of one, viewer seats, the option of a database restore window of up to 28 days instead of the default seven, at the cost of more billed storage, credits that roll over for two months, and a human support engineer.

The thresholds are simple. A sixth builder forces Pro, because Core stops at five collaboration seats. A sixteenth builder, or more than 50 viewers, forces Enterprise^[2]. Larger credit options add usage, not seats: Pro with $250 of credits a month, $225 per month billed monthly, still stops at 15 builders. On refunds, Replit's Terms allow full refunds of Core subscription payments within 30 days of purchase, Pro refunds are handled case by case by Support, and usage, Agent and domain charges are non-refundable.

One credit pool, and the owner pays for it

On Pro, every builder in the team workspace spends from the same pooled balance, with budget controls held by the account admin. Pooling is a Pro feature; Core's builders share a team workspace, but the docs reserve pooled credits for Pro^[3]. The charge lands in one place either way. When a collaborator prompts Agent, the cost counts toward the project owner's credits, and so do compute, requests, the production database and AI Integrations used by a published app. Visitors never pay Replit. The owner does.

That makes a budget the first setting a team lead should touch. Alongside usage alerts, a monthly budget acts as a hard cap: once it is met, Replit emails you and temporarily suspends all usage-based services, hosting and databases included, as our pricing breakdown explains. Organization budgets, a monthly cap, come in increments of $500 a month and need an organization admin or owner to set them. What Core and Pro cannot do is cap one person. Per-user spend limits that override group and workspace defaults are Enterprise only, so one eager teammate on Pro can drain the pool for everyone.

Settings, by contrast, are personal. Mode, model, Effort, Plan Mode and auto-approve belong to each user, so a teammate who switches to Max leaves your defaults alone while spending more of the shared balance. Agent requests are priced by effort, and Replit gives no fixed price per prompt. Free Mode softens the bill: on Core and Pro it lets builders chat and build without spending credits, inside an allowance that resets every five hours under a weekly limit. Agreeing which jobs justify Power or Max is the cheapest team policy available.

Roles, access and who can publish

Every account has a personal workspace, and paid plans can open team workspaces, where members see all projects and an admin manages access centrally instead of project by project. Invitations come with three roles. A Member sees the other members and creates apps and projects; a Guest reaches only the apps shared with them; a Viewer gets read-only access. Viewer seats come with Pro (50 included) and Enterprise; Core has none. Core and Pro have a single account admin and no separate workspace admin. Projects created inside organizations have been private by default since June 2025, so viewers need explicit access to each new one.

Two habits save trouble later. Collaborators can read a project's chat history and Agent memories, which matters if anyone pasted customer details into a prompt. Moving a personal app into the team workspace is irreversible, and linked account secrets do not travel with it. When a downgrade cuts seats, the most recently added collaborators keep access and the projects of anyone removed transfer to the account admin, so nothing is orphaned.

Publishing access is the other lever. Since May 2026 every plan can publish an app as password protected, Workspace only or Invite only instead of public. The last two require visitors to sign in through Replit, while password-protected visitors need no account, and changing access means unpublishing first. That puts a private internal tool within reach on Core. Only Enterprise can force every new app private, ban public apps outright or make members wait for an admin's approval before they publish.

Building side by side with Agent

Agent 4, launched in March 2026, was designed around parallel work. Each task runs in an isolated copy of the project and moves across a shared Kanban board through Draft, Active, Ready and Done, and nothing touches the main project until someone applies it. Core runs one background task at a time, Pro up to ten and Enterprise up to 64; extra tasks wait in a queue. Replit says about 90% of merge conflicts resolve automatically (March 2026), a vendor figure rather than a promise. Canceled tasks cannot be restored.

Shared setup is split by plan. Workspace skills come with every paid plan, and on Core and Pro any member can manage them, while workspace custom instructions need Pro or Enterprise. Connectors are managed workspace-wide by the account admin on Core and Pro, who sets up a connection once for builders to use; deleting one removes it for everybody. On Pro, AI Integrations stay off until an organization admin switches them on, and their usage bills to the organization account. Only Pro lets you choose the region of the workspace itself.

Where the Teams plan went

Buyers searching for the old Teams plan will not find it on sale. Replit announced in February 2026 that Pro would replace it, and existing Teams customers were upgraded to Pro at no extra cost for the rest of their term, with migration starting in March 2026. Per-seat billing went with it. Help pages about prorated seat prices and seat removal describe the legacy plan, and Replit says that after migration Pro carries no per-seat fees. An older page says canceling deletes the organization and its apps; since August 2025 organizations can cancel without deleting it.

When Enterprise becomes the plan

Enterprise is where identity and oversight live. SAML SSO works with Microsoft Entra ID, Google Workspace, Okta or another provider, and once it is on, everyone with an email on a claimed domain must sign in through it. SCIM provisions and deprovisions members from the identity provider and maps its groups to workspace roles. Audit logs cover deployments, access, secrets, connectors and Agent activity, are kept 30 days by default and can stream to Datadog, Splunk or Amazon S3. None of these exists below Enterprise.

Governance reaches further than sign-in. Admins can require private deployments, mandate security scans before publishing, pin a publishing geography, ban ZIP export of source code and choose which model providers each workspace may use. Custom groups, per-user spend limits, an Admin API in beta and an Analytics Dashboard that splits spend by member, team and app are Enterprise only too. Our buyer's checklist walks through which of these a smaller team can safely do without.

Buying no longer needs a call. Since May 2026 any organization can buy Enterprise on the website by picking an annual credit commitment on a slider; each dollar becomes a dollar of pooled credits, seats are unlimited by default, usage past the commitment is pay-as-you-go, and payment by card or ACH is annual and upfront^[4]. Deals over $200K in spend, or custom contract terms, still go to sales. Upgrading moves team workspaces and their apps across with published apps staying live, though the personal workspace stays behind.

Two trade-offs come with the move. Enterprise workspaces lose Free Mode and get a single Auto mode instead, so everyday chat no longer runs inside a no-cost allowance. On training, Replit may use prompts and generated content to improve its models; Pro can opt out, and Enterprise content is handled under the Enterprise agreement. Support climbs too: Replit's support policy staffs Pro's support engineers Monday to Friday, 6 am to 6 pm PT, and self-serve Enterprise gets a dedicated Account Manager from day one.

The bottom line

Choose by headcount first, then by control. Up to five builders who can share one background task fit on Core, while a team that needs viewers, parallel Agent work, a pooled balance or a sixth seat belongs on Pro, which starts at $100 per month billed monthly. Set an organization budget on the day you invite people, because collaborators' paid Agent work and every visitor draw on the owner's credits. Move to Enterprise when you pass 15 builders or 50 viewers, or when SSO, audit logs and per-user limits stop being optional.