Meridian
Published Sep 7, 2026Enterprise ITSM without the platform tax.
Replaces
- ServiceNow IT Service Management · ServiceNow, Inc. — no published list price
- Jira Service Management · Atlassian Corporation — $51.42 per seat per month (Premium (per agent)), about $246,816/yr at 400 seats
Rented, per year
$246,816
Jira Service Management list price at 400 seats.
Owned, per year
$17,040
AWS infrastructure only. Azure is $17,880.
Build
16 weeks
3 engineers. To parity on the ten core features above, including CMDB seeding, migration of open tickets and the last 24 months of closed history, and re-implementation of existing SLA definitions and approval routing.
Difficulty
5/5
Among the hardest in Techtons. Read the parity table closely.
Reference organisation: 12,000 employees, 250 agents, ~180,000 tickets/year, 200,000 CIs, 120 GB attachments, single region, prod + non-prod. 3-year Compute Savings Plan on Fargate, 3-year reservation on Container Apps and PostgreSQL Flexible Server. Non-prod stopped outside business hours. Excludes vendor support plans, LLM gateway token spend and egress above 1 TB/month. Figures are infrastructure only and exclude the build.
What it is
Meridian is an ITSM system of record: incidents, requests, problems, changes with CAB and approval routing, a service catalog, and a CMDB with relationship-aware impact analysis. It is built for organisations running 5,000 to 50,000 employees where ServiceNow has become a platform commitment rather than a tool — a licence line, a partner line, an internal ServiceNow team, and an upgrade project every six months. Meridian delivers the ITIL processes you actually operate against, in a schema your own engineers can read.
Why this one stops making sense
- ServiceNow does not publish a list price, which is itself the problem: you cannot benchmark a renewal against a number nobody will show you.
- The cost that hurts is rarely the licence. It is the certified partner, the two internal platform administrators and the scoped-application backlog that exists only because the platform is hard.
- Jira Service Management Premium is $51.42 per agent per month. At 250 agents that is $154,260 a year, and agents are the cheap part of your support organisation.
- Your CMDB is a map of your own estate. Keeping it inside a proprietary platform means every downstream system integrates through that vendor's API and pricing.
- Upgrade cycles you did not schedule regress customisations you did not document. Owning the code means the upgrade is a pull request.
What ships
- Incident management with priority matrix, major-incident declaration and post-incident review
- Request fulfilment driven by a versioned service catalog with typed request forms
- Problem management linking recurring incidents to known errors and workarounds
- Change management: standard, normal and emergency paths with CAB scheduling and risk scoring
- CMDB with typed configuration items, relationships and impact/blast-radius queries
- Discovery ingestion from cloud provider inventory, agent feeds and CSV import
- SLA definitions with business calendars, pause conditions and breach escalation
- Knowledge base with article lifecycle, review dates and incident-to-article promotion
- Approval routing driven by org structure, cost centre and CI ownership
- Full audit trail on every record, immutable and exportable
Data model
Stack
- frontend
- Next.js 15 App Router + Tailwind + TanStack Query, with a dedicated agent workspace shell
- backend
- NestJS on Node 22 — REST, plus a workflow engine executing versioned process definitions
- database
- PostgreSQL 16 with Row Level Security, ltree for CI hierarchies and recursive CTEs for impact queries
- cache
- Redis 7 for SLA clock state, catalog rendering and permission caches
- queue
- BullMQ for SLA timers, notification fan-out, discovery ingestion and approval reminders
- auth
- OIDC against the customer IdP; SCIM 2.0 for agent groups and approval hierarchies
- search
- PostgreSQL tsvector across incidents, knowledge articles and CIs
- ai
- Optional incident summarisation, similar-incident retrieval and draft knowledge articles through an LLM gateway
Parity, honestly
What we match, and what we do not.
The rows marked No are the important ones. If one of them is the reason you bought ServiceNow IT Service Management, keep buying it — and we will tell you that on the first call rather than the fifth month.
| Capability | ServiceNow IT Service Management | Ours | Note |
|---|---|---|---|
| Incident, problem, change and request processes | Yes | Yes | Aligned to ITIL 4 practice names so existing process docs still apply. |
| CMDB with relationship modelling and impact analysis | Yes | Yes | Recursive graph queries in Postgres, six hops by default. |
| Service catalog with typed, conditional request forms | Yes | Yes | — |
| SLA engine with business calendars and pause states | Yes | Yes | — |
| Change advisory board scheduling and conflict detection | Yes | Yes | Includes freeze windows and CI-level collision checks. |
| Virtual agent / conversational intake | Yes | Partial | Meridian ships a Slack and Teams intake bot with retrieval over the knowledge base. It is not a full conversational designer. |
| Per-agent licensing that penalises occasional approvers | Yes | No | Requesters and approvers are free in Meridian. That is most of your organisation. |
| ServiceNow Store and certified partner ecosystem | Yes | No | There is no Meridian store, no certified integrator network and no pool of trained administrators to hire from. If your operating model depends on that labour market, that is a real reason to stay. |
| FedRAMP High / IL4 and IL5 authorised environments | Yes | No | ServiceNow holds authorisations Meridian cannot inherit. If you sell to US federal agencies at those impact levels, keep the ServiceNow contract. |
| Twenty years of pre-built ITIL content, templates and workflows | Yes | Partial | We ship the processes you run today, mapped in workshops. We do not ship a library covering every practice in every industry. |
| Agentic discovery of on-premises estate (Windows, network, mainframe) | Yes | Partial | Meridian ingests from cloud APIs, Intune, Jamf and existing discovery tools. It does not ship its own credentialled on-prem discovery probe. |
| Extending the platform without a certified developer | No | Yes | New fields and workflows are TypeScript and SQL migrations reviewed like any other code. |
| Data export without vendor mediation | Partial | Yes | It is your Postgres instance. There is nothing to export. |
Reference architecture
Built twice, on purpose.
Every application in Techtons ships with a production architecture for AWS and one for Azure, using the same diagram grammar so you can read them side by side. Your cloud, your account, your bill.
Amazon Web Services
- Compute
- ECS Fargate services (api, workflow, worker, ingest) behind an ALB
- Data
- Aurora PostgreSQL with a reader for reporting, ElastiCache Redis
- Storage and edge
- S3 for attachments and discovery snapshots, CloudFront for static delivery
- Identity
- Cognito federated to the customer IdP via OIDC/SAML
- Observability
- OpenTelemetry to CloudWatch and X-Ray, with SLA breach metrics as custom CloudWatch alarms
- Infrastructure as code
- Terraform, one module per environment, remote state in S3 with a DynamoDB lock
Services
The decision worth arguing about
The non-obvious decision is keeping the CMDB in Aurora PostgreSQL rather than reaching for Neptune. A CMDB looks like a graph problem, and every architecture review proposes a graph database within twenty minutes. In practice the queries that matter are bounded: what does this database server support, what breaks if we reboot this load balancer, which business services does this change touch. Those are three to six hops, which a recursive CTE over an ltree-indexed relationship table answers in single-digit milliseconds on 200,000 CIs. The trade shows up at the edges — unbounded traversals, shortest-path between arbitrary CIs, and 'show me everything transitively downstream' across a 500,000-CI estate degrade badly, so Meridian caps traversal depth at six and returns a truncation flag rather than running for thirty seconds. We would rather refuse a query than operate a second database whose backup and failover story nobody on the team has rehearsed.
Microsoft Azure
- Compute
- Azure Container Apps (api, workflow, worker, ingest) with KEDA scaling on Service Bus queue depth
- Data
- Azure Database for PostgreSQL Flexible Server with a read replica, Azure Cache for Redis
- Storage and edge
- Blob Storage for attachments and discovery snapshots, Front Door Standard for edge and WAF
- Identity
- Microsoft Entra ID, with Entra groups mapped directly to approval hierarchies
- Observability
- Azure Monitor with Application Insights, SLA breach as Log Analytics alert rules
- Infrastructure as code
- Bicep in an azd-compatible layout
Services
The decision worth arguing about
Azure gives Meridian a discovery source AWS cannot match: Azure Resource Graph returns the customer's entire subscription estate, with tags and dependencies, from one KQL query, so the CMDB seeds itself in an afternoon instead of a six-week discovery project. The non-obvious part is what that forces downstream. Resource Graph delivers change events out of order and in bursts, and a CMDB that applies relationship updates out of order produces phantom dependencies that then appear in change impact analysis — the one place in the system where wrong data causes an outage. Ingestion therefore runs through Service Bus with sessions keyed on the CI identifier, which guarantees per-CI ordering. The trade is throughput: a session is processed by exactly one consumer at a time, so a subscription-wide re-scan of 200,000 resources takes about 40 minutes rather than the four minutes an unordered fan-out would take.
Sources
Every price on this page, with the page we read it from and the date we read it.
| Product | Plan | List price | Checked | Source |
|---|---|---|---|---|
| ServiceNow IT Service Management | ITSM Pro | Not published | 2026-09-05 | www.gsa.gov/about-gsa/newsroom/news-releases ServiceNow does not publish list pricing. The closest public reference point is the GSA OneGov agreement of September 2025, which discloses discounts of up to 70% off list for the ITSM Pro and Pro Plus bundle and 40% off list for standalone ITSM Pro, without ever naming the list rate those discounts apply to. |
| Jira Service Management | Premium (per agent) | $51.42 / seat/month | 2026-09-05 | www.atlassian.com/collections/service/pricin |
Should you still be paying for ServiceNow IT Service Management?
Two weeks, fixed price. We audit what you actually use, map it against Meridian, cost the replacement on your own AWS or Azure account, and give you a delivery plan. If the honest answer is to keep the licence, that is what the report will say.