Kepeink documentation

Kepeink is a reverse-connectivity tunnel service. You install a small Agent on your machine, choose a local service — a web app, a static folder, or an SSH endpoint — and Kepeink publishes it on the public internet at a hostname it assigns you. The agent dials out to Kepeink over HTTPS and holds the tunnel open; nothing ever connects in to your machine, so no port forwarding and no public IP address are required.

When Kepeink is useful

• You have no public IP. Home broadband behind CGNAT, mobile/LTE, or satellite links never expose an inbound port. The agent's outbound connection sidesteps that entirely.
• You want to share a local dev server. Hand a teammate a real HTTPS URL for the app running on your laptop instead of screen-sharing.
• You self-host from home. Put a home-lab dashboard, a personal wiki, or a media server online without touching your router.
• You need a quick, disposable demo. Spin up a public URL for a folder of files or a prototype, then tear it down when you are done.

How it works

1. You sign up and create a tunnel in the dashboard. The tunnel records which local target to expose and in which backend mode.
2. Kepeink gives you an agent token and a one-line installer.
3. You run the installer on the machine that hosts the service. The agent opens an outbound HTTPS connection to Kepeink's router plane and keeps it alive.
4. Visitors reach your assigned hostname over HTTPS. Kepeink relays each request down the open tunnel to your local target and streams the response back.

Backend modes

Each tunnel runs in one backend mode:

• proxy — the agent reverse-proxies a local HTTP(S) target you name, such as http://localhost:3000. Use this for web apps, APIs, and dashboards.
• static — the agent serves files from a local folder directly, no application server required. Use this for a built site or a folder of assets.

Hostnames, custom domains, and TLS

• Every tunnel gets a server-assigned public hostname on a shared Kepeink domain, ready to use immediately.
• You can attach your own custom domain to a tunnel when you want a branded URL.
• You can turn on end-to-end TLS, where the agent terminates HTTPS on your machine with its own Let's Encrypt certificate. The private key is generated on your machine and never leaves it.

Billing

Kepeink is billed as prepaid traffic credit. You buy a bandwidth top-up up front; the traffic your visitors use draws it down. Credit is valid for the period shown at purchase, and you can buy more whenever you need it from the dashboard.

Start here

New to Kepeink? Follow the tutorials in order: begin with Install the Agent, then Expose a local web app. Prefer to learn by example? Jump to the use cases for ready-to-run recipes.