The Event Bus for GitHub
Dispatch, observe, and replay workflow events across organizational boundaries — securely, with zero payload drift.
GitHub Actions stop at org boundaries. Zekt bridges them — no shared secrets, no shared repos, full replay.
Set up in minutes — no credit card required
Powerful Workflow Solutions
Everything you need to collaborate around GitHub workflows across or within organizations - solving provider and consumer patterns
Zekt Orchestration
Orchestrate GitHub workflows across organizations — securely, seamlessly & event-driven.
- Secure event brokering & messaging
- Cross-repository / organizations - orchestration
- Publish your workflow services to consumers using the Zekt Directory
- Connect GitHub workflows — without merging your worlds
Zekt Analytics
Get greater insights to statistics and analysis - improve efficiency
- Insights dashboard & statistics
- Time Travel — replay any event, exactly as it happened
- Which pipelines are mostly subscribed to?
- Export & Integration functionality
Zekt Shield
Enterprise-grade security with Zero-Knowledge Encryption for your workflows.
- Zero-Knowledge Encryption (ZKE) for payloads
- Secure data transmission between Providers and Consumers
- Bring Your Own Key (BYOK) architecture
- Compliant with strict security standards
Zekt Action
A free GitHub Action that lets providers attach custom messages to dispatched events — giving consumers the context they need.
- Send structured messages alongside events. Zekt Action supports arbitrary JSON payloads (max 512 KB in size)
- Free on all tiers — only message processing API usage charges
- Documented at https://zekt-dev-org.github.io/zekt-docs/overview/zekt-actions/ - hit the ground running!
- Optionally — enhance workflows without changing existing ones, just reference the Zekt Action - attach the arbitrary JSON payload once your repo is enabled & Zekt does the rest
Zekt VS Code Extension
A free VS Code extension that lets Zekt customers perform common management tasks against Zekt from within VS Code — giving customers the context they need from within their favourite IDE. Zekt VS Code Extension enables conversational MCP integration towards Zekt.
- Perform common administrative tasks against Zekt backend from within VS Code
- Enable MCP integration — conversational agent capabilities against Zekt from VS Code chat UI
- Free on all tiers — only message processing API usage charges
- If you prefer VS Code for administration instead of full blown Zekt web UI — use this plug-in. Not on par with web UI.
Zekt for ISVs
Embed Zekt inside your product — Zekt's multi-tenant orchestration, replay, and analytics infrastructure is purpose-built for embedding. If you're an ISV looking to power your solution with reliable cross-org event delivery — let's explore together.
- Purpose-built for multi-tenant embedding
- Orchestration, replay & analytics under the hood
- Your brand, Zekt's infrastructure
- Exploratory initiative — not a self-service offering
This is an exploratory partnership — not a self-service offering.
Time Travel — Replay Any Event, Exactly As It Happened
Production incident? Consumer workflow changed? New team onboarding? Replay events from the last 90 days with zero payload drift.
Something broke at 3 AM. Don't panic — rewind time. Replay any event from the last 90 days, exactly as it was delivered, with zero payload drift. Your consumer workflows won't know the difference.
Incident Recovery
Consumer workflow broke overnight? Select the failed events and replay them — structurally identical to the originals. No manual re-construction.
Compliance Replay
Auditor needs proof of what was delivered 60 days ago? Replay the batch with a full audit trail — every event accounted for.
Dev & Testing
Changed your consumer workflow? Replay yesterday's events to verify it handles them correctly — with real production payloads.
Consumer Onboarding
New team just subscribed? Replay the last week of events so they can catch up — no waiting for the next live event.
Time Travel is available with the Analytics Add-on — the #1 reason teams upgrade.
See Analytics Pricing →How Zekt is Different
Zekt is not a general-purpose automation tool. It does one thing — GitHub cross-org workflow orchestration — and does it better than anything else.
Not a General Automation Tool
Zapier and Pipedream connect 7,000+ SaaS apps together. Zekt does one thing: GitHub cross-org event orchestration. We do it better because it's all we do.
- Purpose-built for GitHub workflow ecosystems
- No generic connectors — deep GitHub-native integration
- Provider/consumer model designed for org boundaries
Not a Webhook Delivery Service
Hookdeck and Svix deliver generic webhooks to any HTTP endpoint. Zekt dispatches structured events between GitHub repositories with workflow-aware routing and replay fidelity.
- Events are GitHub-native, not generic HTTP payloads
- Routing rules based on workflow context — not just URLs
- Time Travel replay with zero payload drift
Not a CI/CD Pipeline
GitHub Actions runs your workflows. Zekt connects them across organizational boundaries — without sharing repos, secrets, or access. Build locally, orchestrate globally.
- Complements GitHub Actions — doesn't replace it
- Zero-trust: no credentials cross org boundaries
- Providers control who subscribes to their events
Events + Messages — Complete Context
Other tools deliver payloads. Zekt delivers payloads and messages. Providers use the free zekt-action to attach human-readable context to every event — so consumers know the what and the why.
- Events carry structured data — messages carry intent
- Free zekt-action available on GitHub Marketplace
- No competitor offers built-in provider-to-consumer messaging
About Zekt
Built by developers, for developers
Zekt Mission
- Simplify GitHub workflow orchestration across organizations without heavy & sticky plumbing
- Enable secure cross-repository coordination without complexity - increase collaboration
- Provide enterprise-grade automation capabilities for distributed teams
- Bridge organizational boundaries with seamless integration - especially, build "local automation" (e.g workflows) - where you act as a provider - and consumers subscribe to events emitted
Why Zekt Exists
- GitHub Actions stop at organization boundaries
- Teams struggle with cross-org workflow coordination
- Manual processes slow down distributed development or require clunky workarounds
- Security concerns limit workflow sharing between organizations
Our Approach
- Event-driven architecture for real-time workflow orchestration
- Zero-trust security model with granular permission controls
- Developer-first experience with minimal configuration
- Enterprise scalability with multi-tenant isolation
- Easy & seamless onboarding process
Technology Stack
- Built on Azure PaaS & Github SaaS - scale effortlessly
- GitHub App integration for secure & transparent access
- Modern JavaScript with progressive enhancement
- Responsive design optimized for all devices
hub Zekt - the who & the what?
- Zekt is an abbreviation for Zero Event Kernel Tribe (Zekt). Why? Partly cause we deal with eventing - but mostly because it sounds cool
- By developers, for developers - our story behind Zekt! Get the context of the why & what
- Meet the Zekt crew members! Let's introduce ourselves...
Get in Touch
Ready to change how you work with your workflows?
Let's talk.
Contact Information
Connect with us through multiple channels. We're here to help optimize your development workflows.
Location
Zekt - southern Sweden,
Remote-first company
Response Time
Within 24 hours
Business hours: 09:00 - 18:00, Swedish time (CET)
Get in Touch
Ready to optimize your GitHub workflows? Send us a message and we'll get back to you within 24 hours.