Ship It
Configure a micro-page below. Zekt will orchestrate a Provider to build it and a Consumer to deploy it — returning a live URL.
Provider Repository
View Repo
Waiting to start...
-
1Receive build config
-
2Validate & sanitize
-
3Generate HTML page
-
4Dispatch via Zekt
-
5Build complete
Consumer Repository
View Repo
Waiting for provider...
-
1Receive Zekt event
-
2Write page to repo
-
3Deploy to GitHub Pages
-
4Verify & report URL
✅ Your Page is LIVE!
📋 What Just Happened?
Correlation ID
—
Events Dispatched
2 (Provider → Consumer)
Total Delivery Time
—
Provider Workflow
View Run ↗
Consumer Workflow
View Run ↗
Payload Integrity
✅ Verified
How It Works
You click
"Ship It 🚀"
"Ship It 🚀"
Zekt API
triggers Provider
triggers Provider
Provider builds
your page
your page
Zekt delivers
event + message
event + message
Consumer deploys
your page
your page
This demo showcases Zekt's ability to orchestrate workflows across multiple repositories using secure, event-driven architecture. Your page is built by a Provider, delivered through Zekt's event mesh, and deployed by a Consumer — all without sharing credentials.
📨 What the consumer receives — Event + Message:
{
"event": "build.completed",
"message": "Production build for v2.1.0 — includes your requested page",
"provider": "zekt-demo-provider",
"consumer": "zekt-demo-consumer",
"timestamp": "2026-03-11T14:30:00Z"
}
Events carry structured data. Messages carry intent. The free zekt-action makes this possible.