# Spike > Spike is an incident alerting and on-call management platform for DevOps and SRE teams: AI that triages every incident, unlimited alerts on phone, SMS, Slack, Microsoft Teams, WhatsApp, and Telegram, flexible on-call scheduling, automated escalation policies, and branded status pages. This file indexes spike.sh, the product and marketing site. Spike’s blog, glossary, changelog, and docs are separate properties with their own detailed llms.txt files, linked at the bottom. ## Product > Core product pages describing what Spike does: incident response, alerting, on-call, escalation, status communication, and Spike’s AI. Read by teams evaluating Spike or looking for a specific capability. - [Spike (Home)](https://spike.sh/): Incident management that wakes the right person the moment something breaks — on-call schedules, escalations, and alerts by phone, SMS, WhatsApp, and Slack. - [Incidents](https://spike.sh/incidents/): Spike reads your alerts and writes the incident: a clear title, suggested severity and priority, a full activity log, and an MCP your agents can query. - [Incident response](https://spike.sh/incident-response/): Respond in one place — AI triages severity and priority, you acknowledge and resolve, escalate across every channel, and loop in your team. - [AI](https://spike.sh/ai/): Spike puts AI through every incident: it writes a clear title, suggests severity and priority, and answers your team over MCP and Slack. - [Alerts](https://spike.sh/alerts/): Incident alerts on phone, SMS, the mobile app, Slack, Microsoft Teams, WhatsApp, and Telegram within a second — act on them straight from the alert. - [On-call](https://spike.sh/on-call/): Build fair on-call rotations, override schedules on the fly, and keep every responder in sync across Slack, Microsoft Teams, phone, and the mobile app. - [Escalations](https://spike.sh/escalations/): Multi-level escalation policies that reroute an alert to the next on-call responder by phone, SMS, Slack, or push until someone acknowledges. - [Alert routing](https://spike.sh/alert-routing/): Set conditions once and let Spike route, suppress, reassign, and escalate alerts automatically. Pick an incident and watch the rule decide, live. - [Status pages](https://spike.sh/statuspage/): Hosted status pages your customers trust: live uptime, incident history, planned maintenance, and subscribers, all on your own domain. - [Mobile app](https://spike.sh/mobile-app/): Acknowledge, resolve, and triage incidents and manage on-call from the Spike mobile app, with critical alerts that break through Silent and Do Not Disturb. ## Integrations > Spike connects to the monitoring, cloud, error-tracking, and ChatOps tools your team already uses, so alerts from wherever an issue is first detected land in Spike as incidents. Grouped below by category, each links to Spike’s page for that tool. - [Integrations directory](https://spike.sh/integrations/): Browse all of Spike’s integrations, filterable by category, including AWS, Google Cloud, Sentry, Datadog, Grafana, and more. ### Infrastructure Monitoring - [Datadog](https://spike.sh/integrations/datadog/): Infrastructure Monitoring. - [Prometheus](https://spike.sh/integrations/prometheus/): Infrastructure Monitoring. - [Grafana](https://spike.sh/integrations/grafana/): Infrastructure Monitoring. - [Dynatrace](https://spike.sh/integrations/dynatrace/): Infrastructure Monitoring. - [Zabbix](https://spike.sh/integrations/zabbix/): Infrastructure Monitoring. ### Application Performance Monitoring (APM) - [New Relic](https://spike.sh/integrations/newrelic/): Application Performance Monitoring (APM). - [Splunk](https://spike.sh/integrations/splunk/): Application Performance Monitoring (APM). ### Website Monitoring - [Pingdom](https://spike.sh/integrations/pingdom/): Website Monitoring. - [Uptime Robot](https://spike.sh/integrations/uptime-robot/): Website Monitoring. ### Log Monitoring - [Sumo Logic](https://spike.sh/integrations/sumologic/): Log Monitoring. ### Error Tracking - [Sentry](https://spike.sh/integrations/sentry/): Error Tracking. - [Rollbar](https://spike.sh/integrations/rollbar/): Error Tracking. - [Bugsnag](https://spike.sh/integrations/bugsnag/): Error Tracking. ### Network Monitoring - [Cloudflare](https://spike.sh/integrations/cloudflare/): Network Monitoring. ### Cloud Computing - [AWS](https://spike.sh/integrations/aws/): Cloud Computing. - [Google Cloud](https://spike.sh/integrations/google-cloud/): Cloud Computing. - [Microsoft Azure](https://spike.sh/integrations/azure/): Cloud Computing. - [Vercel](https://spike.sh/integrations/vercel/): Cloud Computing. ### API Monitoring - [Sematext](https://spike.sh/integrations/sematext/): API Monitoring. ### ChatOps - [Slack](https://spike.sh/integrations/slack/): ChatOps. - [Microsoft Teams](https://spike.sh/integrations/msteams/): ChatOps. - [Discord](https://spike.sh/integrations/discord/): ChatOps. - [Google Meet](https://spike.sh/integrations/google-meet/): ChatOps. ### Task Management - [Linear](https://spike.sh/integrations/linear/): Task Management. - [Jira](https://spike.sh/integrations/jira/): Task Management. - [Jira Data Center](https://spike.sh/integrations/jira-server/): Task Management. - [ClickUp](https://spike.sh/integrations/clickup/): Task Management. - [Shortcut](https://spike.sh/integrations/shortcut/): Task Management. ### Help Desk - [Freshdesk](https://spike.sh/integrations/freshdesk/): Help Desk. - [Zendesk](https://spike.sh/integrations/zendesk/): Help Desk. - [SupportPal](https://spike.sh/integrations/supportpal/): Help Desk. ### Other - [Zapier](https://spike.sh/integrations/zapier/): Other. ## Alternatives & Comparisons > Landing pages for teams migrating to Spike from a specific competitor, plus a head-to-head overview. Read by teams comparing where to land after deciding to leave a tool. - [Spike vs. the alternatives](https://spike.sh/comparison/): Compare Spike with PagerDuty, Opsgenie, xMatters, Zenduty, and Squadcast across AI-native incident response, on-call, and status pages. - [PagerDuty alternative](https://spike.sh/pagerduty-alternative/): The modern, affordable PagerDuty alternative — AI incident response, on-call, escalations, and status pages in one platform. - [Opsgenie alternative](https://spike.sh/opsgenie-alternative/): Atlassian is retiring Opsgenie. Spike is the modern alternative — AI incident response, on-call, escalations, and status pages, with guided migration. - [Zenduty alternative](https://spike.sh/zenduty-alternative/): The focused, AI-native Zenduty alternative — on-call, escalations, status pages, and a first-party MCP in one platform. - [Squadcast alternative](https://spike.sh/squadcast-alternative/): The focused, AI-native Squadcast alternative — on-call, escalations, status pages, and a first-party MCP in one platform. - [xMatters alternative](https://spike.sh/xmatters-alternative/): The modern, affordable xMatters alternative — AI incident response, on-call, escalations, and status pages in one platform. ## Guides > Long-form, evergreen guides that go deeper than a single blog post. Read by anyone learning incident management, on-call, or escalation policies from scratch, or deciding whether to build or buy. - [Guides hub](https://spike.sh/guides/): Practical guides on incident management, incident response, on-call, escalation policies, and build vs buy — written for the teams who carry the pager. - [Incident management guide](https://spike.sh/incident-management-guide/): What incident management is, the incident lifecycle, team roles, and best practices, plus a practical glossary of key terms for on-call teams. - [Incident response guide](https://spike.sh/incident-response-guide/): The fundamentals of incident response — key roles, the response lifecycle, best practices, and common challenges teams face when incidents strike. - [On-call guide](https://spike.sh/oncall-guide/): How on-call management works — schedules, rotations, handoffs, overrides, and well-being practices that keep systems covered without burnout. - [Escalation policies guide](https://spike.sh/escalation-policies-guide/): How escalation policies work — responders, alert channels, delays, and timeout rules that get the right person on the job fast, every time. - [Build vs. buy guide](https://spike.sh/build-vs-buy/): Building an in-house incident management tool versus buying one — cost, implementation time, reliability, and long-term scalability. ## Customer Stories > First-person accounts of teams running Spike in production. Read by prospective customers who want evidence Spike works at a given scale or in a given industry. - [Customer stories index](https://spike.sh/customers/): Stories from developers, SREs, and DevOps teams worldwide who rely on Spike for incident management and on-call. - [SocialBee](https://spike.sh/customers/socialbee/): For over three years SocialBee has trusted Spike to alert on-call engineers before incidents reach customers. - [Neat](https://spike.sh/customers/neat/): Neat gets ahead of outages with proactive on-call alerts across six time zones, keeping their 400+ team covered 24/7. - [Thndr](https://spike.sh/customers/thndr/): Thndr’s trading platform relies on Spike to cut MTTR, silence noisy alerts, and reach on-call SREs fast for millions of users. - [Sportskeeda](https://spike.sh/customers/sportskeeda/): Sportskeeda leans on Spike’s real-time alerts during live sports events, wiring Cloudflare, AWS, and cron checks into on-call rotations. - [Virtually Human](https://spike.sh/customers/virtually-human/): Virtually Human migrated from OpsGenie to Spike with zero disruption — on-call for 15 engineers across eight time zones. - [Internset](https://spike.sh/customers/internset/): Internset has used Spike’s status page for over two years for proactive, transparent, branded incident reporting. ## Pricing & Getting Started - [Pricing](https://spike.sh/pricing/): Simple, transparent per-user pricing. Start a 14-day free trial with no credit card, and get a month free on annual plans. - [Book a demo](https://spike.sh/demo/): Book a 30-minute demo to see how teams cut alert noise, route incidents, and run on-call — questions answered live. - [FAQ](https://spike.sh/faq/): Common questions about Spike — what an incident is, how alerting works, integrations, team members, and billing. - [Security](https://spike.sh/security/): Encrypted data, hardened data centers, TLS everywhere, strict production access, and PCI-certified payments. - [Contact](https://spike.sh/contact/): Reach the Spike team — talk to sales, request an integration, or reach support; we usually reply within a day. - [Contact sales](https://spike.sh/contact/sales/): Talk to sales about custom plans, pricing, enterprise contracts, and phone or SMS coverage for your region. - [Request an integration](https://spike.sh/contact/integrations/): Tell us what you’d like to connect and we’ll prioritise it — integration requests are fast-tracked. ## Legal - [Terms and conditions](https://spike.sh/terms/): Terms governing use of Spike, including billing, termination, liability, and governing law. - [Privacy policy](https://spike.sh/privacy-policy/): How Spike collects, uses, and protects personal data as a GDPR-compliant platform, including retention and your rights. - [GDPR](https://spike.sh/gdpr/): How Spike meets GDPR requirements — the Data Processing Addendum, transfer safeguards, subprocessors, and data subject rights. - [Data Processing Addendum](https://spike.sh/gdpr/dpa/): How Spike processes customer data as processor — security measures, subprocessors, and international transfer safeguards. - [Migration discount terms](https://spike.sh/alternatives/terms/): Terms for Spike’s migration discount — eligibility, qualifying providers, coupon usage, and validity. --- ## More from Spike > Spike’s blog, glossary, changelog, and docs are separate properties, each with its own detailed llms.txt index. This root file only summarizes them; follow the links below for full listings. - [Blog](https://spike.sh/blog/llms.txt): Incident response, on-call scheduling, escalation policies, alert routing, postmortems, and head-to-head tool comparisons, written by the team building Spike. - [Docs](https://docs.spike.sh/llms.txt): Product documentation: how to configure incidents, on-call schedules, alerts, escalation policies, integrations, and every other feature in Spike. - [Glossary](https://spike.sh/glossary/llms.txt): 500+ term reference glossary of incident management, on-call, and alerting terminology. - [Changelog](https://spike.sh/changelog/llms.txt): Running record of every feature, integration, and fix shipped to Spike, in the order it shipped.