API version adoption
Who is still on v1?
Track traffic share and get a customer migration list.
86%on v2
v2 · 43 customersv1 · 7 customers
Customer integration intelligence
Every API request tells a customer story.
Apirelio connects telemetry, customer identity and release context so your teams can see risk, adoption and impact in one place.
Health score84+6 pts
Active customers483 at risk
Success rate98.7%+0.4%
Customer trafficLast 7 days
124.8k requestsrelease 2.4.0
!
Release regression detectedPOST /invoices/send · +38% latency
nowFlagship intelligence
API change impact simulator
Know the blast radius before the breaking change ships.
Upload the OpenAPI contract proposed for your next release. Apirelio compares it with the current contract, then maps every risky change to real production traffic and the exact customers who depend on it.
- ✓ Removed operations, required parameters and auth changes
- ✓ Affected customers and percentage of production traffic
- ✓ Evidence-backed pre-release verdict without payload capture
Current contractBilling API v2.442 operations
→Candidate contractBilling API v3.039 operations
Analyzed!
Pre-release verdict8 customers are in the blast radius23.4% of observed production traffic
3breaking changes
!
6 customers
Operation removedPOST /v1/invoices/{invoice}/send
1,240 requests6 customers
!
4 customers
New required parameterPOST /v2/refunds
842 requests4 customers
△
2 customers
Authentication changedGET /v2/customers/{id}
381 requests2 customers
AENSLCOS
Acme Europe is most exposed2 breaking changes · 628 requests
Review customer →01
Customer health
Know who needs attention before the support ticket arrives.
One explainable score combines usage, reliability, latency, endpoint adoption and regularity. Every score includes the signals and components behind it.
- ✓ Portfolio view across every customer
- ✓ Healthy, warning, critical and inactive states
- ✓ Traffic movement against the previous period
Customer healthAcme Europe
Healthy90Health score
Activity30/30
Reliability26/30
Performance14/15
Adoption12/15
Regularity8/10
Traffic +18%vs previous 7 days
1.2% error ratewithin target
4 endpoints1 not yet adopted
02
Release impact
Connect every deployment to the customers it affected.
Compare a release with its preceding equal-duration baseline. See whether success rate or latency regressed, which endpoints moved and who experienced the change.
- ✓ Automatic before-and-after baseline
- ✓ Endpoint-level regression ranking
- ✓ Exact list of affected customers
Release impact2026.07.29.1
RegressionBaseline98.4%141 ms P95
−13.8%→+118% latencyCurrent release84.6%308 ms P95
EndpointRequestsError change
POST /invoices1,248+8.4%
POST /invoices/{id}/send918+4.2%
GET /customers/{id}2,841stable
Example incident
From signal to action
One risky release. Four affected customers. No guesswork.
An illustrative workflow using the same signals available in the Apirelio demo workspace.
Release2026.07.29.1Production
Observed impactSuccess −13.8 ptsLatency +118%
AENSOSLC
4 customers affectedLumen Commerce is most impacted
- 10:04DeployRelease 2026.07.29.1 starts serving traffic
Release context arrives automatically with request telemetry.
- 10:12DetectPOST /invoices begins regressing
Error rate rises and P95 latency moves from 141 ms to 308 ms.
- 10:13ScopeFour affected customers identified
Engineering sees the endpoint; Support and Success see the accounts.
- 10:20ActThe team has one shared incident picture
No payload search, log correlation or customer-ID translation required.
OutcomeFrom deployment to customer impact in one investigation path.Explore the live demo →
03
Integration journey
Turn onboarding into a measurable funnel.
Track every account from its first connection to regular production usage. Surface stalled integrations with the next action needed to move forward.
0148Connected→
0243First success→
0339Production→
0434Adopted→
0531Regular
LC
Lumen CommerceConnected 2 days ago · 2 failed requests
StalledNext best actionResolve the first failing request
One shared operating view
Answer the questions that generic observability cannot.
What changed?
A deterministic daily briefing.
Compare traffic, reliability, latency, customers and errors.
Requests+18.4%vs prior period
Error rate+2.1 ptsneeds attention
New errors3codes detected
Alerts and integrations
Keep every team ahead of risk.
Monitor inactivity, high error rates and traffic drops, then notify Slack, Teams, signed webhooks or scheduled email recipients.
Orbit Systems error rate18.7% in the last hourOpen
Acme Europe traffic drop42% below previous periodOpen
Daily integration reportDelivered to 3 recipientsSent
Built for your team
One source of truth. Different decisions.
Every team sees the same integration reality through the lens of the work they need to do.
Engineering
Ship changes without losing customer context.
Connect deploys to reliability, latency and the exact accounts affected by a regression.
- ✓Release impact
- ✓Endpoint regressions
- ✓Error diagnostics
Billing APILast 7 days
P95 after release308 ms+118%
CustomerAcme Europe
EndpointPOST /invoices/send
Release2026.07.29.1
Trust by design
Useful insight without risky data collection.
Apirelio collects operational integration signals, not application payloads. The SDK is designed to fail independently from the API it observes.
Privacy first
No bodies, credentials, cookies, query strings or IP addresses.
Fail-safe SDK
Network delivery runs outside the customer request and failures never change its response.
Framework native
Native hooks for Laravel, Symfony, Nette, Slim, CakePHP, FlightPHP, Express, Fastify, NestJS, Nuxt/Nitro, FastAPI, Django, Flask, Ruby on Rails, Gin and Fiber.
Real-time ingestion
ClickHouse-backed analytics designed for high-volume request telemetry.
Your customer-facing API
POST/invoices/{invoice}/send
Middleware observes outcome and contextAsync batch→
Apirelio eventProject-scoped ingestion key
customer_idroutestatusduration_msreleaseCapturedOperational signals only
Normalized route, status, duration, customer and application IDs, API version, release and allow-listed metadata.
Never capturedSensitive request data
Request bodiesResponse bodiesCredentialsCookiesQuery stringsIP addresses
ControlsBounded and revocable
Keys are project-scoped and revocable, stored as hashes, metadata is allow-listed and retention is configured per project.
Coming next
The intelligence layer keeps growing.
These capabilities build naturally on the telemetry and customer context already in Apirelio.
Automatic API version resolvers
Infer versions from route prefixes or custom application logic.
Symfony SDK
Messenger-backed, fail-safe instrumentation for Symfony 6.4 through 8.x.
Nette SDK
Native DI extension and fail-safe lifecycle instrumentation for Nette 3.2 and 3.3.
Slim SDK
PSR-15 middleware with normalized Slim 4 routes and privacy-safe customer context.
CakePHP SDK
Matched-route PSR-15 middleware for CakePHP 4.5–5.x with fail-safe buffered delivery.
FlightPHP SDK
Native before/after middleware for matched FlightPHP routes with fail-safe buffered delivery.
TypeScript SDKs
Asynchronous integrations for Express, Fastify, NestJS and Nuxt 3–4, all built on one bounded Node.js core.
Python SDKs
Dependency-free Python Core plus native FastAPI, Django/DRF and Flask integrations with bounded background delivery.
Ruby SDKs
Ruby Core with Rack middleware plus automatic Rails 7.1–8.x integration through a Railtie.
Go SDKs
Concurrent Go Core plus native Gin and Fiber middleware with bounded background delivery and graceful shutdown.
OpenTelemetry bridge
Connect integration context with existing observability stacks.
AI-assisted investigation
Turn deterministic signals into suggested causes and next actions.
See your integrations clearly