Rolling out. This feature is rolling out to pilot customers, so it may not be in your workspace yet.
Pulse calculates the numbers first, then asks the AI to explain only the evidence from your selected period. Here's how to read what it writes.
Three views of every finding
- Owner: what happened, who it affected, and why it matters to the business, in plain language.
- Engineering: what the evidence shows in your application, and the likely cause.
- Database: what the evidence shows in your database, when the database is involved.
Confirmed vs. suspected
Confirmed means the evidence directly shows it. Suspected means it's a plausible cause the evidence doesn't prove yet. Every claim links to the checks, incidents or metrics behind it.
Every recommendation answers the same questions
- What to do: the concrete steps.
- How long: an effort range such as 1–4 hours or 1–2 days, never a fake-precise number, with the reasoning behind it.
- Impact: what gets better and for whom.
- Pros and cons: every change has a trade-off, and the report names it.
- Risk and reversibility: how safe the change is, and whether you can undo it.
- Who: your developer, your database admin, your hosting provider, or InnoStak engineers.
What the report won't do
It won't claim revenue losses, guarantee a root cause, or make changes to your systems. If data is missing or stale, it says so under Limitations instead of guessing.