Product · Deploy tracking
Every anomaly,
pinned to the release that caused it.
Most outages are change-driven. Greenslope treats releases as first-class events, not metadata bolted onto a dashboard. When something breaks, the timeline already has what changed — and when — without you having to stitch it together.
Serves this job
"When a user reports the app feels slow or broken, I want to know which endpoint is misbehaving and whether my last release caused it." (JTBD 1) · "When something breaks, I want the change timeline to include Vercel-native change events and GitHub releases." (JTBD 10a)
A change timeline assembled for you, not by you.
Point the OTel SDK at Greenslope's ingest endpoint. Install the Vercel integration and GitHub App. We do the correlation.
Release attribution, by default
Each span carries its release ID as a resource attribute. Anomalies are scored against pre- and post-release distributions so a regression points at the commit, not the person on-call.
Vercel-native change events
Deployments, rollbacks, env-var changes, feature-flag changes, and firewall attack events land on the timeline automatically via the Vercel integration.
GitHub releases, linked
Our GitHub App listens for tag and release webhooks. Every release on the timeline links to its release notes — no more hunting between tabs.
Blast radius in one view
Trace-derived dependency view tells you if the cause is local to your service, downstream-internal, or a third party — so you don't waste the first fifteen minutes of an incident narrowing the search.
Freshness you can trust
The Doctor page shows per-service freshness in real time: seconds-fresh, minutes-stale, or not arriving at all. You'll know when a dashboard is lying.
Opinionated SLOs and thresholds
New endpoints are watched for ~24 hours, then Greenslope proposes SLOs and latency thresholds derived from the actual distribution. Accept, tweak, or override.
What ships today, what comes next.
What ships today
- Vercel deployments, rollbacks, env-var changes, and feature-flag events.
- GitHub release and tag events via the GitHub App.
- Per-service release attribution based on OTel resource attributes.
- Per-endpoint anomaly scoring vs. pre- and post-release distributions.
- Change-timeline view with filterable sources.
- Multi-service tenants as the default data shape.
Out of scope (or V2+)
- LaunchDarkly, Statsig, and Split feature-flag events — V2+ on customer demand.
- Terraform apply events and managed-DB failovers — V2+.
- External status-page aggregation (StatusGator / IsDown) — V2+.
- GitHub commits and PRs on the timeline — V2+ when PR-level attribution demand surfaces.
- One-click programmatic rollback — V1 is suggest + deep-link to Vercel's rollback dialog. Programmatic rollback ships when Vercel stabilises the REST endpoint.
- Per-service team ownership and routing — V2+ at Team tier.
Get started
See what your last 10 deploys really did.
Point GreenSlope at one service. Five minutes to first insight. No credit card, no sales call. If you don't like it after 30 days, we'll help you export everything.