Every category where a model named Spike.sh for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.

Category	Function	Share	Rank	Negative rate	Labels	Quadrant
Incident management and on-call	IT operations and endpoint	2%	9 of 53	0%	3	under 10 labels · led by incident.io at 25%

Movement

This is the first edition on this tier, so no move can be computed for Spike.sh yet. From the next edition this section shows, per buyer segment, whether its share moved by more than the measured noise floor.

By model

How each model treated Spike.sh across every prompt where it was named for a mid-market B2B company. Twelve models, six prompts per category.

Model	First choice	Alternative	Labels
Claude Haiku 4.5	0	1	1
GPT-5.4 mini	0	0	0
Gemini 3.5 Flash	0	0	0
Perplexity Sonar	0	0	0
Grok 4.1 Fast	0	0	0
Mistral Small	0	0	0
DeepSeek V4 Flash	0	1	1
Llama 4 Maverick	0	0	0
Qwen 3.7 Flash	0	0	0
Kimi K2	1	0	1
GLM 4.7 FlashX	0	0	0
MiniMax M2.5	0	0	0

By framing

Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.

FramingLabels by classFirst choices

Direct2 labelsNone

Paraphrase5 labels1

Comparative5 labelsNone

Budget-constrained7 labels2

Scale-constrained0 labelsNone

Negative2 labels1not counted in share

First choiceAlternativeMentionNegative21 labels in all, every segment counted; 3 of the 4 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.

What the models said for it

Verbatim evidence the judge attached to positive labels.

“For most budget-constrained companies, Spike at $7/user or Squadcast with its free tier offer the best balance of features and affordability.” Kimi K2 · Incidents · budget prompt · first choice

“combines on-call, escalations, incidents, and status pages in one product at a lower entry price, with a Starter plan at $7/user/month” Claude Haiku 4.5 · Incidents · budget prompt · alternative

“Cheapest Per-User Option ... Perfect for very small teams” DeepSeek V4 Flash · Incidents · budget prompt · alternative

And against it

Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.

No model argued against it.

Named alongside

The products named in the same answers as Spike.sh, over the 21 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and Spike.sh was named but was not.

ProductSame answerTook the first choice insteadHead to head

Better Stack17 of 216Not in the top three

PagerDuty17 of 211Not in the top three

incident.io16 of 215Not in the top three

Squadcast14 of 214Not in the top three

Grafana IRM8 of 210Not in the top three

Rootly8 of 210Not in the top three

Hyperping7 of 210Not in the top three

Opsgenie7 of 210Not in the top three

Jira Service Management5 of 210Not in the top three

Runframe3 of 212Not in the top three

A head-to-head page exists where both products are in a category's top three. The other rows are the same fact without a page behind them, so they link to the product instead.

What carried it into the answer

The sites and pages cited by the answers that named Spike.sh. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, four of the twelve in this edition, so these counts come from 20 of the 21 answers that named Spike.sh and are not a share of its labels.

Domains cited

hyperping.com14

rootly.com14

incident.io13

monday.com13

runframe.io12

guideflow.com10

augmentcode.com9

g2.com8

xurrent.com7

instatus.com6

106 of the 106 domain citations in answers naming Spike.sh came from somebody else's page.

Pages cited

monday.com/blog/service/incident-management-software13

hyperping.com/blog/best-incident-management-tools11

runframe.io/comparisons/best-incident-management-tools-for-startups11

augmentcode.com/tools/best-incident-management-software9

rootly.com/blog/15-best-incident-response-software-platforms-for-modern-engineering-teams-7

rootly.com/sre/cost-effective-startup-incident-management-tools-under-5007

xurrent.com/blog/top-incident-management-software7

g2.com/discussions/what-is-the-most-affordable-incident-management-software-for-smbs6

Pages are listed as the models cited them.

Names read as Spike.sh

What the judge wrote, as written, with how often. The vendor table decides that these count as Spike.sh; a claim can dispute any of them.

Spike 1

Is this your product?

Claim this page

Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Spike.sh's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Spike.sh, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.

It does not get any change to labels, shares or verdicts, any preview, or any say over which quotes appear. A verification link goes to your work email; an address at spike.sh is approved on the spot, any other address is reviewed by hand.

Your name and company appear on the claimed page, or the company alone if you ask below. A title and a LinkedIn address appear there too if you give them, and are left off if you do not. Your email address is never published.