Skip to main content
Services inside a Celesto computer are private by default. This isolation is useful for running agents, notebooks, APIs, and preview apps safely, but it also means you need to expose a service before you can open it in a browser or send a webhook to it. Port publishing creates a public HTTPS URL that forwards traffic to a port inside the computer, so you can preview, test, and share running services without deploying them elsewhere. A port is the numbered address a service listens on. For example, a local development server might listen on port 8000.

When to publish a port

Publish a port when you need to:
  • Preview an app generated by an agent.
  • Share a local API running inside a computer.
  • Receive webhooks during a test run.
  • Inspect a notebook, dashboard, or development server.

Publish a service

The following example starts a simple HTTP server on port 8000, publishes the port, prints the public URL, lists published ports, and then removes the published port.
1

Start a service and publish its port

Start a server inside the computer, publish the port, and open the returned HTTPS URL in your browser.
The publish command returns a public HTTPS URL that forwards traffic to the service running inside the computer.

Inspect published ports

Use the list command when you need to confirm which ports are currently exposed for a computer.
CLI
Each published port includes the internal port, the public URL, and its current status.

Published port fields

integer
Port inside the computer that receives forwarded traffic.
string
Public HTTPS URL for the published service.
string
Current published-port state.

Clean up published ports

Published URLs are intended for short-lived development and testing workflows. Remove a published port when you no longer need external access to the service.
CLI
For short-lived previews, unpublish the port before deleting the computer.

Troubleshooting

If the published URL does not load, check that the service is still running inside the computer and listening on the expected port.
CLI
If the command fails, restart the service and publish the port again.
Treat published URLs as public. If the service exposes sensitive data or actions, add authentication to the service before sharing the URL.
Last modified on July 4, 2026