Replit Tunnels: Enterprises Can Connect Replit to Private-Network Databases and Internal APIs via an IT-Run Client (Early Access)
Replit has announced Tunnels, which lets enterprise Replit environments reach private services through a client that IT runs inside the internal network. For now, early access requires contacting Replit.
News date: About 5 min read
Contents
Replit published a blog post introducing Tunnels on November 11, 2026, and updated it on November 20. Tunnels is meant to let enterprise teams connect Replit to real company data and services behind a private network. A private network is an internal company network that is not exposed to the public. According to the post, Tunnels is currently in early access, and you need to contact the Replit team to request it. The post gives no information on pricing, plan tiers or regional availability. Everything described below is Replit's own account.
What is Tunnels?
According to Replit, a tunnel lets a Replit environment connect to services in a private network, such as databases and internal APIs. An API is an interface through which programs exchange data. The connection runs through a client program that IT runs inside the company network. Replit also says Tunnels is fully integrated with its connectors, making it easier for Replit to reach company services securely. Connectors are what Replit uses to link to services such as Stripe and Snowflake. Replit's enterprise controls also include governance tools, separate development and production databases, and single-tenant infrastructure, meaning a compute environment not shared with other customers. There is also a Bring Your Own Cloud option for running Replit in your own cloud.
How do the security model and data flow work?
Replit says IT can choose which services each workspace can reach. This means there is no need to open the whole network or allow public inbound access. Public inbound access means letting an outside network connect directly into the company network. What Replit can read or change is determined by each service's own authentication and permissions. The connection between the Tunnels client and Replit is encrypted and authenticated with mTLS. mTLS is mutual TLS: both ends of the connection verify each other's identity, and the traffic is encrypted. Authentication and TLS for each private service are configured separately by IT. An endpoint is an individual private service that Replit is to be able to reach. All traffic to endpoints passes through Replit's tunnel server and the Tunnels client in the internal network. This traffic includes authentication requests from connectors, tool calls from Replit Agent (Replit's AI agent), and requests from published applications.
How do you get it and set it up? What are the example uses?
| Aspect | What Replit describes |
|---|---|
| Rollout stage | Early access; contact the Replit team to ask |
| Where to set up | Once enabled, create a tunnel and add endpoints in Workspace Settings |
| Internal component | Tunnels client run by IT inside the network |
| Encryption | Tunnel uses mTLS; each service configures its own authentication and TLS |
| Finance example | Accounts receivable review (example connectors: Stripe, Sharepoint, Snowflake) |
| Healthcare example | Finding referral delays (examples: Calendly, DrChrono) |
| Manufacturing example | Material shortage dashboard (examples: NetSuite, Shopify, Databricks, Shippo) |
What does this mean for enterprise workflows?
Replit gives several examples. A team can ask "which accounts need a closer look?" to find customers with outstanding balances or missing documents. A team can also ask which patient referrals are still waiting to be scheduled, to find delays and incomplete handoffs. Replit also says inventory and production records can be used to build a material-tracking dashboard that compares available and required quantities by part number and SKU. These are all demonstration scenarios put forward by Replit.
Frequently asked questions
Can I use Tunnels right now?
According to Replit's post, it is currently in early access, and you need to contact the Replit team to ask. Only once it is enabled can you create a tunnel in Workspace Settings.
Do I need to open inbound connections on the company network?
Replit says there is no need to open the whole network or allow public inbound access. IT chooses which services each workspace can reach, and the connection is made through a client inside the internal network.
Is there pricing or regional availability information?
Replit's post gives no pricing, plan or regional information; confirm the details with Replit.
Found this guide helpful? Share it with someone who needs it
Claude Code 2.1.330: Enterprise Admin Console Sign-In, easel Chart Module, and Scheduled Tasks Extended to 30 Days
Anthropic's Claude Code 2.1.330 changelog lists Enterprise Admin Console sign-in, a built-in easel chart module, scheduled tasks of up to 30 days, and stricter approval for rm commands.
AWS Quick adds chat-built flows, multi-agent answers and Meta ads/Amplitude connectors, available today in all Quick regions
AWS Distributed KV Caching Agent Skill for Self-Hosted LLMs: AWS Says Cost Drops Up to 40% and Time to First Token Up to 80%
Amazon SageMaker HyperPod Slurm Adds Cluster Extensions: Managed Observability and User Management, Available in All HyperPod Regions
Sources
Compiled from the references and verification dates listed above; fares, schedules, product features, and terms can change, so please confirm the latest details on the relevant official website before travelling, booking, or purchasing.