Spike.sh plans and prices
| Plan | Per user a month | Phone and SMS alerts | On-call schedules | What else it adds |
|---|---|---|---|---|
| Standard | 7 USD | 100 a month, shared by phone and SMS | 1 (1 person) | Unlimited incidents, escalations, WhatsApp and Telegram alerts, Slack, Discord and Teams, a public status page, 1 call routing number with 5 incoming calls a month |
| Business | 14 USD | Unlimited | Unlimited | Private status pages, war rooms, incident context, multiple teams, Jira, ClickUp and Linear, unlimited alert rules and webhooks, live chat support |
| Enterprise | Quote | Not listed | Not listed | SSO, a dedicated Slack Connect channel, call routing managed by Spike |
Source: the Spike pricing page, October 2026. Prices are shown as billed monthly; the annual toggle is labeled "1 month free", which works out to about 6.42 and 12.83 USD per user a month if you pay for a year. SSO is marked "On request" on Business and listed as an Enterprise feature.
Why directories show different Spike prices
Search for Spike pricing and you will find 7, 8, 16 and 19 USD starting prices, a free plan for 5 users and plans called Pro and Team. Those come from directory listings captured at different times. Spike renamed and repriced its plans more than once, and the current page shows Standard and Business only, with no free tier. If a quote or a review cites a Pro or Team plan, ask Spike which current plan it maps to before you budget.
What does Spike cost for 5, 15 and 40 users?
Monthly cost at list prices with every user on call. Spike rows are monthly billing, the others are annual list prices. The Business row is the realistic floor for a team that rotates.
| Setup | 5 users | 15 users | 40 users |
|---|---|---|---|
| Spike Standard, 1 schedule for 1 person | 35 USD | 105 USD | 280 USD |
| Spike Business | 70 USD | 210 USD | 560 USD |
| Spike Business, first 6 months with the Opsgenie offer | 35 USD | 105 USD | 280 USD |
| Zenduty Growth | 80 USD | 240 USD | 640 USD |
| SIGNL4 Optimize | 75 USD | 225 USD | 600 USD |
| PagerDuty Professional | 105 USD | 315 USD | 840 USD |
| IncidentBot Starter (1 public status page) | 120 USD | 360 USD | 960 USD |
| IncidentBot Team (3 status pages, incident roles, Jira sync) | 245 USD | 735 USD | 1,960 USD |
Read it honestly. On price per seat, Spike Business is one of the cheapest full on-call tools you can buy: 210 USD a month for 15 people against 315 USD for PagerDuty Professional and 360 USD for IncidentBot Starter. If your team needs alerting, rotations, escalation and a status page and nothing more, Spike is a strong pick. Zenduty, SIGNL4 and PagerDuty prices come from our Zenduty pricing, SIGNL4 pricing and PagerDuty pricing guides.
Where the Spike bill grows
- Rotations. The 7 USD plan has one on-call schedule for one person. The moment two people take turns, every seat moves to 14 USD, which doubles the bill.
- Alert volume. Standard's 100 phone and SMS alerts are shared by the whole account, not per user. A noisy week on a 10 person team can use them in days.
- Private pages and war rooms. A private status page for staff or a key customer, war rooms and incident context are Business features.
- SSO. Single sign-on is on request for Business and listed for Enterprise, so a security review that requires SAML can push you to a quoted plan.
- The Opsgenie discount ends. Half price for six months is a good start, but budget the full 14 USD from month seven.
Is Spike worth it, or do you need more incident workflow?
Spike covers more than most low-cost pagers. Business includes war rooms, incident context, a status page and Jira and Linear, so a small engineering team can run its whole on-call process on it. Where teams look further is the part after the page goes out: who leads the incident, who tells customers, and what gets written down afterwards.
| What you need | Spike | IncidentBot |
|---|---|---|
| Push, SMS and voice paging | Standard (100 alerts) or Business (unlimited) | Starter (100 SMS and voice per user) or Team (unlimited, fair use) |
| Rotations and escalation | Business, 14 USD | Starter, 24 USD (3 schedules), unlimited on Team |
| WhatsApp and Telegram alerts | Yes | No |
| Live call routing | Yes, 1 number on Standard | No |
| Slack incident channel with roles | War rooms on Business | /incident channel on Starter, commander, comms and scribe roles on Team |
| Customer status page with email subscribers | Public on Standard, private on Business | Public on Starter, 3 public or private pages with subscribers on Team |
| Postmortem drafted from the timeline | Not listed on the pricing page | Team, with action items synced to Jira and Linear |
| People who only follow incidents | Counted as users | Free read-only viewers on every plan |
Spike also wins on reach: WhatsApp, Telegram and a call routing number are things IncidentBot does not offer. IncidentBot is the better buy when incidents involve more people than the rotation. A 15 person on-call team with 30 support, success and leadership staff following along pays for 15 seats here, while a per-user tool counts everyone who logs in. Alerts for both tools can come from your APM, cloud monitoring or data observability checks on pipeline freshness and schema, so the choice does not change what you monitor.
If you are leaving Opsgenie, both tools want your business. IncidentBot imports Opsgenie schedules, overrides and escalation policies with a read-only API key, which the Opsgenie alternative page walks through. Small teams weighing the whole category can start with incident management software for small teams.
What to ask Spike before you sign
- Which plan does our rotation need, given that Standard lists one on-call schedule for one person?
- Is the 100 alert limit on Standard counted per account or per user, and what happens when we hit it mid-month?
- What is the exact annual price per user with the one month free?
- Does the 50 percent Opsgenie offer apply to Business, and what is the price from month seven?
- Is SSO available on Business, and at what extra cost?
- Do people who only read incidents and status pages need a paid seat?
Put the same questions to every vendor on your shortlist and add the cost of anything they do not cover. Our pricing page lists every IncidentBot plan and what each one includes.
How much does Spike.sh cost?
Spike.sh costs 7 USD per user a month on Standard and 14 USD on Business, billed monthly, according to spike.sh/pricing in October 2026. Annual billing gives one month free, and Enterprise is quoted. There is no free plan, but both paid plans have a 14 day trial.
Does Spike.sh have a free plan?
No. The current pricing page lists Standard, Business and Enterprise, each with a 14 day trial and no free tier. Directories that mention a free plan for up to 5 users describe an older version of Spike's pricing.
Which Spike plan includes on-call scheduling for a team?
Business. Spike's comparison table limits Standard to one on-call schedule for one person, while Business has unlimited schedules. A team that rotates on-call between two or more people should budget 14 USD per user a month.
Is Spike cheaper than PagerDuty?
Yes. Spike Business at 14 USD per user a month costs less than PagerDuty Professional at 21 USD billed annually, and it includes unlimited phone and SMS alerts and a status page. For 15 users that is 210 USD against 315 USD a month.
Does Spike offer a discount for Opsgenie users?
Yes. Spike's pricing page offers teams migrating from Opsgenie 50 percent off for their first six months. Opsgenie stops working on April 5, 2027, so check whether the offer covers Business and what the price is after month six.
What is a good alternative to Spike for engineering teams?
For software teams that run incidents in Slack and want customers told through a status page, IncidentBot covers paging, schedules, escalation, the incident channel, a status page and postmortems from 24 USD per seat billed annually, with read-only viewers free. PagerDuty Professional and Zenduty Growth are the other common comparisons.
Price your rotation with the status page and readers included
Run a sample incident with an escalation policy and a status update, then create your account and point one alert source at IncidentBot.