Replit Launches Bring Your Own Cloud for Enterprise Customers

Three ways to bring Replit into your cloud

According to Replit, enterprise teams want to build apps connected to company systems and data, but strict security requirements often mean development and production must stay inside the isolation and control of their own cloud. Replit says it has already expanded its governance and isolation posture with governance tools, separate development and production databases and a single-tenant offering. BYOC is the next step.

The company says the approach gives security and platform teams greater isolation and control while preserving the familiar Replit experience. The three options differ in how much of the deployment and operations work falls on the customer.

• Full BYOC: the full Replit platform and published project hosting in the customer's cloud tenant.
• BYOC for Published Apps: published Replit projects are hosted in the customer's cloud tenant, while Replit manages the platform.
• Image Exports: a way to self-host Replit-built apps in the customer's own cloud.

Full BYOC and BYOC for Published Apps

Full BYOC brings both the Replit platform and published project hosting into the customer's tenant. Replit says the platform includes compute, storage, the file system, integrations and the Agent harness, which powers project building, connectors, scheduled agents, publishing and other knowledge work. The setup relies on Replit's cellular architecture, which groups infrastructure into isolated units called cells. Deploying cells in a customer's cloud is meant to deliver the same Replit experience on the customer's own infrastructure.

Because the Agent harness is part of the cell, Replit says security teams can govern which internal resources it reaches and apply controls to outbound connections. It also guarantees colocation between the harness and compute resources, which the company says eliminates network latency. Replit calls Full BYOC its most comprehensive option and notes that it requires the most involved upfront setup. It is launching as a private preview for enterprise customers.

BYOC for Published Apps is the intermediate option. Replit manages the platform, so there is less operational overhead, while published projects run in the customer's tenant. Administrators control the publishing destination for each Replit Workspace, and builders still click "Publish" as they do today. A production app can connect to private databases in the customer environment, and the backing infrastructure has private endpoints that can be reached through the company network or VPN. Security teams can use their existing cloud security tools to inspect deployed workloads and dependencies.

Replit says it publishes and manages the infrastructure through infrastructure as code, giving the Replit Agent and users primitives such as object storage, caching, message queues and scheduled jobs. Secure tunnels connect Replit to resources in the customer tenant over private networking. According to Replit, tunnels use two layers of encryption (mTLS on the tunnel itself plus mTLS between communicating services) and only communicate outwards, so no publicly accessible ingress is needed. Storage is encrypted, and customer-managed encryption keys (CMEK) let the customer control file contents and revoke access at any time. CMEK is available for customers with an agreement that includes full physical isolation of the Replit Cell. BYOC for Published Apps is in early access.

Image Exports and mixed environments

Image Exports give infrastructure teams a Docker image, a Terraform file and an SBOM to deploy Replit-built applications in their own cloud. Builders still hit "Publish", which starts a customizable review process for security and compliance. The published app does not dial back out to the Replit platform, because the option is intended for customers in restricted environments.

Teams using Image Exports deploy and operate the application with their own tools and processes, and must supply some building blocks Replit normally provides, such as managed auth and connectors. Replit describes it as a fit for customers with highly specialized software requirements who do not need the typical ease of use of Replit, and says the Agent can be customized using Skills and Project Memory. It can be combined with BYOC for Published Apps so admins decide how each project is published. Image Exports are in early access for enterprise customers.

Replit also points to the needs of large organizations. A European and a US business unit may need separate cells, and a research team working with sensitive systems may need a cell in the company's cloud while another team stays in a Replit-managed environment. One cell could also serve as a canary or staging environment.

Which option fits whom

Replit positions Full BYOC for organizations that need both the platform and published hosting in their own cloud, with Replit managing the infrastructure. BYOC for Published Apps suits teams that want hosting in their cloud without the cost of running the full platform there. Image Exports is for teams that need highly customized production infrastructure and are willing to deploy and manage hosting themselves.

All three programs are limited to enterprise customers for now, and interested organizations are asked to talk to Replit's enterprise team to choose a deployment option. The source does not give pricing or general availability dates.