authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Comparison · Infra & APIs
incident.io vs Mergify
A side-by-side editorial comparison of incident.io and Mergify — release velocity, themes, recent moves, and the top alternatives to consider.
incident.io vs Mergify: at a glance
What is incident.io?
Alert rate limits stop being per-source and start being per-tenant, by query.
Investigations went generally available on 5 August, with Nexus posting a root-cause hypothesis and its evidence into the incident channel minutes after declaration. The releases since have been the operational surround: a 24/7 schedule coverage policy that flags gaps before a rotation goes unstaffed, more filtering in Insights, agent-written status page updates, and a resource-by-resource Terraform provider rework. This release lets an alert source extract a value from the incoming payload with a query expression and shard its rate limit on that value, so one noisy customer or cluster no longer consumes the whole source's budget.
What is Mergify?
Mergify's queue learned to merge stacked pull requests, then spent August tightening the edges.
Mergify automates merge queues for GitHub, and August was a mix of one real capability and a batch of contract cleanup. The queue can now merge GitHub-native stacked pull requests in order, speculative-check budgets apply per lane across dynamic scope sets, and conditions can match on whether a pull request came from a fork. Alongside that, the badge API was removed, pagination stopped advertising first and last links, and author-run commands were restricted to fork pull requests by default.
incident.io vs Mergify: editorial side-by-side
incident.io
6.3INFRA · APIS
Alert rate limits stop being per-source and start being per-tenant, by query.
◆ Current state
Investigations went generally available on 5 August, with Nexus posting a root-cause hypothesis and its evidence into the incident channel minutes after declaration. The releases since have been the operational surround: a 24/7 schedule coverage policy that flags gaps before a rotation goes unstaffed, more filtering in Insights, agent-written status page updates, and a resource-by-resource Terraform provider rework. This release lets an alert source extract a value from the incoming payload with a query expression and shard its rate limit on that value, so one noisy customer or cluster no longer consumes the whole source's budget.
◆ Where it's heading
Two threads run in parallel. Nexus started inside the incident channel doing diagnosis and has moved outward to the customer-facing artifact. The second is platform work for customers running at scale — coverage policies, escalation routing, and now rate limiting that understands the shape of the payload rather than treating a source as one undifferentiated stream. Sharded limits are what you build when a single alert source fronts many tenants, which says something about the size of the deployments driving the roadmap.
◆ Prediction
Rate limits that read a query expression out of the payload share machinery with routing and deduplication, so the same expression surfacing in alert routing rules is the likely next step. The changelog entry does not say.
Mergify
6.3INFRA · APIS
Mergify's queue learned to merge stacked pull requests, then spent August tightening the edges.
◆ Current state
Mergify automates merge queues for GitHub, and August was a mix of one real capability and a batch of contract cleanup. The queue can now merge GitHub-native stacked pull requests in order, speculative-check budgets apply per lane across dynamic scope sets, and conditions can match on whether a pull request came from a fork. Alongside that, the badge API was removed, pagination stopped advertising first and last links, and author-run commands were restricted to fork pull requests by default.
◆ Where it's heading
Two threads. The queue is absorbing workflows that used to sit outside it - stacked pull requests, flaky-test detection and rerunning within a CI budget - which pushes Mergify from a merge gate toward owning the whole pre-merge pipeline. The other thread is a deliberate narrowing of surface: deprecated endpoints removed, the github_actions action marked for removal in March 2027, default command permissions tightened around forks. That is a product trimming what it maintains so the queue can take on more.
◆ Prediction
Expect more of the pre-merge pipeline to move inside the queue on the flaky-test pattern, and further deprecations of automation that overlaps with what GitHub Actions now does natively.
Alternatives to incident.io and Mergify
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either incident.io or Mergify.
Warp
The essay series keeps running ahead of the products it describes.
Node-RED
Both lines patch on the same day, and the reverted JSONata upgrade finally sticks.
werf
The 3.x line finally ships function: authenticated secret writes and render patches.
Infisical
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
Retool
Retool posts one-line changelog entries, and its agent work is the only visible thread
See all incident.io alternatives → · See all Mergify alternatives →
Recent activity from incident.io and Mergify
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoincident.ioShard alert source rate limits
- 8d agoincident.ioReworking our Terraform provider
- 8d agoMergifyPer-lane check capacity for dynamic scopes
- 8d agoMergifyPagination drops the first and last links
- 8d agoMergifyRepository badge API removed
- 8d agoMergifyClearer reason when the merge queue can't create the draft pull request
- 15d agoincident.ioAgent-written status updates, Pingdom metrics, and language self-serve
- 21d agoMergifyMerge GitHub stacked pull requests with the merge queue ⚡
- 22d agoincident.io24/7 schedule coverage policy
- 22d agoMergifyNew from-fork condition attribute
- 28d agoincident.ioInvestigations now available, powered by Nexus ⚡
- 29d agoincident.ioFlexible filtering in Insights
Frequently asked questions
What is the difference between incident.io and Mergify?
They serve adjacent needs but don't currently overlap on shipped themes. incident.io and Mergify are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is incident.io better than Mergify?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. incident.io and Mergify are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to incident.io?
Top incident.io alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "incident.io alternatives" section above for the current picks, or visit /alternatives/incident-io for the full list with editorial commentary on each.
What are the best alternatives to Mergify?
Top Mergify alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Mergify alternatives" section above for the current picks, or visit /alternatives/mergify for the full list with editorial commentary on each.