Operating system for engineering teams
Shipped in public, every week, since 2019.
This is the live shipping record of Zilzul — release notes auto-generated from the same engine our customers use on their own teams. Every merged PR becomes a published entry, every shipped ticket becomes a changelog line. Read the last four cycles below.
- Releases shipped
- 214
- Median cycle
- 6 days
- Upstream PRs since 2021
- 9,412
Recent cycles
The last four releases, in order.
Every entry below was written by Zilzul's release-notes engine from real merged pull requests. No hand-edited marketing copy, no post-hoc embellishment. If it shipped, it's here.
-
Async standups go fully read-only by default
- Standup threads are now archived automatically after 14 days; managers can request extensions per workspace.
- Added per-engineer digest mode — receive one combined update at 09:00 local instead of three.
- Fixed an edge case where commits on draft branches were attributed to the wrong cycle.
-
Cycle-time analytics validated to ±6% by DORA
- New percentile filters on the cycle-time chart — p50, p75, p90, p95 toggleable per view.
- Google Cloud's DORA research team confirmed our measurement methodology against their reference dataset.
- Backfilled 12 months of historical cycle-time data for every existing workspace.
-
Release notes publish to changelog and Slack in one click
- One-click publish to a public-facing changelog page with custom domain support.
- Slack thread is auto-created in #releases with formatted entries and links back to the source tickets.
- Added CSV export of every shipped cycle for compliance and customer-success teams.
-
Public roadmap ships 1,847 community requests since 2021
- Customers can now upvote and watch feature ideas directly from the roadmap view.
- Status transitions ('Considering', 'Planned', 'In progress', 'Shipped') emit webhook events.
- Fixed a regression where archived ideas reappeared in active filters after page refresh.
Flagship release · v4.16
Auto-generated release notes, pulled from merged PRs and shipped tickets.
The same engine that writes this changelog ships to every Zilzul workspace. Connect GitHub or GitLab, point it at your changelog destination and your #releases Slack channel, and a draft entry appears within sixty seconds of the final merge. One click publishes to your customers and your team simultaneously — replacing the Trello board, the Notion doc, the Loom walkthrough, and the Friday status thread that usually go into a release.
- Replaces: the average 3-tool release workflow (Trello + Notion + Loom) with one drafted entry.
- Cadence: drafts land within 60 seconds of merge; publish on your schedule — manual, nightly, or per-cycle.
- Trust: every line links back to the merged commit and the shipped ticket; auditors love it, so do customers.
The numbers behind every release.
Every metric below is pulled from production telemetry across 3,400+ teams. No vanity counters, no self-reported estimates — just the audit trail a skeptical engineering manager can actually trust.
- 487 Releases shipped in the last 12 months Auto-published to the changelog and customer Slack channels, directly from merged PRs.
- 2.4d Median cycle time, end-to-end Cycle-time analytics accurate to ±6%, validated by the DORA research team at Google Cloud.
- 99.992% Uptime across 1.2B ticket events SOC 2 Type II certified, GDPR-compliant, audited by Drata with zero exceptions in 2023.
- 1,847 Features shipped from community requests since 2021 Every customer can submit, upvote, and watch their idea ship via the public roadmap.
Get every release note the moment it ships.
Subscribe to the Zilzul changelog by email or RSS. No marketing blasts, no "monthly product recap" — just the same auto-generated notes we publish to our own Slack, sent the second a PR merges.
Start a sprint in 11 minutes.
Skip the demo, skip the sales call. Open a workspace, import a backlog, and ship your first cycle today. Fourteen days, full feature set, no credit card. The same onboarding time our customers report — not a marketing estimate.
- 11 minMedian time to first sprint (industry average: 2.5 days)
- 38%More story points shipped per sprint after switching
- 4.2Fewer meetings per engineer, per week