Kite is open source.
The protocol, CLI, and mesh live under Alpha-Centauri-Cyberspace on GitHub. The hosted control plane runs on getkite.sh. Build, fork, embed, or just read the code — it's all MIT.
What's open, what's hosted.
Kite's positioning is simple: open protocol, open clients, hosted control plane. You can run the CLI against our cloud, fork the mesh into your own stack, or build something new on top of the protocol crate — but the production delivery, storage, and replay infrastructure is a service we operate.
Four public repos.
Everything you need to ship, fork, or embed Kite. Each repo tracks its own release cadence and issue tracker.
The kite binary. Rust, async, and built for the terminal. Handles auth, streaming, replay, and scripting.
brew install alpha-centauri-cyberspace/kite/kiteThe wire format. Published on crates.io so anyone can speak Kite — CloudEvents-normalized payloads, signatures, envelope types.
cargo add kite-protocolThe mesh protocol. Fan-out across subscribers, backpressure, and resumable delivery. Makes multi-consumer webhooks sane.
cargo add kite-meshOfficial Homebrew tap. Keeps every macOS and Linux user one command away from the latest kite build.
brew tap alpha-centauri-cyberspace/kiteSend us a pull request.
Every public Kite repo is MIT licensed. Use it, fork it, ship it inside your own product — the only ask is that you keep the copyright notice.
Bug reports, protocol feedback, and PRs are welcome. Start with the CONTRIBUTING guide in kite-cli, then open an issue on whichever repo you're working in. We prefer small, focused PRs with a test.