*.service.gravixlayer.ai. No tunnel and no local port forwarding.
Each runtime and port gets a hostname. Open it in a browser, call it from code or CI, or share a short-lived link.
A client calls the public hostname. The edge checks the token, then proxies the request to the server inside the runtime.
1ClientBrowser, SDK, or curlSends a token header or an auth cookie
HTTPS
2Edge{port}-{runtime_id}.service.gravixlayer.aiAuthenticate, strip the token, route
private by defaultTTL 3600 s
proxied
3Inside the runtimeYour HTTP serverFastAPI, Streamlit, or Jupyter
listening on :8000
The token is returned onceYour app never sees the service token
The process inside the runtime must already be listening on the port. Opening a service publishes a route. It does not start your server.
Publish an app
Start a small API in the runtime, open a private URL, then create and list items. Outbound traffic is denied by default, so the example attaches a temporaryallow_all policy. That lets pip install reach PyPI. Prefer a narrower allowlist.
Choose who can open it
Defaults
Private (default)
- Programmatic clients send
X-Gravix-Web-Service-Token: <token>. - Browsers use
browser_url, which hits/_ws/authonce and sets an auth cookie for later page loads and API calls from that origin. - Your app never sees the Gravix service token. The header and cookie are removed before the request reaches the process inside the runtime.
is_public=true / --public)
- No token required. Anyone with the URL can reach that port until expiry or revoke.
- Use only for intentionally open demos. Prefer private for APIs and anything with data.
Open a URL
Call the URL
The SDK handle adds the token header for private services automatically:Revoke a URL
Open it in the console
On the runtime detail page, open the Web Service section, enter the port your server listens on, and open or copy the link. Private links use the same token/cookie model as the API. After expiry, open again for a fresh URL.Keep it private
- Keep private by default — only use
--public/is_public=Truefor deliberate demos. - Treat tokens like secrets — store them in CI secrets; never commit them; prefer
browser_urlfor humans so the token is not left in shared chat after auth. - Short TTLs — use the smallest
expires_in_secondsthat fits the session; revoke when done. - Rotate when leaked —
rotate_token=True/--rotate-tokeninvalidates the previous token and browser cookies. - Bind the server carefully — listen on
0.0.0.0only if you intend edge access; do not expose admin UIs without auth inside the app. - Egress is separate — a web service is inbound HTTPS to a port inside the runtime. Outbound calls from the runtime still follow Limit outbound traffic.
Fix a failed request
Next
Limit outbound traffic
Allow or deny outbound hosts
Run commands
Start servers and install packages inside the runtime
Create Runtime
Create a sandbox to host your HTTP app
Store a credential
Attach a key your server needs