What is Zekt?
Zekt is for companies that want to turn their workflows into services that others can easily consume: teams inside the same GitHub organization, other GitHub organizations, or personal GitHub accounts.
Zekt’s orchestration is popular in platform engineering, where long chains of individual steps can be orchestrated across different providers.
Your business logic stays in your own workflow YAML. Zekt handles only event dispatch and distribution, including orchestration. It never dictates the logic you expose. It routes events to the intended receivers, lists your services in the Zekt Directory, and handles access approval, payload schemas and delivery tracking.
How it works
Section titled “How it works”Zekt connects GitHub Actions workflows across repository and organization boundaries. A workflow in one repository can trigger workflows in other repositories, and nobody shares tokens or repository access.
Zekt delivers each event to a receiving repository as a GitHub repository_dispatch event, and
records the delivery. Delivery is at-least-once. You manage everything in the web console at
www.zekt.dev.
The building blocks
Section titled “The building blocks”| Component | What it is |
|---|---|
| Zekt Core | Providers, consumers, the Directory and access approval. |
| Zekt Action | The GitHub Action zekt-dev-org/zekt-action@v3. Use it to attach a payload to an event, submit orchestration requests, and report a consumer service’s outputs. |
| Zekt Analytics | Add-on: archive events, replay them with Time Travel and Webhook Replay, and get insights. |
| Zekt Shield | Add-on: end-to-end payload encryption with your own keys, Redaction Guard, and Doctrine. |
| Zekt Chainlink | Add-on: one repository acts as both consumer and provider, so events can chain across repositories. |
For prices, see zekt.dev/zekt-pricing.