Zekt Core

Back to Zekt

Base service — the foundation every other Zekt component builds on

Core Service

The event bus that connects
GitHub workflows across every boundary

Providers publish. Consumers subscribe. Zekt handles the rest — securely, reliably, and without merging your organizations.

Starting at $10 / repo / month + usage

What Zekt Core gives you

Click any card to dive deeper into each capability

Event Brokering
Secure event delivery — no webhooks or tokens to share
click to flip
Event Brokering
Zekt intercepts GitHub workflow_dispatch triggers and routes events to every authorized consumer — without any direct network access between organizations. Providers never expose tokens. Consumers never need provider credentials.
  • Zekt acts as the trusted intermediary
  • HMAC-signed delivery, tamper-proof in transit
  • No firewall rules, no VPNs, no shared secrets
click to flip back
Cross-Org Orchestration
Connect repos across organizations — or enterprises
click to flip
Cross-Org Orchestration
Provider repos publish events; consumer repos subscribe. Works across different GitHub organizations and enterprises.

Perfect for platform teams of handling consumers or suppliers who need to trigger partners workflow.

Publish your workflow as a service in the Zekt directory marketplace & Consumers only need a standard repository_dispatch workflow.
click to flip back
Zekt Directory
Discoverable workflow services — browse & subscribe
click to flip
Zekt Directory
Providers list their services in the public Zekt Directory. Consumers browse, request access, and subscribe — without contacting the provider team directly.
  • Service discovery without Slack DMs or Confluence docs
  • Access control: providers approve or reject subscription requests
  • Service metadata: SLA, payload schema, event types
click to flip back
Zero-Config Consumer
Consumers need zero infrastructure to receive events
click to flip
Zero-Config Consumer
A consumer repo only needs a GitHub Actions workflow that listens on repository_dispatch. No keys to manage, no servers to run, no extra configuration.

That's it. Zekt handles authentication, delivery, retry, and tracking on behalf of both sides.
click to flip back
Delivery Guarantees
At-least-once delivery with automatic retry
click to flip
Delivery Guarantees
Failed dispatches are retried automatically. Delivery status is tracked per event — both provider and consumer can see whether an event was received and acted on.
  • Automatic retry on transient GitHub API failures
  • Delivery status: pending, delivered, failed
  • Per-event correlation ID for traceability
click to flip back
Per-Repo Billing
Pay only for what you use — enable per repo
click to flip
Per-Repo Billing
$10 / repo / month base rate. Usage-based API metering on top. Enable only the repos you need — disable at any time to stop billing for that repo.
  • No seat licenses, no org-wide commitments
  • Provider repos and consumer repos billed separately
  • Usage metered per event dispatched
See full pricing details.
click to flip back

When to use Zekt Core

Zekt Core is the right fit when:

  • You need to trigger GitHub Actions in another organization without exposing secrets or granting direct repo access.
  • Your CI/CD pipelines span organizational boundaries — e.g. a platform team triggering deployments in product teams.
  • You want to build an internal service marketplace: one team publishes a workflow, many teams subscribe and consume it.
  • You're replacing fragile manual webhook scripts with a production-grade, monitored event bus.

Not sure if Zekt is the right tool? See Zekt vs. Alternatives for an honest comparison.

Combinations that work great

Zekt Core is the only required component. Add-ons extend it.

Recommended add-ons

  • Core + Analytics — Usage dashboards, event history, Time Travel replay. Recommended for any production deployment.
  • Core + Shield — Zero-Knowledge Encryption for payloads carrying sensitive data.
  • Core + Chainlink — Let a repo act as both provider and consumer for multi-hop pipelines.
  • Core + Zekt Action — Attach a structured JSON payload to every dispatched event. Free.

Incompatible combinations

  • None — Core is the foundation. All add-ons require Core, and Core itself has no incompatibilities.
  • Note: certain add-on to add-on combinations have constraints. See Zekt Shield and Zekt Analytics for the Shield + Time Travel constraint.

Next up

Explore Zekt Analytics

See what the Analytics add-on unlocks — dashboards, history & Time Travel