No inbound firewall rule
The agent connects out from your machine. Kepeink terminates public TLS and forwards requests over that authenticated tunnel.
Kepeink gives your device an outbound agent, a public HTTPS hostname, and byte-metered routing credit. It is built for small operators, prototypes, and agents that need a stable endpoint without a VPN ceremony.
$ routerctl tunnel create demo created demo.kepeink.dev $ kepeink-agent --token $KEPEINK_TOKEN route https://demo.kepeink.dev -> http://127.0.0.1:8080 meter bytes in + out against workspace credit
The browser console is a thin client over the same documented endpoints used by automation. Route state is pushed to edges; usage is metered at the edge; public abuse intake is part of the control plane.
The agent connects out from your machine. Kepeink terminates public TLS and forwards requests over that authenticated tunnel.
Credits are prepaid GiB windows. Billing follows bytes in plus bytes out, so automation and human traffic use the same ledger.
Machine tokens, OpenAPI docs, and CLI workflows are first-class. The UI does not get private endpoints unavailable to you.
Each product maps directly to the billing catalog. No hidden seat count, no metered card surprise after the entitlement window expires.
1 GiB credit for first tunnel checks, webhook tests, or a short-lived demo.
25 GiB for a prototype, internal tool, or low-volume public callback endpoint.
50 GiB for daily development tunnels and small production services.
500 GiB for stable projects that need a long entitlement window and fewer billing touches.
Create a token in the management console, then run the matching installer for the machine that will host your origin service.
curl -fsSL https://cdn.kepeink.hu/install.sh | sudo sh -s -- <token>
powershell -NoProfile -ExecutionPolicy Bypass -Command "Invoke-WebRequest -UseBasicParsing https://cdn.kepeink.hu/install.ps1 -OutFile $env:TEMP\kepeink-install.ps1; & $env:TEMP\kepeink-install.ps1 -Token <token>"