Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by FatSync Software Private Limited · spike.sh

Report an error on this page Is this your product? →

Link to this page

Spike.sh: AI-assisted analysis on whats-best.ai Spike.sh: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Spike.sh at a glance

Vendor
FatSync Software Private Limited
Headquarters
Incorporated in India source, captured 6 Nov 2026
Data hosting
Outside the EU by default source, captured 6 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 6 Nov 2026
Panel verdict
The AI panel rates Spike.sh 3/5, the mean of 6 judges. Spike.sh is an on-call and incident management platform from FatSync Software Private Limited of Pune, India. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

Spike.sh alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

Spike.sh is an on-call and incident management platform from FatSync Software Private Limited of Pune, India. Scores peak on alerting and routing and incident response, both at 7: delivery across phone, SMS, push, email and chat, with phone and SMS in over 100 regions, routing rules with documented grouping and suppression, live call routing over Twilio or Plivo with call logs and recordings, and incidents carrying timelines, war rooms, auto-drafted postmortems and status pages on every plan. Lowest marks went to reliability and compliance and sovereignty, both at 4, where we found no public information on an availability figure, an SLA with credits or certifications, and the chain runs from an Indian entity under Delhi courts through United States hosting to fourteen subprocessors located in the United States, with a published data processing addendum incorporating the 2021 Standard Contractual Clauses. Divergence is narrow: on-call scheduling and integration and administration run 6 to 7 over missing working-time exports and API limits, and pricing transparency runs 5 to 6, the lower marks weighing billing that counts maximum users rather than active users.

Report an error

Speaks for it

  • Live call routing over Twilio or Plivo numbers with call logs, recordings and a fallback chain, with phone and SMS delivery stated for over 100 regions.
  • Incidents carry severity and priority, a timeline, a Slack channel, war-room calls, an auto-drafted postmortem, and tracked time-to-acknowledge and time-to-resolve.
  • On-call schedules support unlimited layers with weekly, daily and follow-the-sun rotations, and escalations with unlimited levels that repeat until acknowledged.
  • A documented REST API with a downloadable OpenAPI specification covers incidents, escalations, on-call and status pages, alongside 170 named integrations.
  • A published data processing addendum incorporates the 2021 EU Standard Contractual Clauses and the UK transfer addendum, with a public subprocessor list.

Report an error

Held against it

  • We found no public information on an availability figure, an SLA with credits, or vendor certification such as ISO 27001 or SOC 2.
  • The contracting entity is FatSync Software Private Limited under Indian law with exclusive venue in the Delhi courts, production hosting is in the United States, and all fourteen listed subprocessors — OpenAI among them for the AI title rewriting — are located in the United States.
  • We found no public information on an EU hosting option or an EU contracting entity or representative.
  • Enterprise is contact sales, and we found no public information on the per-call price beyond the free allowance or on stakeholder and viewer seat pricing.
  • The API documentation states that granular API permissions are not supported and that requests are handled one team at a time.

Report an error

Best for

  • You need paging across phone, SMS, push and chat with rule-based routing, live call routing, call logs and recordings.
  • You are switching from OpsGenie: 20% off the first year on an annual plan is published for OpsGenie switchers.
  • You want incident workflows with timelines, war rooms, auto-drafted postmortems and a status page on every plan, from Standard at $7 per user per month, billed monthly, with a 14-day free trial the pages describe as requiring no credit card.
  • Your team automates through APIs and webhooks: the documented REST API, downloadable OpenAPI specification, webhooks and MCP support cover incidents, escalations, on-call and status pages.

Report an error

Avoid if

  • You require EU hosting or an EU contracting entity: hosting and all fourteen subprocessors are in the United States, the contracting entity is Indian, and we found no public information on an EU option.
  • You must enter a vendor in a third-party risk register with an SLA or certification: we found no public information on an availability figure, an SLA with credits, or vendor certification.
  • Your procurement must compute a full annual cost from public pages — ask the vendor: the public pages we read do not show it
  • You need more than one on-call rotation from day one: the Standard plan includes a single on-call schedule, with unlimited schedules on Business and Enterprise.

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

On-call schedules, rotations & escalation

Show reasoning
How this is scored

Who is on call and what happens when nobody answers: schedules with daily, weekly and custom rotations, layers and follow-the-sun hand-offs across time zones, overrides, swaps and holiday cover, escalation policies with timeouts, repeat and fallback levels, round-robin and team escalation, calendar export and sync, reminders before a shift, on-call reports and hours exported for on-call pay and working-time rules, and a mobile app that shows the shift and lets a responder hand it over.

0 — No schedules or escalation of any kind; alerts go to a fixed list of people.

3 — A simple weekly rotation and one escalation step; overrides, layers, time zones and on-call reports are basic or not described.

5 — Schedules with several rotation types and layers, overrides and swaps from the app, escalation policies with timeouts and several levels, time-zone handling, calendar export, shift reminders, and a report of who was on call when.

8 — Follow-the-sun and multi-team schedules, round-robin and conditional escalation, coverage gaps flagged before they happen, schedules and policies managed as code or by API, and on-call hours exported per person for pay and working-time rules, all documented.

10 — Scheduling a large organisation runs on: every feature above with fairness and fatigue reports, rest-period rules enforced or warned, schedules imported from HR or workforce tools, and every scheduling limit documented per plan.

Report an error

The SRE Lead

Layers with their own members, rotation and handoff times, follow-the-sun rotations, drag-and-drop and plain-English overrides from chat, and escalations with unlimited levels that repeat until acknowledged are all documented, with schedules and overrides reachable through the API. I found no public information on coverage-gap warnings, on-call hours exported per person for pay and working-time rules, or round-robin escalation, so it sits below the top band. 2 3 9 16 17

Report an error

The IT Operations Manager

Schedules are built from layers with their own members, rotations and handoff times, with weekly, daily and follow-the-sun rotations, unlimited escalation levels that repeat until acknowledged, an acknowledge timeout, and overrides by drag-and-drop swap or in plain English from chat — that covers our five-admin weekly standby, and the schedule calendar plus the who's-on-call answer in Slack tells me who carries the pager at 3 a.m. Schedules, overrides and escalation policies are also reachable through the documented API. We found no public information on calendar export, warnings for coverage gaps before they happen, or exporting on-call hours per person for pay and working-time rules. 2 3 9 16 17

Report an error

The MSP NOC Lead

Schedules are built from layers, each with its own members, rotation and handoff times, follow-the-sun rotations, drag-and-drop swaps and overrides from chat, and schedules, overrides and escalations are reachable through the documented API — enough to model a night-shift layer and a rota per key account, with unlimited escalation levels that repeat until acknowledged and per-severity policies. I found no public information on coverage-gap warnings before they happen or an export of on-call hours for pay and working-time rules, which my night crew needs, and the single schedule on Standard means Business tier at minimum for us. 2 3 9 10 16 17

Report an error

The ICT Risk Officer

Weekly, daily and follow-the-sun rotations, unlimited schedule layers with their own members and handoff times, overrides created in chat or by drag-and-drop, and unlimited escalation levels that repeat until acknowledgement are all documented, with schedules and overrides also reachable through the API; escalation changes are versioned with a diff, which matters when I must show who altered the paging chain. The lowest plan allows a single schedule. We found no public information on calendar export, warnings for coverage gaps before they happen, or exported on-call hours for pay and working-time rules. 2 3 9 10 16 17

Report an error

The Engineering Manager

The documentation covers unlimited layers with handoff times, weekly, daily and follow-the-sun rotations, swaps by drag-and-drop or in plain English in chat, and escalations with unlimited levels, acknowledgement timeouts and repeat-until-acknowledged, plus API coverage of on-call and overrides. What I personally need for our works council is missing from the public pages: we found no public information on on-call hours exported per person for payroll, rest-period or fatigue warnings, or coverage gaps flagged before they happen. The plan table shows reports of only an overview on the entry plan, with custom reports on the higher tiers. 2 3 9 16 17 10

Report an error

The Skeptic

Weekly, daily and follow-the-sun rotations, unlimited layers with documented precedence rules, overrides by drag-and-drop or in plain English in chat, and escalation policies with unlimited levels, acknowledge timeouts, versioned diffs and a per-step trace are all documented, and the API covers on-call schedules and overrides. What holds it back is that I found no public information on coverage-gap warnings before a shift, calendar export to a personal calendar, or on-call hours exported for pay and working-time rules — and the Standard plan buys exactly one schedule. 2 3 9 10 16 17

Report an error

Alert delivery, routing & noise reduction

Show reasoning
How this is scored

Whether the alert reaches a human and only the right one: notification by push, SMS, voice call, email and chat, critical alerts that override do-not-disturb on iOS and Android, personal notification rules with retries and fallbacks, acknowledgement by app, SMS reply or keypad, delivery receipts, live call routing for a hotline, routing rules by service, severity, payload and time, deduplication, grouping and correlation of related alerts, suppression and maintenance windows, heartbeats for silent failures, and inbound email and webhook endpoints.

0 — Sends no alerts to people; a dashboard or log viewer only.

3 — Push and email notifications with acknowledgement; SMS, voice, routing rules and noise reduction are basic or not described.

5 — Push, SMS, voice and email with personal notification rules and retries, critical alerts on mobile, acknowledgement from the app or by phone, routing by service and severity, deduplication, and maintenance windows.

8 — Alert grouping or correlation with its logic documented, routing on payload fields and time conditions, delivery receipts and a notification log per alert, live call routing, heartbeat monitoring, suppression rules, and the countries and channels where SMS and voice are delivered stated.

10 — Delivery that is evidenced, not promised: redundant SMS and voice carriers named with automatic failover, delivery statistics published, AI or rule-based noise reduction with measurable results, and every notification limit per plan documented.

Report an error

The SRE Lead

Grouping and de-duplication are documented down to the mechanics — the incident title acts as the identifier for grouping, suppression and auto-resolution, and webhook repeats against an open same-titled incident create nothing new — with routing rules on title, details, priority, severity, time of day and day of week. Live call routing over Twilio or Plivo with call logs, recordings and a fallback chain is documented in depth and phone and SMS are stated for over a hundred regions; I found no public information on heartbeat monitoring for silent failures or per-alert delivery receipts. 3 10 18 19 23

Report an error

The IT Operations Manager

Delivery spans phone, SMS, push, email and chat with do-not-disturb bypass, grouping and deduplication driven by the incident title, suppression rules, and routing conditions on title, details, severity, priority, time of day and days of the week — that is close to what I need to turn a monitoring alert into an acknowledged phone escalation with the deputy paged after a timeout. Live call routing over Twilio or Plivo is documented down to fallback responders, call logs and recordings, and phone and SMS delivery is stated for over a hundred regions. We found no public information on heartbeat monitoring for silent failures, delivery receipts per notification, or acknowledging the voice call by keypad; the suppression rules are the documented answer for quiet periods, though a maintenance-window feature for alerting itself is not described. 3 8 18 19 23

Report an error

The MSP NOC Lead

Phone, SMS, push, email, WhatsApp, Telegram, Discord, Slack and Teams delivery is documented with do-not-disturb bypass, acknowledgement timeout and reminder, and escalation that repeats until acknowledged, and phone and SMS are stated for over a hundred regions. Routing rules on title, details, priority, severity, time of day and days of week, with grouping, deduplication, suppression and auto-resolve, cover routing by customer and contract hours, and live call routing with a primary plus two fallback responders, call logs and recordings is well documented. I found no public information on delivery receipts, a notification log per alert or heartbeat monitoring for silent failures. 3 8 10 18 19 23

Report an error

The ICT Risk Officer

Delivery across phone, SMS, push, email, Slack, Teams, WhatsApp, Telegram and Discord with a do-not-disturb override, and routing rules on title, payload details, severity, priority, time of day and days of week, are documented alongside title-based grouping and suppression with the logic explained, auto-resolution of known noise, and live call routing with a two-fallback chain, recordings and per-call logs. Phone and SMS are stated for over a hundred regions. We found no public information on delivery receipts, a notification log per alert, or heartbeat monitoring for silent failures. 1 3 8 10 18 19 23

Report an error

The Engineering Manager

Phone, SMS, push, email and chat including WhatsApp, Telegram and Discord, with a stated do-not-disturb bypass, deduplication and grouping by title documented, routing conditions on title, details, repeated incidents, priority, severity, time of day and days of week, suppression rules, and live call routing on Twilio or Plivo numbers with call logs, recordings and a primary-plus-two-fallback chain. Phone and SMS delivery is stated for over 100 regions. We found no public information on heartbeats for silent failures or delivery receipts per notification. 1 3 8 10 18 19 23

Report an error

The Skeptic

Grouping logic is actually documented — the title is the identifier for grouping, suppression and auto-resolution — routing conditions cover title, details, priority, severity, time of day and day of week, and live call routing with Twilio or Plivo numbers, a fallback chain, call logs and recordings is described in unusual detail, with phone and SMS stated for over a hundred regions. But I found no public information on heartbeats for silent failures or per-notification delivery receipts, and while Twilio and Plivo are named as the SMS and voice providers in the subprocessor list, no automatic carrier failover or delivery statistics are published. 3 7 10 15 18 19 23

Report an error

Incident response, status pages & post-incident review

Show reasoning
How this is scored

What happens once the alert is a real incident: declaring an incident from Slack, Microsoft Teams or the app, a dedicated channel and video bridge, incident roles and commander, severities and incident types, runbooks, tasks and automated workflows, stakeholder updates, public and internal status pages with subscribers, a timeline, post-incident reviews and postmortem templates with follow-up actions, analytics such as MTTA and MTTR, and AI features that summarise, suggest causes or draft the review.

0 — No incident record of any kind beyond the alert itself.

3 — An incident list with status and notes; channels, roles, status pages and post-incident reviews are basic or not described.

5 — Incidents declared from chat or the app with severities, a Slack or Teams channel created, incident roles, a timeline, a public status page, stakeholder notifications, postmortem templates, and MTTA and MTTR reports.

8 — Workflows and runbooks that automate the response, incident types with their own process, internal and public status pages with components and subscribers, follow-up actions tracked into Jira or Linear, service catalogue and dependencies, and AI summaries with their data handling described.

10 — A response process a regulated enterprise runs on: every feature above with major-incident and regulatory reporting templates, cross-team analytics and learning reviews, AI features documented with model provider, data handling and an opt-out, and every limit per plan stated.

Report an error

The SRE Lead

Incidents get a Slack channel opened from the thread, a timeline, severity and priority, war-room calls, a status page on every plan with components and subscribers, and a post-mortem that arrives auto-drafted, with AI titles, severity suggestions and root-cause hints in Slack and the OpenAI processing behind the AI named in the data processing addendum. I found no public information on incident roles like a commander, a service dependency catalogue, or follow-up actions tracked into the ticket tools, so I hold it just under the top band. 6 10 20 21

Report an error

The IT Operations Manager

Incidents carry severities and priorities, get an AI-written title and an auto-drafted postmortem, can open a Slack channel and a war-room call, keep a timeline with acknowledgement and resolution times, and push tickets to Linear, Jira or ClickUp. Public and private status pages come with components, subscribers over email, Slack, RSS and Atom, planned maintenance with reminders, and the AI model provider appears in the published subprocessor list, which is more disclosure than most. We found no public information on incident commander roles, a service catalogue with dependencies, or follow-up actions from the review being tracked into the ticketing tools. 5 6 10 20 21

Report an error

The MSP NOC Lead

Every incident carries severity and priority, gets a timeline, can open a Slack channel, pull responders into a war room, take a resolution note and an auto-drafted postmortem, with time to acknowledge and time to resolve tracked — the raw material for a monthly response report per customer. Public and internal status pages with components, subscribers on email, Slack, RSS and Atom, maintenance windows and custom domains are on every plan, with private pages from Business up, and the data processing addendum names OpenAI as the processor behind the AI title rewriting. I found no public information on incident roles such as a commander, or on follow-up actions tracked to closure beyond pushing incidents to Linear, Jira or ClickUp. 5 6 10 15 20

Report an error

The ICT Risk Officer

Severities and priorities, a timestamped timeline, a Slack channel per incident, war-room calls, resolution notes, an auto-drafted postmortem and time-to-acknowledge and time-to-resolve figures are documented, together with public and private status pages carrying components, subscribers and planned maintenance; the escalation-step trace is what I would lean on as evidence for the regulator. The AI that writes titles and summaries runs through OpenAI, named in the subprocessor list. We found no public information on incident commander roles, incident types with their own process, a service catalogue with dependencies, or any major-incident or regulatory reporting template. 5 10 12 15 20 21

Report an error

The Engineering Manager

Severities, an incident timeline, war rooms with video, a Slack channel per incident, an auto-drafted post-mortem, time-to-acknowledge and time-to-resolve tracked, public and private status pages with components and subscribers by email, Slack, RSS or Atom, tickets pushed to Linear, Jira or ClickUp, and AI summaries with root-cause hints in Slack and over MCP. OpenAI is named in the data processing addendum as the subprocessor powering the AI title rewriting, which is more transparency than most. We found no public information on a dedicated incident commander role or a service catalogue with dependencies. 5 6 10 15 20 21

Report an error

The Skeptic

A Slack channel per incident, war-room calls, a timeline, severities, public and internal status pages with components, subscribers and planned maintenance, auto-drafted postmortems, time-to-acknowledge and time-to-resolve tracked, plus automated actions that route to another team, resolve by timer or fire webhooks and GitHub workflows — a real slice of the higher level. I found no public information on incident roles such as a commander, postmortem follow-up actions tracked into ticketing, or a service catalogue; the AI that titles incidents names OpenAI in the data processing addendum, but there is no published opt-out. 5 6 10 15 18 20 21

Report an error

Integrations, API & administration

Show reasoning
How this is scored

How the tool fits the stack and the organisation: inbound integrations with monitoring and observability tools (Prometheus, Grafana, Datadog, Zabbix, Checkmk, PRTG, Azure Monitor, CloudWatch, Sentry), outbound integrations with chat, ticketing and ITSM tools (Slack, Microsoft Teams, Jira, ServiceNow, ConnectWise, Autotask), bidirectional sync, a documented REST API, webhooks and a Terraform provider, teams and services, roles and permissions, single sign-on (SAML or OIDC) and SCIM, audit logs, multi-tenant or customer separation for service providers, and migration help from other tools.

0 — No integrations and no administration beyond a single shared account.

3 — Email and webhook intake and a few named integrations; the API, roles and single sign-on are basic or not described.

5 — Dozens of named inbound and outbound integrations including Slack or Teams and Jira, a documented REST API and webhooks, teams with roles, two-factor authentication, single sign-on, and an import path from at least one other tool.

8 — Bidirectional ITSM and ticketing sync, a Terraform provider or configuration as code, SCIM provisioning, granular roles per team, audit logs, service-provider or multi-tenant set-ups, and API coverage of schedules, escalations and incidents documented.

10 — Administration that scales across many teams and customers: every setting reachable by API with parity stated, audit logs exportable to a SIEM, SSO enforced with SCIM, white-label or sub-account management for service providers, and documented migration from the major competitors.

Report an error

The SRE Lead

A hundred seventy integrations including Prometheus, Grafana and Sentry inbound plus Slack, Teams, Jira and Linear outbound, and a documented REST API with a downloadable OpenAPI spec covering incidents, escalations, on-call, status pages and subscribers. The documentation itself states granular API permissions are not supported and requests run one team at a time, role-based access and audit logs sit in higher plans with SAML single sign-on Enterprise-only, and I found no public information on a Terraform provider, SCIM provisioning or bidirectional ticket sync. 7 9 10 20 22

Report an error

The IT Operations Manager

A hundred and seventy named integrations including Slack, Microsoft Teams and Jira, a documented REST API with a downloadable OpenAPI specification covering teams, escalations, on-call schedules and incidents, webhooks on shift and incident events, role-based access and audit logs on the higher plans, and a 20 percent first-year migration offer from OpsGenie give it real substance. The API is team-scoped, one team per request, and the documentation itself states granular API permissions are not supported at the moment. I found no public information naming Checkmk or PRTG among the integrations, though a generic webhook intake exists, and none on a Terraform provider, SCIM provisioning or bidirectional ticketing sync. 7 9 10 20 22

Report an error

The MSP NOC Lead

A hundred and seventy integrations including Datadog, Prometheus, Grafana and Sentry inbound, a documented REST API with a downloadable OpenAPI specification covering incidents, escalations, on-call, overrides and status pages, and an OpsGenie migration offer with twenty percent off the first year give the tool real legs. Roles are tiered — role-based access from Business, single sign-on and audit logs on Enterprise — and the API documentation itself states that granular API-key permissions are not supported at the moment. I found no public information on connectors for Autotask, ConnectWise or ServiceNow, on two-way ticket sync, SCIM provisioning or a Terraform provider, which is the PSA and identity glue my stack runs on. 4 7 8 9 10 20 22

Report an error

The ICT Risk Officer

A hundred and seventy named integrations including Datadog, Prometheus, Grafana and Sentry inbound and Jira, Linear and ClickUp outbound, plus a documented REST API with a downloadable OpenAPI specification covering on-call, escalations, incidents and status pages, take this past a basic catalogue; single sign-on, audit logs and role-based access are stated but only on Enterprise. The captured pages state plainly that granular API permissions are not supported and requests are handled one team at a time, and we found no public information on SCIM provisioning, a Terraform provider, or bidirectional ticketing sync. 4 7 9 10 20 22

Report an error

The Engineering Manager

170 integrations with named monitoring tools plus Slack, Teams, Linear, Jira, ClickUp and helpdesk tools, a documented REST API with a downloadable OpenAPI specification covering incidents, escalations, alert rules, on-call, overrides and status pages, MCP support, role-based access control and audit logs on higher plans, and SAML single sign-on only on the Enterprise tier. An OpsGenie migration offer of 20% off the first year exists. We found no public information on SCIM provisioning, a Terraform provider, bidirectional ticket sync or two-factor authentication. 7 9 10 20 22

Report an error

The Skeptic

A hundred and seventy named integrations including Slack, Teams, Jira, ClickUp, Linear, Zendesk and Freshdesk, a documented REST API with a downloadable OpenAPI specification covering incidents, escalations, on-call and status pages, webhooks, an MCP server, SAML single sign-on on Enterprise and audit logs on Enterprise. But I found no public information on SCIM provisioning, a Terraform provider or bidirectional ticketing sync; granular API permissions are stated as not supported, requests are team-scoped one team at a time, and the OpsGenie path is a first-year discount rather than documented import tooling. 7 9 10 20 22

Report an error

Platform reliability, security & compliance

Show reasoning
How this is scored

Whether the pager works on the day everything else is down and holds up in an audit: an architecture independent of the customer's own cloud, multi-region or multi-zone hosting with failover, a stated availability or SLA with credits, the vendor's own public status page and incident history, delivery via redundant carriers, encryption in transit and at rest, security certifications (ISO 27001, SOC 2, BSI C5), penetration tests, data retention and deletion, audit trails, and what the vendor documents for DORA, NIS2, HIPAA or other regulated customers.

0 — Nothing on availability, security or how the service is operated.

3 — A claim of high availability or "enterprise security"; the SLA, status page, certifications and architecture are basic or not described.

5 — A public status page, a stated availability or SLA, hosting regions named, encryption in transit and at rest, ISO 27001 or SOC 2 stated, and data retention described.

8 — An SLA with credits published, the incident history public, multi-region failover or redundancy documented, redundant notification carriers named, certifications with their scope, a trust centre with reports on request, and a DORA or NIS2 addendum or mapping offered.

10 — Operation evidenced end to end: failover tested and published, independent audits (ISO 27001, SOC 2 Type II, BSI C5) with reports available, regulatory obligations for financial and critical-infrastructure customers explained in plain language, and the vendor's own post-incident reviews public.

Report an error

The SRE Lead

There is a public status page with components and 90-day history, hosting named in the United States, encryption in transit and at rest, and backups retained no more than 30 days with deletion inside 30 days. I found no public information on a stated availability figure or an SLA with credits, vendor certifications like ISO 27001 or SOC 2, multi-region failover, or anything for DORA or NIS2 customers; the security page invites a conversation about certifications rather than showing them. 11 12 13 14

Report an error

The IT Operations Manager

There is a public status page with a ninety-day history, hosting in the United States is stated, encryption in transit and at rest, hashed passwords, backups overwritten within thirty days, a published data processing addendum with the 2021 Standard Contractual Clauses, seventy-two-hour breach notification and customer audit rights. For a service my plants must page me through, the gaps matter: we found no public information on a stated availability figure or an SLA with credits — the terms only hint at a service-credit mechanism with a 45-day claim window — on multi-region failover, on ISO 27001 or SOC 2 certification for the company itself (the security page speaks of ISO and FedRAMP data centres), on penetration tests, or on guidance for NIS2 or DORA customers. 11 12 13 14 15

Report an error

The MSP NOC Lead

There is a public status page with a ninety-day history and per-component status for the API, dashboard, integrations and SMS, encryption in transit and at rest, hashed passwords, thirty-day backup retention and deletion, and a seventy-two-hour breach-notification commitment. The security page points to ISO- and FedRAMP-standard data centres and offers a talk about certifications, but I found no public information on an availability figure, a published SLA with credits, multi-region failover, penetration tests, or a vendor certification such as ISO 27001 or SOC 2 — thin cover for the audits my customers put us through. 11 12 13 14 15

Report an error

The ICT Risk Officer

There is a public status page with ninety days of history, named United States hosting, encryption in transit and at rest, thirty-day deletion, and contractually a published data processing addendum with the 2021 EU Standard Contractual Clauses, the UK transfer addendum, seventy-two-hour breach notification, audit rights and subprocessor objection rights. What I cannot accept for a tool in my third-party register: we found no public information on a stated availability figure or an SLA with credits, vendor certifications such as ISO 27001 or SOC 2, multi-region failover, penetration tests, or anything on DORA or NIS2, and the terms supply the service as-is with liability capped at one month's fees. 11 12 13 14 15

Report an error

The Engineering Manager

There is a live public status page with 90-day history, the United States hosting region is named, encryption in transit and at rest is stated, backups are retained no more than 30 days, and the data processing addendum commits to 72-hour breach notice, audit rights and subprocessor liability. The security page describes ISO and FedRAMP-standardised data centres and invites a talk about certifications. We found no public information on an availability SLA with credits, the vendor's own ISO 27001 or SOC 2 certification, multi-region failover or penetration tests. 11 12 13 14 15

Report an error

The Skeptic

There is a public status page with 90 days of history, a named hosting region (the United States), encryption in transit and at rest, backup retention within 30 days, a data processing addendum with 72-hour breach notification, and a published subprocessor list — real, but not an audit file. The terms hint at service credits for errors reported within 45 days, yet no availability figure or SLA percentage is published; the security page points to ISO and FedRAMP data centres rather than any certification of the vendor itself, and I found no public information on multi-region failover, penetration tests, or DORA and NIS2 documentation. 11 12 13 14 15

Report an error

European sovereignty panel opinion

Show reasoning
How this is scored

Who the contracting entity and the parent company are, where alerts, incident timelines, chat transcripts, contact data, phone numbers and account data are stored and processed, and who the subprocessors are (hosting, SMS and voice carriers, push services, email delivery, AI summary and transcription models, analytics, support and payment tools). Independently sourced by the sovereignty pipeline. Telephony and push providers needed to reach a responder in another country are part of what the product does and are not counted against it; where the data is stored and who processes it is. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (SMS and voice, AI, support, payment) run through non-EU providers without a stated safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every record on the customer's own servers.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including the AI models and notification carriers, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.

Report an error

The SRE Lead

The chain is documented end to end and it is entirely non-European: an Indian company under Indian law with Delhi courts, production hosting in the United States, all fourteen named subprocessors — including AWS, Twilio, Plivo and OpenAI for the AI features — in the United States, and India-based personnel accessing production. A data processing addendum with the 2021 Standard Contractual Clauses and the UK transfer addendum is published, with notice and objection rights on subprocessor changes, but no EU hosting option is evidenced anywhere. 13 14 15

Report an error

The IT Operations Manager

The contracting entity is FatSync Software Private Limited of Pune, India, under Indian law with venue in Delhi, and production infrastructure, databases and all fourteen listed subprocessors — AWS, MongoDB Atlas, OpenAI, Twilio, Plivo, SendGrid among them — are in the United States, with the vendor stating its personnel in India access production systems. A published data processing addendum incorporates the 2021 EU Standard Contractual Clauses and the UK transfer addendum, and subprocessors are listed with locations, fourteen days' notice of changes, objection rights and termination rights. We found no public information on EU hosting options or a European contracting entity or representative. 13 14 15

Report an error

The MSP NOC Lead

The contracting entity is FatSync Software Private Limited of Pune under Indian law with venue in Delhi, production infrastructure and databases are hosted in the United States, and the published subprocessor list names fourteen providers, every one located in the United States, OpenAI included for the AI rewriting of alert payloads. A data processing addendum incorporating the EU standard contractual clauses and the UK transfer addendum is published, with breach notification, audit rights and a right to object to new subprocessors, which is more transparency than many show. For my German customer base this remains a hard sell: we found no public information on a European hosting option or an EU contracting entity, and Indian personnel access to production systems is documented. 13 14 15

Report an error

The ICT Risk Officer

The contracting entity is an Indian company under Indian law with exclusive venue in Delhi, production infrastructure and databases sit in the United States, personnel access production from India, and all fourteen published subprocessors — AWS for hosting, Twilio, Plivo and SendGrid for notification, and OpenAI for the AI rewriting of raw alert payloads into incident titles — are located in the United States. The chain is at least papered: a published data processing addendum incorporates the EU Standard Contractual Clauses and the UK transfer addendum, with fourteen days' notice and a right to object before a new subprocessor starts. We found no public information on EU hosting, an EU contracting entity or representative, or a self-hosted edition. 13 14 15

Report an error

The Engineering Manager

The contracting entity is FatSync Software Private Limited in India with the courts of Delhi as venue, production infrastructure and databases are hosted in the United States, and a published subprocessor list names fourteen providers all located in the United States, including OpenAI for the AI features and Twilio, Plivo and SendGrid for delivery, with personnel access to production from India. A data processing addendum incorporating the 2021 EU Standard Contractual Clauses and the UK IDTA is published, with 14 days' notice and an objection right for new subprocessors. No EU hosting option appears in the captured pages, so for us in Hamburg this is a US and India chain end to end. 13 14 15

Report an error

The Skeptic

The contracting entity is FatSync Software Private Limited of Pune, India, under Indian law and the exclusive jurisdiction of the Delhi courts; production infrastructure and databases sit in the United States, and all fourteen published subprocessors — including AWS, Twilio, SendGrid, Intercom and OpenAI, added in September 2026 for the AI title rewriting — are located in the United States. Credit where due: the subprocessor list is public with locations, a data processing addendum incorporating the 2021 Standard Contractual Clauses and the UK transfer addendum is offered, with 14 days' notice and objection rights on new processors; still, no EU hosting option and no EU entity are offered, so the entire chain runs through the US. 13 14 15

Report an error

Pricing transparency

Show reasoning
How this is scored

Whether a buyer can compute the real annual cost from public pages alone: price per user or responder and per plan, whether stakeholders and viewers are free, how many SMS and voice notifications are included and what the rest cost per country, which features (incident response, status pages, AI, live call routing, SSO, audit logs) are add-ons or in higher plans, platform fees, minimum seats, annual versus monthly billing, and the currency and VAT treatment.

0 — No public prices at all; every customer is a sales call.

3 — A starting price per user exists, but notification limits, add-ons and the enterprise tier are unclear.

5 — Plans are public with their price per user and main inclusions, but at least one commonly needed piece (SMS and voice volume, status pages, AI, SSO or the top tier) is unpriced or "contact sales".

8 — Every plan priced publicly with its scaling rule, notification limits and overage prices stated, add-ons priced, stakeholder seats explained, minimum term and billing options and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given number of responders, stakeholders, notifications and status pages, with every add-on, overage and support fee and the cancellation and data-export terms published.

Report an error

The SRE Lead

Standard at $7 and Business at $14 per user per month, billed monthly, are published with unusually granular inclusions — 100 alerts per month shared across phone and SMS on Standard, unlimited on Business, plan limits on schedules, central phone numbers and API requests, and which plans carry role-based access, audit logs and SAML. Enterprise is contact sales, the terms mention charges for calls beyond a free allowance without stating a price, and I found no public information on stakeholder or viewer seats; the terms also state billing runs on maximum users per month rather than active users. 10 13 19

Report an error

The IT Operations Manager

Standard at $7 per user per month and Business at $14 per user per month are published with their inclusions — one on-call schedule on Standard against unlimited above, one hundred phone and SMS alerts per month shared across both on Standard against unlimited on Business, audit logs, SAML single sign-on and role-based access held back for Enterprise — plus an annual option of one month free, pro-rated seat changes, credit card or wire payment through Stripe, a fourteen-day trial without a card, and terms stating taxes are not included and billing follows maximum rather than active users. The Enterprise tier is contact sales, and we found no public information on the per-call overage price beyond the terms' reference to charges after a limited free allowance, or on whether stakeholder or viewer seats are free. 10 13 21

Report an error

The MSP NOC Lead

Standard at $7 per user per month and Business at $14 are published with per-plan limits for phone and SMS volume, API requests, on-call schedules and central phone numbers, annual billing with a month free, self-serve cancellation with pro-ration, and the terms state taxes are not included and billing counts maximum users rather than active ones. The Enterprise tier is contact sales, so single sign-on and audit logs carry no public price, and the terms say calls beyond a free allowance are charged per call without naming the rate. I found no public information on stakeholder or viewer seat pricing. 10 13 19 21

Report an error

The ICT Risk Officer

Standard at $ 7 and Business at $ 14 per user / month, billed monthly are published with unusually explicit per-plan inclusions and exclusions — audit logs, single sign-on, role-based access, schedule counts, central phone numbers and API request caps are each stated per plan — along with the annual option with one month free, taxes not included in fees, single-click cancellation, proration, and the terms' maximum-users-per-month billing basis. What blocks a full annual cost computation: the Enterprise tier is contact sales, calls beyond the free allowance are described only as charged per call with no per-country price, and we found no public information on stakeholder or viewer seat pricing. 10 13 19

Report an error

The Engineering Manager

Standard at $ 7 and Business at $ 14 per user, billed monthly, are public with their inclusions, including the 100 alerts per month shared across phone and SMS on Standard and unlimited phone and SMS on Business, annual billing with 1 month free, taxes not included, and pro-rated add and remove of team members. The Enterprise tier is Contact Sales, the per-call charge beyond the free calls is not priced publicly, and we found no public information on free stakeholder or read-only seats — the terms bill for the maximum users per month, which for us would charge the managers who only read along. 10 13

Report an error

The Skeptic

Standard at $7 per user per month and Business at $14 per user per month are public with their inclusions — 100 alerts a month shared across phone and SMS on Standard, unlimited phone and SMS on Business — plus per-plan API request limits, schedule counts, SSO and audit-log gating, monthly or annual billing with one month free, and terms stating that taxes are not included and billing counts maximum users, not active ones. But the Enterprise tier is contact sales, the price per call once the included calls run out is not published anywhere I read, and I found no public information on stakeholder or viewer seats — a buyer cannot compute the annual cost of responders plus observers from the public pages alone. 10 13

Report an error

European sovereignty — proven facts

3 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Outside the EU 0/4 pts 15 Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Published, self-serve unverified
Why unverified?

The GDPR page links to the DPA for review, but the DPA document itself is not among the excerpts.

1/1 pts 15 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Spike.sh

Is Spike.sh European?

No. whats-best.ai classifies Spike.sh as Rest of world. Its vendor, FatSync Software Private Limited, is incorporated in India, per the vendor’s page captured 6 Nov 2026.

Where does Spike.sh store data?

Spike.sh stores customer data outside the EU by default, per the vendor’s page captured 6 Nov 2026.

Does Spike.sh have a free plan?

Yes. Spike.sh has a free plan, per the vendor’s page captured 6 Nov 2026.

What are the best alternatives to Spike.sh?

As of 18 Nov 2026, the panel rates ilert (4/5), All Quiet (3.5/5) and OneUptime (3.5/5) highest among the other 16 On-Call & Incident Management products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is ilert (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Spike.sh alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (23)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage spike.sh Checked 6 Nov 2026 Details →
  2. 2 Features page (on-call) spike.sh Checked 6 Nov 2026 Details →
  3. 3 Features page (escalations) spike.sh Checked 6 Nov 2026 Details →
  4. 4 Features page (alert routing) spike.sh Checked 6 Nov 2026 Details →
  5. 5 Features page (incidents) spike.sh Checked 6 Nov 2026 Details →
  6. 6 Features page (status pages) spike.sh Checked 6 Nov 2026 Details →
  7. 7 Integrations page spike.sh Checked 6 Nov 2026 Details →
  8. 8 Documentation docs.spike.sh Checked 6 Nov 2026 Details →
  9. 9 API documentation docs.spike.sh Checked 6 Nov 2026 Details →
  10. 10 Pricing page spike.sh Checked 6 Nov 2026 Details →
  11. 11 Security / trust page spike.sh Checked 6 Nov 2026 Details →
  12. 12 Public status page status.spike.sh Checked 6 Nov 2026 Details →
  13. 13 Terms of service (names the operating company) spike.sh Checked 6 Nov 2026 Details →
  14. 14 Privacy policy spike.sh Checked 6 Nov 2026 Details →
  15. 15 GDPR page spike.sh Checked 6 Nov 2026 Details →
  16. 16 On-call schedules, rotations & escalation — found from sitemap docs.spike.sh Checked 6 Nov 2026 Details →
  17. 17 On-call schedules, rotations & escalation — found from sitemap docs.spike.sh Checked 6 Nov 2026 Details →
  18. 18 Alert delivery, routing & noise reduction — found from sitemap docs.spike.sh Checked 6 Nov 2026 Details →
  19. 19 Alert delivery, routing & noise reduction — found from sitemap docs.spike.sh Checked 6 Nov 2026 Details →
  20. 20 Incident response, status pages & post-incident review — found from sitemap spike.sh Checked 6 Nov 2026 Details →
  21. 21 Incident response, status pages & post-incident review — found from sitemap spike.sh Checked 6 Nov 2026 Details →
  22. 22 Integrations, API & administration — found from sitemap docs.spike.sh Checked 6 Nov 2026 Details →
  23. 23 Integrations, API & administration — found from sitemap docs.spike.sh Checked 6 Nov 2026 Details →