Uptime monitoring built for enterprise scale.
Custom monitor limits, SSO/SAML, a written SLA and dedicated support - for teams that have outgrown standard plans and need monitoring that fits how a larger organisation actually buys and runs software.
Everything in Max, built out for enterprise
Same monitoring engine as every other plan - website, heartbeat and domain monitoring, all HTTP methods and alerting logic - sized and governed for larger teams.
Custom monitor limits & check intervals
Scale past the 300-monitor, 10-second ceiling on Max - enterprise plans are sized to your monitor count and how fast you need checks to run.
SSO & SAML
Single sign-on via your identity provider (Okta, Azure AD, Google Workspace and others) so account access follows your existing provisioning and off-boarding process.
Custom SLA & uptime guarantee
A written service level agreement on monitoring platform uptime and alert delivery times, with service credits if we miss it.
Dedicated support
A named point of contact for onboarding and ongoing support, with priority response times instead of the standard support queue.
Extended log & data retention
Retain incident logs and uptime history beyond the 1095-day standard on Max, for as long as your compliance or reporting needs require.
Invoicing & procurement
Annual billing, purchase orders and invoicing instead of card-only checkout, for teams that need to run monitoring through procurement.
Team roles & permissions
Role-based access across monitors, status pages and alert routing, so teammates and contractors only see and change what they need to.
Bulk SMS & alert credits
Custom-sized SMS credit allocations above the 300/month included on Max, sized to your alert volume.
Enterprise uptime monitoring, without the enterprise complexity
Larger teams tend to outgrow self-serve monitoring plans in the same few places: they need more monitors than a fixed tier allows, faster check intervals across the board rather than on a handful of endpoints, single sign-on so access follows existing identity provider rules, and a written SLA that procurement can sign off on. Kawze Enterprise covers all of that on the same monitoring engine that runs every other plan - website, heartbeat and domain monitoring, full HTTP method and header support, and status pages - so moving to Enterprise doesn't mean moving to a different product.
It's a good fit for engineering teams running monitoring across multiple products or business units, agencies and MSPs monitoring client infrastructure at scale, and any organisation whose security or procurement process requires SSO, an SLA, or invoiced billing before they can adopt a new vendor.
Enterprise FAQs
How is Enterprise priced?
Enterprise pricing is custom, based on monitor count, check frequency, SMS volume and support requirements - contact us with your requirements and we will put together a quote.
Can we get a written SLA?
Yes - Enterprise plans include a written service level agreement on monitoring platform uptime and alert delivery, with service credits if it is not met.
Do you support SSO?
Yes - Enterprise plans support single sign-on via SAML, so account access can be managed through your existing identity provider.
Can we pay by invoice instead of card?
Yes - Enterprise plans support annual billing and invoicing, including purchase orders where required.
What happens to our data if we downgrade later?
Retention follows the same rules as our standard tiers - see the Data Retention Policy - and we will work with you directly on any custom retention terms agreed as part of an Enterprise contract.
How many monitors can an Enterprise plan support?
There's no fixed cap - Enterprise plans go well beyond the 300-monitor limit on Max and are sized to however many endpoints, heartbeats and domains you need to track.
Can Enterprise plans include multiple teams or business units?
Yes - role-based access lets you segment monitors, status pages and alert routing by team or business unit, so a single Enterprise account can support several groups without them seeing each other's configuration.