Introduction
Kepeink documentation
Create a tunnel, run the agent, and open your local service at a public HTTPS URL.
Kepeink gives an app on your own machine a stable public HTTPS URL. The agent connects out, so it works behind CGNAT or LTE with no port forwarding, no public IP, and no domain to buy. You pay for the traffic you use.
http://localhost:8080 → https://abc-def-ghi.rproxy.94000003.xyz
Example address; the dashboard assigns your own hostname.
Start in three steps
- Create a tunnel in the dashboard and choose what it should serve.
- Run the agent on the machine that can reach that app or folder, using the token shown for the tunnel.
- Open the assigned HTTPS URL from the dashboard. Your service is live while the agent is connected.
Follow Expose a local web app for an app or API, or Serve a static folder for files. Install the Agent covers Linux, macOS, Windows, and a quick foreground run. If your app is in Compose, use Run the agent with Docker.
Choose a target
| What you have | Backend mode | Example target |
|---|---|---|
| A running web app, API, or dashboard | proxy | http://localhost:3000 |
| A folder of built files | static | /home/alex/site/dist |
| A folder to manage in a browser | files | /srv/shared |
| Browser SSH terminal | ssh | 127.0.0.1:22 |
| Kepeink Remote Desktop | Remote Desktop | desktop or an existing VNC host:port |
The target must be reachable from the agent. Static folders need an absolute path. A Docker agent reaches a sibling container by service name, such as http://web:3000.
Manage files in a browser and Open Kepeink Remote Desktop cover the browser tools. The file manager requires Basic auth with a user. Remote Desktop strongly recommends it and asks you to confirm twice before creating a desktop without it. Native desktop hosting requires agent v2.5.60 or newer.
Open an SSH console walks through SSH credentials and protecting the browser terminal.
Make it yours
Every tunnel starts with an assigned Kepeink hostname. You can add your own domain after that URL works. End-to-end TLS lets the agent hold the certificate and key on your machine.
Traffic uses prepaid credit. The dashboard shows your balance and lets you add credit as needed, with one-time top-ups or optional monthly renewals.
Tutorials
- Install the AgentConnect a tunnel from Linux, macOS, or Windows with the Kepeink agent.
- Expose a local web appGive a web app or API on your machine a public HTTPS URL in three steps.
- Serve a static folderPublish a folder of files at a public HTTPS URL without running a web server.
- Manage files in a browserSet up a private browser file manager for a folder on your agent machine.
- Open Kepeink Remote DesktopUse your machine's screen, keyboard, and mouse from a private browser session.
- Add a custom domainPut your own hostname on a working Kepeink tunnel.
- Open an SSH consoleOpen a protected browser terminal to an SSH host your agent can reach.
- Turn on end-to-end TLSLet the agent terminate HTTPS on your machine and keep the certificate key there.
- Run the agent with DockerAdd the Kepeink agent to a Compose project and give your app a public HTTPS URL.
- How to invite peopleCreate a single-use invite link in your dashboard and see when it is redeemed.
Use cases
- Share a local dev server with a teammateGive a teammate an HTTPS URL for the app running on your laptop.
- Reach a home service behind CGNATReach a home service over HTTPS without a public IP or port forwarding.
- Put a home-lab dashboard onlineOpen one home-lab dashboard from anywhere, with an optional custom domain.
- Receive webhooks on a local appGive a webhook provider a public HTTPS URL that reaches your local handler.
- Expose Immich with DockerPut an Immich Compose service online by adding the Kepeink agent to its project.