Edge & path routing
Manage the proxy between public requests and your application. Keep whole-domain routes and supported exact or prefix paths attached to their intended services.
Open the guideHow it works
Publish the endpoints a service needs and associate them with the correct runtime port. Supported path rules allow applications to share a host across several services.
Migration preserves discovered path-only routes. A host that publishes only selected paths stays path-specific, and unmatched requests do not need an invented catch-all service. Review actual routing conflicts in the migration plan.
What you can do
Service destinations
Connect public addresses to the intended runtime and port.
Path-aware routes
Preserve supported exact and prefix rules.
Routing recovery
Inspect status and retry failed configuration.
Explore more
Ship it your way.
Self-hosted and free, or managed on Openship Cloud — the same workflow either way.