- Response
- 15 min
- Resolution
- 4 hrs
Site down, data loss, security incident.
Every Ironstar customer talks to a Site Reliability Engineer — not a call centre or chatbot. Our SREs split their time between platform engineering and live support, so you get support directly from the experts.
Most managed-Drupal SLAs commit to a response time and stop there. Ours commit to resolution targets — the time it takes to close the ticket, not to acknowledge it. Across our customer base, the median P1 resolution sits well inside the SLA ceiling.
Site down, data loss, security incident.
Significant degradation. Functionality impaired but service running.
Non-blocking issue. Configuration, advice, or scheduled change.
Feature request, documentation, low-priority planning.
Every SRE rotates through a two-week support window every two months. The rest of the time, they're shipping platform features, automation and runbooks — the things that prevent the next ticket.
It means support never feels like a separate team. The engineer who answers your P1 has commits in the very system that's failing.
On the support roster. Pager-on. Runbooks, customer calls, tickets, incident command.
Shipping features, fixing the root causes surfaced in the last rotation, writing the next runbook.
Drop our SREs into your Slack or Teams. No portal hops, no ticket numbers in subject lines — same place your team already coordinates.
All operational support is delivered by Australian-citizen engineers based in Australia. Every staff member completes AS4811-aligned employment screening before touching production.
Customers operating in Japan get Tier-1 support in Japanese, by Japan-resident engineers. Tier-2 and Tier-3 escalations route to the Australian SRE pool with full handover context.
Customer-impacting incidents are posted to ironstar-status.com with regular updates until the issue is resolved. Subscribe by email, RSS, or webhook to route notices straight into the channel your team already watches.
We offer multiple support tiers so coverage matches what the site is actually for. A pre-launch staging environment doesn't need 24×7 pager-on engineers; a national-broadcaster launch night does. Talk to us about traffic patterns, business hours, and budget — we'll shape a plan around the answer.
Business-hours support with after-hours pager for P1. Fits established sites with predictable traffic and modest change cadence.
Round-the-clock SRE coverage with 4-hour P1 resolution and a named TAM. Our most popular tier for media, government and national retailers.
Dedicated standby SREs for known-peak windows: live broadcasts, product launches, end-of-financial-year traffic. Activated alongside Standard or Always-On.
Don't see yours? Email support@ironstar.io — a real engineer will reply, usually inside the hour.
Tell us what you're running, where it hurts, and where you'd like to be. We'll listen, ask good questions, and tell you honestly whether we're the right fit.