inkvo/changelog

Changelog

What we've shipped. Inkvo releases continuously; this is the human-readable trail of what changed and why it matters on-call.

Subscribe · RSS
June 2, 2026
v1.4
Narratives you can trust enough to act on.

Confidence scores & fix-forward PRs

New
Every narrative now carries a confidence score on its root-cause claim. High-confidence incidents can suggest a concrete action; lower-confidence ones say so plainly instead of guessing.
New
Fix-forward PRs. When a rollback isn't the right move, Inkvo can draft a forward fix as a pull request against your repo — you review and merge. Opt in per service.
Improved
Deploy correlation now reads deployment.environment from OTel resource attributes, so a staging deploy never gets blamed for a prod incident.
Fixed
Resolved a case where simultaneous deploys to two services produced two separate narratives for one root cause. They now merge into a single incident.
May 8, 2026
v1.3
The words match the urgency.

Environments get tone

New
Tone per environment. A prod outage reads like war; a staging hiccup reads like a heads-up; dev stays quiet. Severity thresholds and routing follow the tone automatically.
New
Custom environment remapping — point preview or canary at the tone that fits, in Settings → Detection.
Improved
Baseline learning window cut from 48h to 24h for services with steady traffic.
Fixed
Slack threads occasionally duplicated the first narrative message under high event volume. Deduped.
April 15, 2026
v1.2
More of your stack, one endpoint.

Integrations expansion

New
Added 12 connectors across cloud & infra and source/deploys — including GitLab CI, CircleCI, and Cloudflare Workers logs. Browse them on the integrations page.
New
Opsgenie paging alongside PagerDuty, with on-call rotation sync.
Improved
OTLP ingest now accepts gzip-compressed payloads up to 4 MiB, halving egress for high-cardinality services.
Improved
Post-mortem Markdown export includes the full evidence timeline inline.
March 19, 2026
v1.1
Quieter nights, by default.

Adaptive detection

New
Mark-as-noise feedback. Flagging an incident as not-worth-paging feeds the per-service baseline, so the next one is quieter.
Improved
Seasonality modeling — a 9am traffic ramp is no longer treated as an anomaly. Weekly patterns are learned too.
Fixed
Throughput-drop detection misfired during scheduled maintenance windows. Maintenance windows are now respected.
February 4, 2026
v1.0
The first SRE on your team.

General availability

New
Narrative incidents. When something breaks, you get a story — what broke, what's affected, what changed, and what to do — instead of a wall of graphs.
New
OpenTelemetry-native ingest over HTTP and gRPC. One endpoint, one key per environment.
New
Slack, email, and PagerDuty delivery out of the box.