Self-hosted HTTP gateway that gives AI agents a human-in-the-loop line to Telegram, Slack, Microsoft Teams, Discord, Google Chat, WhatsApp, and Messenger.
Agents send interactive prompts (buttons or free text). Humans answer in chat. Greenlight delivers signed callbacks back to your agent.
Platform credentials are registered per channel via API — not as global environment variables.
Choose your path
| I want to… | Start here |
|---|---|
| Deploy or develop locally in minutes | Quickstart |
| See features, benefits, and how channels connect | Features & benefits |
| Understand PROMPT vs MESSAGE, auth, and architecture | Concepts |
| Compare self-host, enterprise, and cloud admin model | Editions & admin identity |
| Deploy with Docker, Dokploy, or Coolify | Self-Hosting |
| Connect Slack, Telegram, and other platforms | Platforms |
| Integrate an AI agent | Agent integration |
| Wire Greenlight into n8n, Zapier, Make, or similar | Automation platforms |
| Look up HTTP endpoints | API Reference |
| Develop on core, UI, or docs | Local development |
| Understand BUSL licensing | Licensing |
| See upstream projects Greenlight builds on | Credits |
What Greenlight does
- You register a channel (platform + credentials + target chat).
- Your agent creates a prompt or listens for inbound messages.
- Humans interact in the chat app they already use.
- Greenlight posts answers or messages to your
callback_url.
Multiple workflows can post prompts to the same PROMPT channel — each
prompt’s answer returns to that prompt’s callback_url. MESSAGE channels
forward all inbound chat to a single channel callback_url. See
Features & benefits.
Editions
| Edition | Where | License |
|---|---|---|
| Community | This repository (core/, ui/, docs-site/) | BUSL-1.1 |
| Enterprise / Cloud | Separate commercial offering | Proprietary |
Self-host for yourself or your organization is allowed. Selling Greenlight as a competing hosted subscription is not allowed. See Licensing.