Overview
Expose a local service through a public Tubu domain. Start with HTTP, or use a TCP tunnel for SSH and databases.
What is Tubu?
Tubu connects a service on your machine or private network to the internet. The publisher CLI opens an outbound connection to the relay. You do not need a VPN, public IP address, inbound firewall rules, or router port forwarding to publish a service.
Use it to share a development app, receive webhooks, or reach an SSH server or database from another machine. The machine that runs the CLI must be able to reach the target service.
Choose a tunnel
| Type | Use it for | How callers connect |
|---|---|---|
| HTTP | Web apps, APIs, webhooks, WebSocket and SSE. | A public HTTPS URL in a browser or HTTP client. |
| TCP | SSH, PostgreSQL, MySQL and other TCP services. | Run npx tubu-cli forward, then point the application at its local listener. |
WebSocket and SSE use HTTP tunnels. SSH and database access use TCP tunnels. A TCP domain is not a public raw TCP port.
What you can configure
- Multiple HTTP and TCP tunnels in one YAML file.
- HTTP or HTTPS targets, HTTP path routing, path rewrites, and a target
Hostheader set automatically. - Optional shared secret protection for HTTP requests and WebSocket upgrades.
- Third level domains such as
app.tubu.dev, and reserved fourth level domains such asapi.team.tubu.devon eligible plans.
HTTP tunnels support HTTP/1.1, WebSocket Upgrade and SSE. Native HTTP/2 and gRPC are not supported.
Find your next step
- How it works explains the connections and security boundaries.
- Guides provide complete examples for specific tasks.
- CLI reference lists commands and options.
- Configuration reference describes the YAML format.
- FAQ helps with common questions and errors.
- Glossary defines the terms used in these docs.