How ALEXUS stacks up against the field.
The names that come up in evaluations — what each is, what we win on, what to concede. Honest, mid-market-flavoured, EU-sovereign.
The ITSM market split into three camps in 2026.
ALEXUS sits cleanly in the third — and is the only AI-native + EU-sovereign + mid-market + independent player in it.
Bolt-on AI on a ticketing core
Strong ticketing engines with AI assistants and copilots layered on. The ticket is still the unit of work; AI helps a human work it faster.
AI-native conversational ITSM
Built AI-first around employee self-service and chat-based deflection. The category effectively consolidated through 2025 — Moveworks → ServiceNow, Aisera → Automation Anywhere.
AI-native operational platforms
Detection-to-resolution agents that work the incident from telemetry, not the ticket from a human. The only camp with structural room left for a regulated-mid-market EU player.
ALEXUS's structural slot — AI-native + EU-sovereign + mid-market + independent
No other vendor in the third camp ticks all four. ResolveAI is the well-funded US-enterprise version. Cleric AI is the earlier-stage US version. Atomicwork is the chat-deflection sister in Camp 2. The rest live in Camp 1.
Capabilities ALEXUS is built around.
The lower cluster of the "today" section — detection, diagnosis, autonomous resolution, the knowledge graph, the learning loop, AI-native architecture and seat-independent pricing — is where ALEXUS is built and where the rest of the field is partial or absent. The planned block below it is where the moat widens — features the May 2026 landscape doc maps with zero competitive coverage today.
| Capability | ServiceNow | JSM | Fresh. | BMC | Atomic. | Resolve | Cleric | Datadog | Dynatrace | ALEXUS |
|---|---|---|---|---|---|---|---|---|---|---|
Incident ticketing & workflow Open, route, track and close tickets through a defined process. | ||||||||||
CMDB / configuration mgmt Inventory of every IT asset (CI) and the relationships between them. | ||||||||||
Conversational agent (Slack/Teams) Chat-based interface to log tickets and get answers in-channel. | ||||||||||
Auto incident detection from telemetry Spot failures from monitoring signals without a human filing a ticket first. | ||||||||||
AI root-cause diagnosis on a live graph AI reasons over the live dependency graph — not just keyword-matched past tickets. | ||||||||||
Autonomous resolution (closed loop) System detects, diagnoses, decides and acts — not just suggests the fix. | ||||||||||
Knowledge-graph dependency mapping A live graph of services + dependencies, queryable as topology — not a flat asset list. | ||||||||||
Learning loop (improves from outcomes) Every resolution feeds back so the next similar incident is handled faster. | ||||||||||
AI-native architecture (not bolt-on) AI built into the platform foundation, not a chatbot on a legacy ticketing core. | ||||||||||
Pricing not tied to seat count Cost doesn't scale with IT-team or end-user headcount — flat platform pricing. | ||||||||||
EU-sovereign by design All data, processing and IP under EU jurisdiction by default; no US data transfer. | ||||||||||
Planned — ALEXUS roadmapT1 next two quarters · T2 Q3–Q4 2026 · T3 2027+ | ||||||||||
CI lifecycle state machine + drift detection Every CI carries a lifecycle state (live → degraded → deprecated → decommissioned); system flags when modelled state diverges from reality. | T1 | |||||||||
Confidence-scored reconciliation + ownership inference When discovery sources disagree on a CI's identity or owner, the brain decides with a confidence score and an audit-log entry — not a rule engine. | T1 | |||||||||
Compliance attribute model (data-class / residency / PII) Every CI carries canonical compliance fields (data-classification, data-residency, PII-status, regulatory-scope) for one-query audit answers. | T2 | |||||||||
Certificate / secret expiry tracking TLS certs, API keys and secrets are tracked with expiry; renewals surface as ticketable work before they break things. | T2 | |||||||||
Continuous NIS2 readiness scoring (Article 21 measures) Live score against each of the 10 NIS2 Article 21 cybersecurity-measure requirements, with a per-control evidence trail. | T2 | |||||||||
NIS2 Article 23 (CSIRT-portal) incident reporting Pre-formatted 24-hour early-warning and 72-hour full-report templates aligned to each national CSIRT's accepted format. | T2 | |||||||||
Executive Accountability Pack (audit-grade quarterly) A curated quarterly artefact a CISO hands a board, regulator or D&O insurer to demonstrate due diligence under NIS2 personal-liability rules. | T2 | |||||||||
Cross-customer pattern library (compounding moat) Pattern signatures from every customer's resolved incidents feed every other customer's resolutions and lifecycle predictions — value scales with N. | T3 | |||||||||
Datadog and Dynatrace come closest on the detection-and-graph side — but they stop at the eyes. They don't open the ticket, run the change, write the runbook, or hand the CISO an evidence pack. ResolveAI and Cleric come closest on the operational side, at price floors regulated EU mid-market can't reach. · In the planned block, continuous NIS2 readiness scoring, Article 23 reporting and the Executive Accountability Pack have zero competitive coverage today — no productised version exists across this set. The Tier 1 queue is what we'd commit to in a customer conversation; Tier 2 and Tier 3 are direction-of-travel, not delivery dates.
Per-seat is the tax. Flat platform is the alternative.
Per-seat pricing means a 20-person desk and a 200-person desk pay 10× for the same software. AI is frequently a paid add-on. ALEXUS's flat platform fee — all AI included, priced against operator-hour displacement — is the only model in this set that doesn't tax growth.
| Product | Pricing model | Indicative cost | Notes |
|---|---|---|---|
| ServiceNow ITSM | Per fulfiller; quote-only | ~$70–200 / fulfiller / mo | AI bundled in tiers; true TCO 3–5× licence |
| ResolveAI | Custom enterprise; quote-only | Est. $200K–$1M+ ACV | $190M+ raised; $1.5B val; enterprise floor only |
| Cleric AI | Per-investigation / per-cluster usage; quote-only | Est. $50K–$300K ACV | YC-stage; lower floor than ResolveAI |
| incident.io | Per-responder SaaS + Enterprise | ~$25–60 / responder / mo | AI Agents in Pro+; free tier for small teams |
| Rootly | Per-responder SaaS + AI Copilot add-on | ~$25–50 / responder / mo | AI Copilot quoted separately |
| JSM (Atlassian) | Per agent annual | Free (≤3) · ~$20 Standard · ~$48 Premium | CMDB, major-incident, AI gated to Premium+ |
| Freshservice | Per agent annual | $19 Starter / $49 Growth / $99 Pro per agent / mo | Freddy AI Copilot +$29 / agent / mo on top |
| InvGate | Per agent SaaS | ~$25–65 / agent / mo (est.) | AI Hub in higher tiers |
| SysAid | Per admin annual; cloud or on-prem | ~$1,200–3,000 / admin / yr | Sage AI in higher tiers |
| Atomicwork | Per employee SaaS + Enterprise | ~$8–15 / employee / mo (est.) | Sits on top of existing ITSM — additive |
| ManageEngine | Per technician annual | ~$16 / ~$33 / ~$67 per tech / mo | Cheapest credible option |
| BMC Helix | Per named user; quote-only | ~$115 / named user / mo | ~18–21% above ITSM market average |
| Moveworks | Per employee custom; quote-only | ACV commonly $200K–$1M+ | Now a ServiceNow SKU |
| Aisera | Custom; module-priced; quote-only | ~$200K → ~$1.2M list | Negotiated deals land lower |
| ALEXUS | Flat platform sub — not per seat | Tailored quote per tier · contact us | Cost independent of IT-team size; all AI included; no add-on tax; founding-cohort price locks for contract lifetime |
Where ALEXUS wins, what to concede, the line to land.
Every name that comes up in evaluations — direct rivals first, ITSM incumbents second, observability and adjacent layers last. Pulled from the May 2026 Competitive Landscape doc and kept honest on what to concede.
ResolveAI
Ex-Splunk founders. The most direct, well-funded competitor in agentic SRE — Coinbase, DoorDash, Snowflake, MongoDB.
EU-sovereign + Irish base. Mid-market fit (their floor is enterprise). Structured operational graph + Write-Authority Map (vs their agents-with-tribal-knowledge approach). Price point ≈1/10th their likely enterprise ACV. The regulated-buyer compliance layer their customers don't need yet.
$190M+ raised vs our €1M pre-seed. Coinbase / DoorDash references vs 3 design partners. SOC 2 Type II shipped vs our Q1 2027 target. Splunk founder pedigree. Faster everything.
“ResolveAI is the well-funded US-enterprise version of agentic SRE — Coinbase-scale, billions in valuation. We're not trying to win Coinbase. We're the EU-sovereign, mid-market, structured-graph alternative for the 5,000-person Dutch bank that ResolveAI's price floor is too high for and whose data can't cross the Atlantic.”
Cleric AI
Autonomous investigations on alerts — LLM agent runs a toolformer-style query loop across logs, traces, metrics to produce a root-cause hypothesis.
Full operational loop — Cleric stops at the diagnosis; we close the loop (detect → diagnose → decide → resolve). Structured causal graph vs LLM-as-investigator (lower hallucination, auditable). Operational scope beyond engineering (infra, vendor, capacity, certs, access). EU sovereignty. The regulator-facing evidence layer.
Sharper narrower wedge in pure US-engineering SRE. Faster proof-of-value on a single incident (they don't have to build the graph first). YC distribution into US growth-stage companies. Faster on tool-integration breadth short term.
“Cleric runs autonomous investigations on alerts — a sharp, narrow wedge. We're a full operational loop on a structured graph, scoped to regulated EU mid-market, with the audit-grade evidence layer Cleric isn't building.”
ServiceNow
The ITSM gold standard. Bolt-on AI via Now Assist + the Moveworks acquisition. ~€300K price floor; 6–18 month implementations.
Time to value (weeks vs months). AI architecture (native vs bolted). Cost (one-tenth). Mid-market shape (not theirs). EU sovereignty.
ITIL maturity. Ecosystem & app store breadth. Procurement safety ("nobody got fired"). Reference base of thousands. Channel.
“ServiceNow is the right answer if you have €500K and 12 months. We're the right answer if you have a real problem now — and AI-native operational resilience in week 6 beats a project plan in month 12.”
incident.io
Strong incident management with AI Agents on top. Engineering-led mid-market — Linear, Etsy, Loom, Ramp.
Operational scope beyond the incident workflow — we manage the estate, not the response. Closed loop on a live CMDB / graph (they don't model the system, they coordinate the people). Self-healing before paging. The regulator-facing evidence layer they're not building.
Best-in-class incident-management UX. Strong AI Agent product on the response side. Larger reference base in engineering-led mid-market. Faster integration breadth (Slack, GitHub, Linear).
“incident.io is the gold standard for AI-augmented incident response. We don't compete on the on-call workflow — we sit underneath, trying to keep the incident from getting that far. Complementary today.”
Atomicwork
AI-native ITSM with a 'no-ticket' conversational model — resolves IT support requests directly in Slack/Teams.
Multi-ITSM operational graph (vs their sit-on-top-of-ITSM model). Scope beyond employee self-service (infra, vendor, capacity, change). EU sovereignty. Structured causal reasoning, not chat-only.
Slicker conversational UX in chat tools. Stronger employee-self-service deflection. Faster customer acquisition. Different buyer pain (HR-IT helpdesk).
“Atomicwork is great if you want chat-first self-service deflection on top of your existing ITSM. We sit underneath — we build the graph the deflection layer rides on.”
Freshservice
Mid-market ITSM with Freddy AI. Strong in EU mid-market. Per-agent pricing from ~€30/mo; Freddy AI Copilot a separate ~$29/agent/mo add-on.
A closed loop run by one brain (creates the ticket, RCA, applies the fix when confident — not just suggestion). Graph-native CMDB. Cross-system reasoning beyond ticketing. Bundled cost ceiling — all AI included, no add-on tax.
Mature ticketing UX. Cheaper at small agent counts. Employee self-service surface. Larger reference base.
“Freshservice is a great helpdesk with AI features. ALEXUS isn't a helpdesk — it's the brain that closes the ticket before a human sees it. The cost line we displace is operator hours, not licence fees.”
Datadog
Observability leader. Service Map + Watchdog + Bits AI + Workflows. Not an ITSM platform — complementary.
Cross-system reasoning across alert + ticket + change history. Agentic auto-action (not rule-based runbooks). Full ITSM lifecycle. The ticketing-side reasoning.
Telemetry collection (best-in-class). Alerting and anomaly detection. Service map for traced services. Dashboards.
“Datadog is the eyes — keep it. ALEXUS is the hands and the institutional memory. Datadog tells you the pod is crash-looping; we decide what to do, do it, open and close the ticket, write the post-mortem, link the last three times this happened, and update the runbook.”
ManageEngine SDP
Dominant in Indian SMB / mid-market ITSM. Famously cheap. AI features via Zia (bolt-on).
AI-native architecture (vs Zia bolt-on). Multi-tool graph reconciliation. EU-sovereign for regulated EU buyers. Self-resolving loop vs ticket-flow.
Cheapest licence per seat by a wide margin. On-prem option common in regulated Indian sectors. Established channel. Mature SMB feature set.
“ManageEngine wins on per-seat economics — you can't beat them on price. We don't compete on per-seat; we displace operator hours. Different math, different buyer.”
Rootly
Same shape as incident.io — AI for the on-call workflow rather than the operational loop. Customers include Tripadvisor, Canva, Faire, Productboard.
Operational scope beyond the incident workflow — we manage the estate, not the response. Closed loop on a live graph (they coordinate the people, we model the system). Self-healing before paging. The regulator-facing evidence layer. EU sovereignty.
YC network distribution. Stronger US mid-market engineering footprint. Polished AI Copilot product for the response side. Cleaner integration with engineering tools.
“Rootly is incident.io's YC sibling — AI for the on-call workflow. They wake people up cleanly, we try to keep them in bed. Same complementary read: keep both, no overlap on the buyer's pain today.”
Jira Service Management
Devops-flavoured ITSM, tightly coupled to Jira. Virtual Service Agent + Rovo for AI. Popular with engineering-led EU shops; AI gated to Premium+.
Standalone — not Jira-dependent. Autonomous detect-to-resolve loop (vs automation rules). Cross-system orchestration across the estate. Graph-native CMDB depth. All AI included, not gated by tier.
Cheap entry tier. Jira-shop convenience (zero new tool). Atlassian ecosystem and marketplace. Devops workflow comfort. Free tier for ≤3 agents.
“JSM is the right call if your IT and engineering are the same team and you already live in Jira. The moment you have work outside a Jira ticket — a flapping alert, a change request, an audit — we sit across systems, not inside one.”
PagerDuty
Incident-response specialist with PagerDuty Copilot for RCA suggestions. Adjacent to ITSM, not a replacement. Battle-tested at SRE scale.
Full ITSM lifecycle vs alert routing only. Auto-creates and works the ticket — not just alerts a human. Self-resolving before paging. Live CMDB and change management. The cross-incident learning loop they don't build.
Best-in-class paging UX. On-call rotation depth. Incident-response process maturity. Battle-tested at SRE scale. Strong native integrations across observability vendors.
“PagerDuty wakes the right human up. ALEXUS tries to keep them in bed. Different jobs — they coexist well, and we plug into PagerDuty for the cases we choose to escalate.”
TOPdesk
Dutch mid-market ITSM. Traditional ticketing architecture; on-prem option; AI features added gradually with a conservative roadmap.
AI-native architecture vs traditional ticket-flow with chatbot bolt-on. Self-resolving loop run by one brain. Modern graph CMDB. Faster roadmap on the agentic loop.
Established EU mid-market footprint. On-prem availability. Local-language support breadth (NL / DE / FR). Procurement comfort with regulated EU buyers. Long reference list.
“TOPdesk is solid mid-market ticketing — but the architecture is 2010. ALEXUS is what 2026 ITSM looks like: a graph and an agentic loop, not a workflow engine with chatbot bolt-ons.”
InvGate
Argentina-based mid-market ITSM, aggressive EU push 2024–26. AI Hub feature suite — chat-deflection, ticket triage, summarisation — on a traditional ticketing core.
AI-native architecture vs AI Hub on a 2018 ticketing core. Closed detect-to-resolve loop run by one brain. Graph-native CMDB. The compliance-evidence layer for NIS2-bound EU mid-market that InvGate isn't building. EU sovereignty (vs LATAM).
Established mid-market footprint, especially in LATAM and Spanish-speaking EU markets. Per-agent pricing comfort for procurement. Faster on traditional ITSM features. Larger sales motion and channel.
“InvGate is aggressive mid-market ITSM with an AI Hub bolt-on. We're the layer underneath — a closed loop on a live graph, not a smarter ticket form on a 2018 architecture. They sell ticketing modernisation; we sell operational resilience.”
SysAid
Israeli mid-market ITSM with Sage AI — gen-AI chatbot, ticket-summarisation, helpdesk assistant. Strong with regulated buyers wanting an on-prem option.
AI-native architecture (vs gen-AI chatbot on a traditional core). Closed operational loop, not chatbot-on-top-of-helpdesk. Graph-native CMDB. The compliance-evidence layer. EU sovereignty + on-prem (we match the regulated-buyer comfort).
Mature ITSM feature set. Strong on-prem deployment track record for regulated mid-market. Reasonable AI roadmap on chatbot/summarisation. Established channel into regulated verticals.
“SysAid is solid mid-market ITSM, Sage AI for chat. Different category — operational resilience, not service-desk modernisation. If the buyer wants a smarter helpdesk, SysAid is fine. If they want fewer incidents and less firefighting, we are.”
BMC Helix ITSM
ServiceNow-class enterprise ITSM, smaller share. Same enterprise floor, same bolt-on AI on a Remedy legacy core. Strongest in industrial / OT.
AI-native vs HelixGPT on a legacy ticketing core. Mid-market price point (≈1/10th their enterprise floor). EU sovereignty. Faster time-to-value (weeks vs months). Closed loop, not bolt-on copilots.
Industrial / OT depth. Long enterprise references in BFSI, telco, gov. Channel into regulated heavyweight verticals. Mature ITIL surface.
“BMC Helix is ServiceNow's fading sibling. Same enterprise floor, same bolt-on AI, ~18–21% above ITSM market average. We're built for the next decade's regulated mid-market, not the last decade's enterprise.”
Aisera & Moveworks
Two AI-native ITSM peers, both acquired in late 2025. Independent AI-native conversational ITSM is now a vanishing category.
EU-sovereign + independent (Aisera is now US-corporate; Moveworks is now a ServiceNow SKU). Mid-market fit (their floors run $200K–$1M+ ACV). Operational-loop centre of gravity (vs employee self-service deflection).
Longer track record. Deeper US-enterprise references. Larger product surface (Aisera covers HR + IT + CX). Cleaner conversational deflection UX.
“Moveworks is the same enterprise procurement now wearing AI paint. Aisera is the US-enterprise version of the same idea, now part of Automation Anywhere. ALEXUS is what's left for European mid-market that wants independent.”
Komodor
Kubernetes operations platform with AI-assisted RCA on K8s clusters. Narrower scope than us — K8s only — but deeper into that estate.
Full-estate operational graph (not just Kubernetes). Cross-system reasoning beyond K8s — covers infra, identity, vendor, capacity, certs, access. The compliance-evidence layer. Closed loop including ticketing and runbook capture.
K8s-specific depth — node-level instrumentation, GitOps integration, deep Helm / operator knowledge. SRE community brand. Faster on K8s-only resolution paths.
“Komodor is Kubernetes-specific operational AI — narrower scope, deeper into K8s. We span the full estate, K8s included. Complementary where the customer's pain is broader than just K8s.”
Dropzone AI
SOC AI agent — autonomous alert triage and investigation for security teams. Shares our agentic-ops thesis on the SOC side.
ITSM scope (we cover the whole ops loop, not just security alerts). The CMDB graph a SOC alert ends up referencing anyway. The change-to-incident correlation that ties security findings back to operational change. Cross-team outputs.
SOC-specific tooling depth — SIEM integrations, MITRE ATT&CK mapping, native security-analyst workflow. Dedicated security-buyer relationship. Purpose-built for the SOC seat.
“Dropzone is autonomous alert triage for security teams. Adjacent: shares our agentic-ops thesis but operates on the SOC side. Complementary today; partially overlapping when our security signals ship.”
Tines
Dublin-based security orchestration / no-code automation with AI nodes. Used to DIY agentic ops. Friendly EU peer; complementary if a customer already runs it.
A productised AI ops layer, not a DIY toolkit. The structured operational graph their workflows have to assume. Cross-customer pattern learning their per-tenant workflows can't reach. The maintained product vs. the bespoke harness.
Slick orchestration UX. SOC analyst adoption. Faster custom-workflow build for one-off integrations. Strong Dublin brand. Established EU presence.
“Tines is a buy-the-loop enabler, not a productised AI ops layer. Friendly EU peer; complementary if a customer already runs it. Different shape — we coexist.”
Vanta / Drata / Sprinto
SaaS-layer compliance evidence — collect from SaaS connectors (AWS, Okta, GitHub) and SOC 2 / ISO control libraries. They don't see the ITSM-graph layer.
Operational evidence layer (not SaaS-control evidence) — what the system actually did when controls fired. Live CMDB with confidence-scored CIs. NIS2 Article 23 reporting on the operational side. The decision log a regulator reads after an Article 21 incident.
SOC 2 / ISO automation depth. Mature carrier and auditor relationships. Existing buyer relationships with security and finance teams. Cleaner SaaS-control evidence chain.
“Vanta is the SaaS-control evidence layer. We're the operational-evidence layer. When NIS2 personal-liability rules become the question, the regulator asks both: "What were your controls?" (Vanta) and "What did you actually do when the controls fired?" (us).”
Bronto
Dublin-based logging / observability startup from Trevor Parsons + Noel Ruane. 18 staff. Observability layer, not ITSM — peer in the Irish ecosystem rather than a competitor.
Full ITSM operational loop (we close the ticket, run the change, write the runbook). Live CMDB with confidence-scored CIs. Cross-system reasoning that uses logs as one signal among many — alongside change events, dependency edges and ticket history. The compliance-evidence layer they aren't building.
Logging / observability depth — purpose-built ingestion, query speed, retention economics. Founder pedigree from Logentries. Irish-ecosystem peer relationships. Pure observability buyer fit.
“Bronto is observability, not ITSM — same Irish ecosystem, different layer. They collect signals; we run the operational loop on top of them. Friendly peer, not a competitor — and when their telemetry shows up via webhook, we're a natural downstream consumer.”
DIY (Kota-style, homebuilt)
Not a vendor — a pattern. Engineering-led modern startups assemble their own loop: observability webhook → ticket creation → memory layer (mem0 / Letta / Zep) → agent harness (Cursor / Devin / Claude) → PR with human approval. Confirmed at ~95% throughput at Kota.
Cross-customer pattern learning — impossible to DIY by definition. A structured live causal graph, not retrieval over written narratives. Scope beyond code-defects (infra, vendor, certs, capacity, access). Policy / safety / audit machinery for acting on production. Cross-team outputs for CISO / auditor / CFO. A maintained product — no forever-maintenance of bespoke harnesses.
They have already built the closed loop and it works. mem0 covers the memory/context layer at a useful level. Vanta covers their compliance reporting. The technical components are all off-the-shelf in 2026. Modern engineering-led startups will keep building, not buying — that's their nature.
“If you've built it yourselves and it works, you're not our customer — you're an advisor. We build for companies that won't or can't build this in-house: regulated mid-market enterprises with messy heterogeneous stacks and no AI-engineering bench.”
Operational resilience for regulated EU mid-market — that ResolveAI's price floor doesn't reach.
Today: the operational loop on a live graph. In a year: the operational evidence layer NIS2-bound CISOs are buying for. Beyond: the cross-customer pattern library no in-house team can rebuild.
Still have questions?
Read the FAQ bank or see how ALEXUS earns its keep, week one.
FAQs
The questions CTOs, CISOs, IT directors and SREs actually ask in evaluations — answered straight, with the numbers behind each claim.
Read the FAQsUse Cases
Five high-impact ways teams put ALEXUS to work — conversational service desk, auto-resolution, knowledge graph, root-cause AI, and a live CMDB.
Explore use cases