- Every claim traces to a primary source: the vendor’s own pricing page, docs, status page, or an SEC filing. Review sites and forum threads are colour, never the spine of an argument.
- Where a capability is gated, metered or tier-locked, we mark it partial and name the limit rather than calling it unsupported. “Premium and Enterprise only” is more useful to you than a cross.
- Anything we could not confirm from a primary source reads “Not published”. We never fill a gap from memory, and we never guess a price.
- Warrn’s own column is held to the same standard. Capabilities we sell but have not shipped read “On the roadmap”, and ones that exist but are not yet in the product UI read “Early access”.
- Every competitor gets a section on where they beat us, because a comparison that concedes nothing is just marketing.
Sources
- Opsgenie pricing (legacy)
- What happens when Opsgenie is turned off
- Support coverage after migration
- Compass phase-out
- Atlassian Service Collection rate card
- What are escalation policies
- PagerDuty incident management pricing
- PagerDuty AIOps pricing
- incident.io pricing
- FireHydrant pricing
- Rootly pricing
- Better Stack pricing
- SolarWinds Incident Response pricing
Something out of date, or a claim you think is unfair? Email support@warrn.io with a link to the source and we will correct it — including when the correction is not in our favour.