When a tool your team depends on stops behaving, the first question is never "what is the root cause." It is "is it me, or is it them?" Until this week, the only way to answer that about Agile Analytics was to email us and wait. That is a bad answer when you are mid-sprint, and it is a worse answer when the problem turns out to be a five-minute blip that resolved while you were writing the email.
A status page that actually checks
There is now a public status page at /status, linked from the top navigation. It reports four components — the website, checkout and billing, licence activation, and telemetry ingestion — and it does not read from a dashboard somebody remembers to update. Each check runs against the real dependency when you load the page, cached briefly so a rush of visitors cannot become its own outage. If a check cannot complete, the page says so plainly instead of showing a reassuring green tick it has not earned.
Related: View the status page
It fails honestly
A status page that only works when everything works is decoration. This one degrades: if a dependency check itself errors, that component is reported as unknown rather than healthy, and the page still renders the rest. There is also an incident log, so a problem that has been resolved leaves a record instead of vanishing — the history matters more than the current colour when you are deciding whether to trust a tool with your team's reporting.
A support promise, in writing
We have always replied quickly. What we had not done is commit to it anywhere you could hold us to. Our support page now states the commitment plainly: every request gets a reply from a real person within one business day, Monday to Friday. Not an auto-acknowledgement — a reply. The site used to say "24 hours" in some places and nothing at all in others; there is now exactly one promise, and it is the one we can keep.
Related: Support
Ninety days before anything visible disappears
The quiet fear with any small vendor is that something your reporting depends on gets removed in a release you did not read. Our terms now promise the opposite: no feature you can see is removed without a replacement and ninety days' notice. That is a constraint on us, deliberately, because the alternative is asking you to trust a promise nobody wrote down.
Related: Terms
Invoices your finance team can file
Checkout now collects a business tax ID — VAT number, USt-IdNr., and the equivalents — for buyers in supported countries, and stores it against the customer record. For EU business purchases that means the invoice carries the right details from the first payment, instead of a post-purchase round of credit notes and reissues. It is optional and it is one field, but it removes an entirely avoidable piece of admin from the week after you buy.
Why this, and why now
None of this makes a single chart better. It is all the unglamorous scaffolding that decides whether a team is comfortable putting a small vendor in the middle of how they report on their own delivery — knowing where you stand when something breaks, how fast a human answers, what happens to a feature you rely on, and whether the paperwork works. We would rather write those down than ask you to assume them.