Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

A high performance PageKite implementation in C

branch: master
libev libev: Importing libev for convenience
net.pagekite.lib Track and report app version numbers, not just library
AGPLv3.txt Switching to Apache License Basic semi-functional Android wrapper
Makefile Minor updates More To Dos
pagekite_net.h Bump FE_MAX number
pagekitec.c Abort pagekitec if no frontends could be configured during startup
pkblocker.c Fix DNS checker to not forget what was in DNS before, even if new loo…
pkblocker.h Updated Copyright notice
pkerror.c Abort pagekitec if no frontends could be configured during startup
pklogging.c Fix broken format string
pklogging.h Added loop tracing
pkmanager.c Put upper bound on error_count for long running sanity
pkproto.c Added loop tracing
pkproto.h Updated Copyright notice
pkstate.h Added -R for random frontend selection instead of pinging
tests.c Updated Copyright notice
version.h Version bump


This is a tight, fast implementation of the PageKite protocol in C, suitable for high-performance or embedded applications.

This code is a work in progress.

What is PageKite?

PageKite is a protocol for dynamic, tunneled reverse proxying of arbitrary TCP byte streams. It is particularly well suited for making a HTTP server on a device without a public IP address visible to the wider Internet, but can also be used for a variety of other things, including SSH access.

For more information about PageKite, see

What is in the box?

Things that work:

httpkite.c      Sample implementation of a very basic HTTP server
pagekitec.c     Basic standalone pagekite back-end connector/proxy.

Works in progress:

pagekite-jni.c  JNI wrapper for use in Android development  A simple Python wrapper

Everything else is either support code or documentation.

Getting started

Playing with httpkite.c is probably the easiest way to get started hacking. You can build it like so:

$ make httpkite

Running the program will give some hints on how to use it. It does not do anything useful on its own, the idea is to provide a basic implementation which can extended and build upon.

A more complete implementation of a PageKite proxy is in pagekitec.c.

This project has a Wiki page:

Getting started on Android

This source tree can be included in an Android project using the NDK. It has been tested and verified to work with revision 8 of the NDK, targetting Android 2.2 (Froyo, API level 8).

If PageKite is the only native package you are using, the quickest way to get it to build as part of your project is by adding the following symbolic links to your project tree:

cd /path/to/YourApp/
ln -s /path/to/libpagekite/ jni
mkdir -p src/net/pagekite
ln -s /path/to/libpagekite/net.pagekite.lib src/net/pagekite/lib

You will also need to grab a copy of OpenSSL for Android, we recommend the version maintained by the Guardian Project:

cd /path/to/libpagekite/
git clone

(Although not recommended, SSL support can be skipped by commenting out the relevant lines in the file and removing #define HAVE_OPENSSL from common.h.)

Finally, the JNI interface can then be built using the commands:

cd /path/to/YourApp/
export NDK_PROJECT_PATH=/path/to/android-ndk
make -f jni/Makefile android

Expect this to take a while, as building OpenSSL for multiple architectures is a pretty big task. Once everything has been compiled, you should be able to import net.pagekite.lib and use the methods of the PageKiteAPI class in your app - but please read our licensing terms carefully if your app is not Open Source.

If you are using multiple native packages, you may need to structure your code differently and massage the files a bit.

License and Copyright

libpagekite is Copyright 2011, 2012, The Beanstalks Project ehf.

This code is released under the Apache License 2.0, but may also be used according to the terms of the GNU Affero General Public License. Please see the file for details on which license applies to you.

Commercial support for this code, as well as managed front-end relay service, are available from

Development of this code was partially sponsored by SURFnet and the Icelandic Technology Development fund.

Something went wrong with that request. Please try again.