PageKite

PageKite connects a localhost server to the public Internet through front-end relays, acting as a dynamic tunneled reverse proxy. It supports HTTP and HTTPS servers, SSH, and some other TCP-based protocols. The maker describes uses such as hosting a site at home, remote SSH access, connecting embedded devices, webhooks, APIs, and remote debugging. Its feature page says a server can be made visible with a single pagekite.py command. Accounts start with one pagekite.me DNS name, support unlimited subdomains, and can use customer domains through CNAME records. PageKite says SSL is enabled by default for pagekite.me names and supports end-to-end TLS and wildcard relay certificates. Listed relay locations include the United States, Iceland, the United Kingdom, Germany, Japan, and Australia; the client selects a working relay automatically. PageKite is open-source free software. The maker offers FAQ and how-to resources, online chat, and email support. The service has a free plan and a 31-day trial; paid plans start at $5.99 a month. New subscriptions are temporarily unavailable.

PageKite provides a tunnel from localhost to the public Internet, with support for several protocols and use cases. Its subscription availability and listed traffic and account quotas are worth checking before planning a deployment.

PageKite may suit developers or individuals who need to expose a local server for webhooks, APIs, remote debugging, or SSH access. It also lists use for hosting sites at home and reaching embedded devices.

PageKite is a dynamic tunneled reverse proxy that publishes a server running on localhost through globally distributed relays. It suits developers, home-hosted services, and embedded-device teams that need reachable endpoints without exposing a conventional public server. Its strongest case is quick, protocol-flexible access; quota-based plans and temporarily unavailable new subscriptions make deployment planning essential.

Overview

PageKite connects local HTTP or HTTPS servers, SSH services, and some other TCP-based protocols to the public Internet. A single pagekite.py command can make a server visible, so it is practical for short-lived demos, remote administration, webhook testing, and development environments that would otherwise need firewall or router changes.

Accounts begin with one pagekite.me DNS name, allow unlimited subdomains, and support customer domains through CNAME records. PageKite says .pagekite.me names have SSL enabled by default, with end-to-end TLS and wildcard relay certificates also supported. Relay traffic content is not routinely logged or stored, although transfer amounts, connection details, and partial IP addresses may be retained for up to seven days. Website access and error logs containing IP addresses can remain for up to three months.

Key features

• Broad tunnel coverage: HTTP, HTTPS, SSH, and selected TCP protocols cover websites, shell access, APIs, webhooks, and device connections.
• Global relay selection: Relays in the United States, Iceland, the United Kingdom, Germany, Japan, and Australia are available, and the client chooses a working relay automatically.
• Developer integrations: PageKite is positioned for testing services such as Twilio and Instagram's real-time API, making local webhook and API work reachable from remote systems.
• Open-source client: PageKite is open-source free software; pagekite.py and most other releases use the GNU Affero General Public License version 3 or later.
• Operational controls: TLS termination, rate limiting, and both command-line and other configuration approaches are supported.

Pricing

PageKite uses a freemium model, offers a 31-day trial, and currently says new subscriptions are temporarily unavailable. Quotas cover accounts, kite names, and monthly traffic, so the right tier depends on both team size and transfer volume.

• Pay What You Want — $3 a month: Individuals are asked for $3 USD/month, while non-commercial users may receive service free if they renew monthly by describing their use. It includes some months of service, some GB of transfer quota, up to five extra .pagekite.me names, and custom-domain CNAMEs. The variable allowances make it suitable for modest personal or experimental use, not predictable production traffic.
• Freelancer — $5.99 a month: Monthly billing, or prepay a year for 10% off, with 3 accounts, 8 kite names, and 15 GB monthly traffic. This is the practical entry point for an individual or small project that needs defined limits.
• Team — $24.99 a month: 15 accounts, 40 kite names, 83 GB monthly traffic, and priority support. It fits a small development group that needs shared access and service assistance.
• Business — $49.99 a month: 45 accounts, 100 kite names, 210 GB monthly traffic, and priority support. Choose it when multiple projects or heavier transfer justify the larger quotas.
• Embedded — $199.95 a month: 500 accounts, 500 kite names, 750 GB monthly traffic, priority support, three custom domains, custom licenses, and white-label service. This is aimed at products embedding PageKite rather than ordinary internal tunneling.

All paid tiers are billed monthly and offer a 10% discount when prepaid annually.

Platforms

PageKite supports Android, API, Linux, macOS, self-hosted deployments, web access, and Windows. Installation instructions cover Windows, Mac OS, Linux, and BSD, while an Android app is linked from the homepage. Both deployment and configuration models are supported.

Who it's for

Choose PageKite for home-hosted sites, SSH access, remote debugging, webhook and API development, or embedded-device work where a local service needs a public URL quickly. The command-line setup and automatic relay selection favor developers who value speed over managing their own relay fleet. Teams should verify quota needs and subscription availability before committing; the smallest paid plans trade capacity and seats for lower cost.

Pros and cons

Pros

• One-command exposure of localhost reduces setup friction for demos and development.
• HTTP, HTTPS, SSH, and other TCP support handles more than browser-only tunneling.
• Automatic selection across six relay regions can simplify international access.
• Custom domains, end-to-end TLS, and open-source software provide deployment flexibility.

Cons

• Monthly traffic, account, and kite-name quotas constrain larger or busier deployments.
• The low-cost Pay What You Want tier has variable allowances, making capacity planning difficult.
• New subscriptions are temporarily unavailable, which can block immediate adoption.
• Relay metadata and IP-containing logs are retained for limited periods, so privacy-sensitive operators should review that exposure.

Alternatives

For a self-hosted, free reverse proxy with client and server binaries, choose frp. Caddy is a free alternative with paid Indie and Indie Pro plans at $25 and $50 a month. Choose F5 BIG-IP APM when a paid platform supporting virtual, hardware, or hybrid environments is the priority. Fabio is free MIT-licensed software that requires Consul for service discovery, while freenginx is free BSD-like-licensed software. ngrok offers freemium tunneling with a free tier, and Zoraxy is free AGPL open-source software. LocalXpose is a freemium option with a free Starter tier for two active HTTP or HTTPS tunnels.

Verdict

PageKite is a strong choice for developers and embedded teams that need a local service reachable through a public, TLS-capable URL with minimal setup and broad protocol support. Look elsewhere if fixed high-volume capacity, immediate subscription access, or a fully self-managed relay architecture matters more than convenience.