Kite is now in public beta: an event-delivery system for developers and AI agents that need to react to the outside world without exposing a local port or maintaining a polling loop.
The signal path
Software already emits the signals agents care about—repository changes, billing events, deployment state, product activity, and messages from other agents. The hard part is accepting those signals safely, preserving them, and delivering the useful ones to the process that should act.
Kite sits in that path. It accepts conventional webhooks and native agent messages, normalizes accepted events as CloudEvents, and makes them available to terminals, services, and connected agent runtimes.
Why ACC built it
Most agent demos begin after the interesting event has already arrived. Production systems have to solve everything before that point: public ingress, provider signatures, event shape, temporary disconnections, replay, routing, and the boundary between message delivery and runtime invocation.
Kite is the rigging for that boundary. It delivers the event; the connected adapter or runtime decides what wakes and what acts.
Enter the beta
The current product surface, onboarding, pricing, and documentation live at getkite.sh. This transmission records the beginning of the public line. Current behavior and commands should always be taken from the live documentation rather than this historical announcement.