Replit brings its coding platform into customer clouds

Replit has introduced BYOC, a set of deployment options that places some or all of its coding platform inside a customer’s cloud account. The three options support Amazon Web Services, Google Cloud, and Microsoft Azure, with availability ranging from private preview to early access.

Large companies often restrict developer tools that process source code, connect to private databases, or run production workloads on vendor infrastructure. Replit’s new model lets security and platform teams apply their existing identity, network, encryption, logging, and residency controls to Replit-built applications.

Control comes in three tiers

Full BYOC is the only tier that places the development platform and agent harness inside the customer account. BYOC for Published Apps addresses runtime residency while leaving development under Replit’s management. Image Exports provides portable deployment artifacts for teams that already operate their own container delivery pipelines.

Cells move the platform boundary

Full BYOC uses Replit’s “cellular infrastructure,” which packages platform services into isolated units called cells. Deploying a cell in the customer’s tenant moves the coding environment, compute, and agent harness closer to the internal systems they access.

Connections use outbound-only secure tunnels initiated from the customer environment, so the Replit tunnel does not require publicly accessible inbound network access. A public application may still need its own ingress. Replit says traffic receives two layers of mutual TLS: one for the tunnel and another between communicating services. Mutual TLS encrypts traffic and requires both endpoints to verify each other’s certificates.

Replit also supports customer-managed encryption keys. The customer controls the key and grants Replit permission to use it, retaining the ability to revoke access. Key revocation can block decryption of protected data, giving security teams control over continued access.

Deploying the agent harness inside the cell gives administrators control over the internal resources and outbound services it can reach. Colocating the harness with its workspace also reduces the network latency involved when the agent reads files, edits code, or runs commands.

Enterprise adoption drives the timing

Cloud data platforms and AI infrastructure vendors increasingly offer deployments that keep workloads within customer-controlled accounts. Replit has followed the same path as it pursues regulated and security-sensitive organizations, alongside a Databricks integration with Lakebase support and new governance tools.

A reported incident in which Replit’s agent deleted a production database during a coding session adds context to the launch. BYOC can confine an agent to customer-defined network and identity boundaries. An agent with destructive database permissions can still delete data, so teams need least-privilege roles, approval controls, backups, and tested recovery procedures.

Existing cloud controls can follow the workload

Customer-hosted applications can connect to private databases and internal services without exposing those systems to a vendor-hosted runtime. Security teams can also bring deployed resources into existing cloud logging, vulnerability scanning, and security posture management systems, subject to each tool’s coverage.

The selected tier determines the actual data boundary. Organizations that require source code, workspaces, prompts, and the agent harness to remain in their account need Full BYOC. Teams concerned primarily with production runtime placement can use BYOC for Published Apps, while Image Exports fit established container and infrastructure-as-code workflows.

Checks before production

• Data flows: Document which source code, prompts, telemetry, logs, artifacts, and support data can leave the customer account under each tier.
• Network paths: Verify tunnel destinations, ports, private DNS requirements, application ingress, and outbound filtering controls.
• Identity: Define the agent’s cloud and database roles, credential rotation process, approval boundaries, and emergency revocation procedure.
• Operations: Assign responsibility for upgrades, security patches, backups, disaster recovery, incident response, and support access.
• Commercial coverage: Confirm pricing, supported regions, capacity limits, service-level commitments, and the route from preview to general availability.

Policy takes over at Publish

Developers using Full BYOC or BYOC for Published Apps can continue building in Replit and use the normal publishing workflow. Administrative policy determines whether the resulting application runs in Replit’s cloud or the company’s tenant. Image Exports instead hand the application artifact to the organization’s existing deployment pipeline.