# Spike.sh — On-Call & Incident Management

Spike.sh by FatSync Software Private Limited holds a panel rating of 3/5 from 6 AI judges (category median 3/5), as of 2026-11-06. Provenance: Rest of world; sovereignty: 3 of 6 dimensions proven.

- Vendor: FatSync Software Private Limited (https://spike.sh)
- Category: [On-Call & Incident Management](https://whats-best.ai/software/incident-management.md)
- Provenance (editorial classification): Rest of world
- Canonical page: https://whats-best.ai/software/incident-management/spike-sh
- Alternatives: https://whats-best.ai/software/incident-management/spike-sh/alternatives ([markdown](https://whats-best.ai/software/incident-management/spike-sh/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-06 · oldest source captured 2026-11-06

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## At a glance

- Vendor: FatSync Software Private Limited
- Headquarters: Incorporated in India [S13]
- Data hosting: Outside the EU by default [S15]
- Free plan: Yes, per the vendor’s own page [S2]

## 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.

**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.

**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.

**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.

**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.

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The SRE Lead | The IT Operations Manager | The MSP NOC Lead | The ICT Risk Officer | The Engineering Manager | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| On-call schedules, rotations & escalation | 3.5/5 | 3/5 | 3.5/5 | 3/5 | 3.5/5 | 3.5/5 |
| Alert delivery, routing & noise reduction | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Incident response, status pages & post-incident review | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Integrations, API & administration | 3/5 | 3/5 | 3/5 | 3/5 | 3.5/5 | 3/5 |
| Platform reliability, security & compliance | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 |
| European sovereignty | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 |
| Pricing transparency | 3/5 | 2.5/5 | 3/5 | 3/5 | 2.5/5 | 3/5 |
| **Weighted verdict** | **3/5** | **3/5** | **3/5** | **2.5/5** | **3/5** | **3/5** |

### The judges

- **The SRE Lead** (v1.0): Leads site reliability at a Berlin SaaS company with sixty engineers in eight product teams, Prometheus and Grafana for metrics, Sentry for errors and everything discussed in Slack. Wants an incident declared with one command, a channel with roles and a timeline, the status page updated from the same place, alerts grouped so one database outage does not page five teams, schedules kept in Terraform, and a postmortem that writes its first draft.
- **The IT Operations Manager** (v1.0): Runs IT operations for a packaging manufacturer with 900 staff and three plants running around the clock, with Checkmk and PRTG watching servers, networks and the production line. Five administrators share a weekly standby. Wants a Checkmk alert to become a phone call that the right person acknowledges by keypad, the deputy called after ten minutes, no pages during planned maintenance, and an alerting service that still works when the plant's own network is the thing that is down.
- **The MSP NOC Lead** (v1.0): Leads the network operations centre of a managed service provider in Nuremberg that looks after sixty mid-sized customers, with Zabbix, Microsoft Sentinel and Autotask in the stack. Wants alerts routed by customer and contract hours, tickets opened and closed in the PSA without anyone copying text, a separate on-call rota for the night shift and for each key account, one customer never seeing another's data, and a monthly report per customer on response times.
- **The ICT Risk Officer** (v1.0): ICT risk officer at a Frankfurt payments company supervised by BaFin, where DORA requires major ICT incidents to be classified and reported within hours. The incident tool is itself an ICT third-party service in the register. Reads the subprocessor list, asks where incident timelines and the AI summaries of the response channel are processed, wants an SLA, audit logs and a DORA addendum in the contract, and needs the timeline to hold up as evidence for the regulator.
- **The Engineering Manager** (v1.0): Engineering manager at a logistics software company in Hamburg with developers in Germany, Portugal and Poland, where the works council has agreed an on-call policy with paid standby hours and rest periods after a night call. Wants a follow-the-sun rota across three time zones, swaps from the phone, on-call hours exported to payroll each month, a warning when the same person is paged three nights running, and a price per responder that does not charge for the managers who only read along.
- **The Skeptic** (v1.0): Has seen "never miss an alert" from a pager that was down in the same cloud region as the outage it should have reported, "unlimited notifications" that meant twenty SMS a month outside the US, and an "AI incident assistant" that sent the whole response channel to a model nobody named. Asks which carriers deliver the calls, what the SLA pays, whether schedules and history can be exported when leaving — and what the plan costs once the stakeholders need seats.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: 3 of 6 dimensions proven.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Incorporated in IN | 0/2 | [S13] |
| Hosting location | Outside the EU | 0/4 | [S15] |
| Hosting options | Not determined | — | — |
| Open source | Not determined | — | — |
| Data processing agreement | Published, self-serve | 1/1 | [S15] |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- Analytics tool: Google Analytics [S14]
- Applicable laws: UK GDPR · UK Data Protection Act 2018 · India Digital Personal Data Protection Act 2023 [S15]
- Audit rights: yes [S15]
- Breach notification: 72 [S15]
- Complaint right: yes [S14]
- Cookie consent: yes [S14]
- Data subject rights: access · correction · deletion · restriction · objection · portability [S14]
- Deletion return: yes [S15]
- DPA available: yes [S15]
- DPA openai added: 2026-09-10 · OpenAI [S15]
- DPA version: 2.1 · 2026-09-29 [S15]
- Encryption: yes [S14]
- GDPR: yes [S1]
- GDPR: yes [S5]
- GDPR controller activities: Account registration and authentication · Billing and payment processing · Website analytics and performance monitoring · Marketing communications · Customer support interactions [S14]
- GDPR page: Security · Privacy policy · GDPR · Terms & conditions [S20]
- GDPR role processor: Data Controller · Data Processor [S14]
- India processing access: yes [S15]
- Scc transfers: 2021 · European Commission Standard Contractual Clauses (2021) · yes [S14]
- Security measures: firewall · encryption · access security · industry-standard [S13]
- Subprocessor liability: yes [S15]
- Subprocessor termination right: yes [S15]
- Transfer mechanism: yes [S15]
- UK idta: yes [S15]

**Data**
- Deletion after notice: yes · 30 [S13]
- Deletion contact: support@spike.sh [S14]
- Deletion SLA: 30 [S14]
- No selling: no [S14]
- Password hashing: yes [S14]
- Retention backups: 30 [S14]
- Subject requests: legal@spike.sh · 30 [S15]

**Hosting**
- Domains: spike.sh · *.spike.sh · spiked.sh · *.spiked.sh · fatsync.com · *.fatsync.com [S13]
- ISO fedramp datacenters: yes [S11]
- Region: United States [S15]
- Region US: United States [S14]
- Self domain hosting: yes [S6]

**Integrations**
- API: yes [S5]
- API auth: API key (x-api-key header) plus team id header (x-team-id) [S22]
- API create endpoint: https://api.spike.sh · POST /integrations/create [S22]
- API docs: yes [S21]
- API docs: Documentation · API · Changelog · Guides · FAQs [S20]
- API documented: yes · Resources [S4]
- API endpoint sections: Users · Orgs · Teams · Incidents · Actions On Incidents · Suppressed Incidents · Notes · Integrations · Escalations · Alert Rules · Services · On-call · On-call Overrides · Status Pages · Components · Status Page Incidents · Planned Mainte… [S9]
- API key location: Settings > API in Spike dashboard [S22]
- API read endpoint: GET /integrations/{token} [S22]
- Available route: /integrations/available [S22]
- Calendar channels: On-call schedule posted in Slack/Teams channels [S2]
- Categories: Infrastructure, APM, Website, Logs, More [S7]
- Connects monitoring tools: Spike connects to 80+ monitoring tools, cloud platforms, and error trackers, grouping and de-duplicating alerts [S7]
- Count: 80+ [S1]
- Count: 170 [S7]
- Create body fields: customName · desc · slug · escalation · service · repeatEscalation · ackTimeout [S22]
- Create responses: 400 · 401 [S22]
- Create scope: per team [S22]
- Cross org team rejected: 403 [S22]
- Escalation channels: Slack · Teams · phone · SMS [S20]
- Incident triggers: yes [S10]
- Linear: Sync duty to Linear [S2]
- Live call routing webhook setup: webhook URL into provider console [S19]
- Mobile apps: yes [S2]
- Mobile apps: iOS App Store · Google Play [S14]
- Mobile apps: App Store · Google Play [S21]
- Openapi spec download: yes [S9]
- Opsgenie migration: 2025-06-04 · 2027-04-05 [S7]
- Opsgenie migration: OpsGenie migration offer: 20% off first year [S10]
- Opsgenie migration offer: first year · 20 [S4]
- Opsgenie support dates: 2025-06-04 · 2027-04-05 [S4]
- Promotion: 20 [S7]
- Read error responses: 401 · 404 [S22]

**Legal**
- Company name: FatSync Software Pvt Ltd [S3]
- Company name: FatSync Software Pvt Ltd [S4]
- Company name: FatSync Software Pvt Ltd [S11]
- Company registration: India · Companies Act 1956 · L-3/404, Brahma Suncity, Vadgaonsheri, Pune-411014, Maharashtra, India [S13]
- Copyright: FatSync Software Pvt Ltd [S10]
- Entity: FatSync Software Pvt Ltd [S1]
- Entity: FatSync Software Pvt Ltd [S2]
- Entity: FatSync Software Pvt Ltd [S7]
- Entity: FatSync Software Pvt Ltd [S5]
- Entity: FatSync Software · 2026 [S12]
- Entity: FatSync Software Pvt Ltd [S21]
- Entity: FatSync Software Pvt Ltd [S20]
- Governing law: courts of Delhi, India · India [S13]
- Incorporation country: India [S15]
- Incorporation india: India [S14]
- Liability cap: aggregate liability capped at fees paid in preceding 1 month [S13]
- Operating company: FatSync Software Private Limited [S13]
- Operator: Spike · FatSync Software Private Limited [S14]
- Operator: FatSync Software Private Limited [S15]
- Opsgenie eol dates: 2025-06-04 · 2027-04-05 [S20]
- Opsgenie migration offer: yes [S13]
- Opsgenie migration terms: yes [S13]
- Related documents: Privacy policy · GDPR · Security (coming soon) [S13]
- Terms last updated: 2026-09-14 [S13]

**Pricing**
- Annual billing option: yes · 1 month free [S10]
- Auto renewal: yes [S13]
- Billing basis: billed for maximum users per month, not active users [S13]
- Billing periods: monthly · other mutually agreed periods [S13]
- Billing proration: yes [S10]
- Business price: monthly · 14 [S10]
- Business unlimited alerts: yes [S10]
- Calls included free: per call received per account · yes [S13]
- Cancellation: yes [S10]
- Enterprise price: custom quote per organisation · yes [S10]
- Error correction credit: 45 [S13]
- Fee revision notice: 30 [S13]
- Free tier: yes · no [S2]
- Free tier: yes [S5]
- Free trial: 14 · no [S1]
- Free trial: 14 · no [S14]
- Free trial: yes [S20]
- Free trial start: yes [S6]
- Live call routing availability: all paid plans [S19]
- Migration discount: 20 [S1]
- No refund downgrade: no [S13]
- Nonrenewal notice: 15 [S13]
- Opsgenie discount: annual plan, OpsGenie switchers · 20 [S10]
- Opsgenie migration discount: first year · OpsGenie migration · 20 [S5]
- Payment methods: credit card · wire transfer (annual, Business/Enterprise) · Stripe [S10]
- Promo: first year · OpsGenie migrators · 20 [S2]
- Promo opsgenie migration: 20 [S20]
- Standard alert limit: yes · 100 [S10]
- Standard price: monthly · 7 [S10]
- Suspension notice: 30 [S13]
- Taxes not included: no [S13]
- Trial: 14 [S10]
- Trial: 14 · no [S21]

**Product**
- Ack reminder: yes [S20]
- Acknowledge action: Acknowledge action creates incident in acknowledged state without sending alerts [S18]
- Acknowledge timeout: yes [S8]
- Actions: Actions: reassign to member, load escalation policy, change integration, ignore incident, mark priority, mark severity, trigger outbound webhook, acknowledge incident, resolve incident, resolve by timer, route to other team [S18]
- Active incidents: 0 [S12]
- Activity log: yes [S5]
- AI incident writing: AI writes incident title with suggested severity and priority [S5]
- AI rephrase: Compact · Technical · Elaborate [S5]
- AI severity priority: AI recommends severity and priority [S20]
- AI triage: Spike titles incidents, suggests severity and priority via AI, shows past behavior [S20]
- Alert channels: Phone, chat, or app alerts including WhatsApp, SMS, Slack and Teams bots [S1]
- Alert channels supported: phone · sms · mobile_app · email · slack · microsoft_teams · whatsapp · telegram · discord [S8]
- Alert noise: Auto-resolve unactioned alerts and group related alerts into one incident [S21]
- Alert routing: Rule-based automatic alert routing [S1]
- Alerting capabilities: Immediate alerting, escalation policies, on-call rotations [S21]
- API auth: x-api-key · api_key [S9]
- API base URL: https://api.spike.sh [S9]
- API granular permissions: no [S9]
- API interactive docs: yes [S9]
- API multi team limitation: no [S9]
- API purpose: REST API for programmatically managing incidents, teams, users, on-call schedules [S9]
- API requests: unlimited · users x 1000 per month · unlimited [S10]
- API rest json: REST · JSON [S9]
- API team scope: x-team-id · yes [S9]
- API webhooks: yes [S20]
- Audit logs: Enterprise only [S10]
- Auto detection: yes [S1]
- Auto detection: auto-detection of duplicates and recoveries [S5]
- Auto resolve recurring noise: recurring noise · yes [S4]
- Automation: Automated alert routing, ticket creation, status page updates [S21]
- Automation via webhook: Lambda · restart server · GitHub workflow · own automation via webhook [S4]
- Brand customization: yes [S6]

**Subprocessors**
- Annex reference: Annex III of the DPA [S15]
- List: 14 · United States [S15]
- List location: infrastructure hosting · database hosting · email delivery · SMS delivery · yes [S14]
- Notice period: 14 · email · 14 [S15]

**Support**
- API feedback channel: chat widget [S9]
- Business live chat: Business · Enterprise · live chat [S10]
- Demo: 30 [S1]
- Demo: 30 [S2]
- Demo: 30 [S5]
- Demo: 30-minute demo with founder offered [S21]
- Demo: 30 [S20]
- Demo call: founder · 30 [S3]
- Demo call: 30 [S6]
- Demo call: 30-minute call with founder [S4]
- Docs: docs.spike.sh [S10]
- Enterprise dedicated: Enterprise · Slack Connect [S10]
- Live call routing number provisioning: support@spike.sh · yes [S19]
- Nonrenewal channels: email support@spike.sh · in-product cancellation option [S13]
- Security contact: Team contact available for security questions and certifications [S11]
- Standard: Standard · Business · Enterprise · email [S10]

194 more facts on the canonical page: https://whats-best.ai/software/incident-management/spike-sh

## Questions

### 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](https://whats-best.ai/evidence/19831).

### 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](https://whats-best.ai/evidence/19840).

### Does Spike.sh have a free plan?

Yes. Spike.sh has a free plan, per [the vendor’s page captured 6 Nov 2026](https://whats-best.ai/evidence/19789).

### What are the best alternatives to Spike.sh?

As of 18 Nov 2026, the panel rates [ilert (4/5)](https://whats-best.ai/software/incident-management/ilert), [All Quiet (3.5/5)](https://whats-best.ai/software/incident-management/all-quiet) and [OneUptime (3.5/5)](https://whats-best.ai/software/incident-management/oneuptime) 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](https://whats-best.ai/software/incident-management/ilert) (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [Spike.sh alternatives](https://whats-best.ai/software/incident-management/spike-sh/alternatives).

## What this page leaves out

- 39 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 8 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement.

## Sources

- [S1] Vendor homepage: https://spike.sh/ (checked 2026-11-06)
- [S2] Features page (on-call): https://spike.sh/on-call/ (checked 2026-11-06)
- [S3] Features page (escalations): https://spike.sh/escalations/ (checked 2026-11-06)
- [S4] Features page (alert routing): https://spike.sh/alert-routing/ (checked 2026-11-06)
- [S5] Features page (incidents): https://spike.sh/incidents/ (checked 2026-11-06)
- [S6] Features page (status pages): https://spike.sh/statuspage/ (checked 2026-11-06)
- [S7] Integrations page: https://spike.sh/integrations/ (checked 2026-11-06)
- [S8] Documentation: https://docs.spike.sh/ (checked 2026-11-06)
- [S9] API documentation: https://docs.spike.sh/spike-api-docs (checked 2026-11-06)
- [S10] Pricing page: https://spike.sh/pricing/ (checked 2026-11-06)
- [S11] Security / trust page: https://spike.sh/security/ (checked 2026-11-06)
- [S12] Public status page: https://status.spike.sh/ (checked 2026-11-06)
- [S13] Terms of service (names the operating company): https://spike.sh/terms/ (checked 2026-11-06)
- [S14] Privacy policy: https://spike.sh/privacy-policy/ (checked 2026-11-06)
- [S15] GDPR page: https://spike.sh/gdpr/ (checked 2026-11-06)
- [S16] On-call schedules, rotations & escalation — found from sitemap: https://docs.spike.sh/oncall-schedules/create-on-call-schedule (checked 2026-11-06)
- [S17] On-call schedules, rotations & escalation — found from sitemap: https://docs.spike.sh/oncall-schedules/introduction-to-layers-in-on-call-schedules (checked 2026-11-06)
- [S18] Alert delivery, routing & noise reduction — found from sitemap: https://docs.spike.sh/alerts/alert-rules (checked 2026-11-06)
- [S19] Alert delivery, routing & noise reduction — found from sitemap: https://docs.spike.sh/live-call-routing/introduction-to-live-call-routing (checked 2026-11-06)
- [S20] Incident response, status pages & post-incident review — found from sitemap: https://spike.sh/incident-response/ (checked 2026-11-06)
- [S21] Incident response, status pages & post-incident review — found from sitemap: https://spike.sh/incident-response-guide/ (checked 2026-11-06)
- [S22] Integrations, API & administration — found from sitemap: https://docs.spike.sh/spike-api-docs/integrations (checked 2026-11-06)
- [S23] Integrations, API & administration — found from sitemap: https://docs.spike.sh/integrations-guideline/integrating-with-webhooks (checked 2026-11-06)

---

Cite as: whats-best.ai, "Spike.sh — On-Call & Incident Management", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/incident-management/spike-sh

Corrections: https://whats-best.ai/correct/1627?target=page
