Private networking
Services in a project reach each other over a private network, so your database and internal APIs never need a public port. Wire one app into another as a ready connection.
Service links depend on the runtime. Fleet network administration requires a self-hosted or desktop controller.
Open the guideHow it works
Keep internal services off public routes where the runtime supports private links. Connection wiring supplies the appropriate address and variables to a consuming project.
For registered fleets, verify an existing provider network or prepare managed WireGuard networking. Changes use reviewed plans and dependency checks; cross-server reachability depends on the topology.
What you can do
No exposed ports
Internal services stay off the public internet.
One-click wiring
Inject a DB/service connection into another project as env vars.
Private by default
Expose only the routes you explicitly publish.
Explore more
Ship it your way.
Self-hosted and free, or managed on Openship Cloud — the same workflow either way.