[Feature Request] Multi VM Port Bridging.

[seanfilimon]

**Description: **

CodeSandbox SDK that enables multi-VM port bridging.

The goal is to allow multiple VMs to communicate with each other using ports or some type of private network interface, without requiring ports to be publicly exposed or accessed through direct URLs.

Motivation / Use Case:

Managing multiple running applications in a single VM can quickly become taxing.

Scaling a workspace across several VMs is currently difficult when each service requires manual port management or CLI-based orchestration.

A private, VM-to-VM networking solution would make it much easier to run and scale complex applications that rely on multiple services (e.g., microservices, databases, backend + frontend combos).

Proposed Solution (High-level idea):

Introduce a private networking layer between VMs.

Allow exposing ports internally to other VMs in the same workspace.

Provide SDK APIs for establishing and managing these connections programmatically.

Benefits:

Simplifies scaling multi-service environments.

Eliminates the need to expose unnecessary public ports.

Provides a smoother developer experience when working with distributed systems.

Implementation:

You are already able to expose ports publicly. What this would do is allow us to whitelist a port potentially for use with a specific IP or Sandbox.

[christianalfoni]

Hi @seanfilimon!

This is a very exciting idea and feature, but it will require a bigger effort on our side to make it work securely and creating a general good DX around it.

We also have SSH on the roadmap that would provide tunneling.

But before all this we are working on a new infra for the SDK 😅

So first infra, then SSH and then we would be able to look at any additional requirements on top of that.