Public tunnels for local work

Put localhost on the internet.

Chiq gives local apps, APIs, webhooks, and TCP services a secure public surface. Start a tunnel, inspect live traffic, replay requests, and keep control without deploying.

Early accessShow CLI
Getting started

Up and running in seconds.

One install, one login. Tunnel HTTP, TCP, static files, readable subdomains, and custom domains straight from your terminal.

$ chiq http 3000
chiq 1.0 - press Ctrl+C to quit

Status: Online
Protocol: HTTP
Forwarded: app.chiq.uz -> 127.0.0.1:3000
Install

Install chiq CLI

Install the CLI from the official install script.

curl -fsSL https://chiq.uz/install.sh | sudo bash
Authenticate

Connect your token

Obtain an auth token from chiq.uz/auth, then authenticate.

chiq auth <your-auth-token>
HTTP

Start an HTTP tunnel

Replace 3000 with the local port you want to expose.

chiq http 3000
TCP

Start a TCP tunnel

Expose SSH, databases, sockets, or internal tools.

chiq tcp 22
Subdomain

Reserve a readable URL

Use a stable subdomain for repeated callbacks.

chiq http 3000 -s custom
Static files

Serve a directory

Publish a local folder through the built-in server.

chiq serve .
Debug

Open the tunnel debugger

Start an HTTP tunnel with live request inspection.

chiq http 3000 --debug
CNAME

Use your own domain

Point your domain CNAME, then start the tunnel.

chiq http 3000 --cname example.com
Core features

Expose, inspect, control.

A focused tunnel workflow: public endpoints, live request context, replay, reserved names, custom domains, and HTTP or TCP forwarding.

Public endpointsTurn a local port into a reachable HTTPS URL for demos, callbacks, previews, and test environments.
Traffic inspectorRead method, route, status, latency, headers, response, and body without leaving your development flow.
Any local serviceForward web apps, APIs, webhooks, SSH, databases, WebSockets, queues, and other TCP services.
Workflow

Terminal speed. Dashboard memory.

Start from the CLI when you need speed. Keep session history when you need answers: what failed, what arrived, which route was slow, and what should be replayed.

$ chiq http 4242 --name webhooks
public https://webhooks.chiq.uz
local localhost:4242
policy auth, replay, request log
200POST /webhooks/order.created47ms
302GET /oauth/callback18ms
101TCP / ssh-forwardlive
500POST /webhooks/retry-me91ms
Traffic controls

Rules before traffic reaches your code.

Public does not have to mean uncontrolled. Attach simple policies to keep local services reachable only in the way you intended.

Access guardProtect previews with tokens, basic auth, or allowed client ranges.
Route shapingRewrite paths, add headers, redirect requests, or split traffic.
Replay loopSave a failed webhook, fix the handler, then send the exact request again.
Stable identityUse reserved subdomains and custom domains when one address must not change.
Use cases

Built for the moments before deploy.

Use chiq.uz when the outside world needs to reach something still running on your laptop, test box, private network, or short-lived preview.

Webhook testing

Receive callbacks on localhost. Inspect payloads and replay until the handler is right.

Live previews

Share a local build without provisioning staging for every small review.

Mobile QA

Open your local web app or API from a phone, tablet, or remote device.

Private access

Forward TCP traffic for databases, SSH, internal tools, sockets, and services.

Pricing

Start with early access. Keep the plan simple.

Early access includes public HTTPS tunnels, TCP forwarding, inspection, replay, reserved subdomains, custom domains, and basic traffic controls.

Included direction
  • Concurrent tunnels
  • Reserved names
  • Custom domains
  • HTTP and TCP
  • Live inspector
  • Request replay
FAQ

Short answers.

Enough context without turning the landing page into full documentation.

Can I inspect webhook payloads?

Yes. Incoming requests should show headers, body, status, timing, and route context.

Does it work from the terminal?

Yes. The CLI is the fastest path for opening and controlling a tunnel.

Can I use a stable URL?

Reserved subdomains and custom domains are part of the planned workflow.

Is TCP supported?

Yes. The product direction covers HTTP tunnels and raw TCP forwarding.

Early access

Give your local work a public surface.

Join the early list and help shape a tunnel workflow for fast, precise local development.

Request accessView CLI