Sixter Documentation

Sixter is a secure tunneling and deployment platform. Expose localhost or a private server to the internet with automatic HTTPS, custom domains, one‑click deployment, and team coworkspaces.

Tunnels

Forward a public URL to a local port — HTTP & WebSocket.

Deployment

Push a folder; Sixter builds, runs and serves it over HTTPS.

Tunnel Mode

Host apps from a box with no public IP.

Coworkspaces

Teams, roles and a push → review → deploy flow.

Installation

Linux:

curl -fsSL https://sixter.in/sixter_amd64.deb -o sixter.deb
sudo dpkg -i sixter.deb
sixter help

Windows / macOS: download the CLI from your dashboard and add sixter to your PATH. The CLI ships with its companion binaries (tunnel client, repo tools) in the same folder.

sixter login

The CLI prints a URL and a short code. Open the URL on any device, approve, and credentials are saved to ~/.sixter/config.yaml. On an SSH‑only server use sixter login -no-browser. Every account gets two permanent subdomains: <name>.sixter.in for tunnels and <name>-repo.sixter.in for the repo dashboard.

Expose localhost with a tunnel

sixter tunnel -port 3000

Forwards https://<name>.sixter.in to http://127.0.0.1:3000. HTTP and WebSocket both work, with automatic HTTPS. See the step‑by‑step tutorial: expose localhost to the internet.

Custom domains & automatic HTTPS

Point your own domain at Sixter and it terminates TLS for you — no certificate management. For a subdomain, add a CNAME to sixter.in; for an apex domain use an A record to the gateway (or your provider's CNAME flattening). Certificates are issued and renewed automatically via Let's Encrypt.

Deploy a project

sixter repo --server <name>-repo --project myapp

Uploads the current folder to your repo server, which auto‑detects the stack (Node, Python, Go, static, …), builds it, runs it as a service, health‑checks it, and rolls back automatically if it fails to start.

Tunnel Mode — host without a public IP

If your server sits behind NAT with no public IP, switch a project to Tunnel Mode. The Sixter gateway accepts traffic for your domain and forwards it down the server's outbound tunnel to your app — TLS is terminated at the gateway. No port‑forwarding, no public IP required.

Team coworkspaces

Group related projects into a workspace and invite teammates with roles (lead, backend, frontend, deployment, viewer). Developers enroll and push with the CLI:

sixter project init <token>   # link this folder to a workspace project
sixter push                     # upload your work → pending review

A push is staged, not deployed. A project lead or deployment member promotes it:

sixter project deploy

An activity feed records every deploy and change for audit.

Firewall & security

Every request is inspected at the edge: a WAF blocks SQL injection, XSS, path traversal and scanner probes; optional bot protection blocks scrapers and automation tools; rate limiting and per‑IP banning stop abuse; and a global guard mitigates L7 floods. Sixter's own tooling is always allowlisted.

Get started Compare with ngrok