Serval vs. Flow by ServiceNow: full-stack ITSM vs. automation layer

PublishedOct 2, 2026

Serval vs. Flow by ServiceNow: a full-stack ITSM vs. an automation layer

Serval is an AI-native, full-stack ITSM: one system for your service desk, IT operations, asset inventory, and access management, with AI that resolves tickets and builds the automations.

Flow by ServiceNow is an AI chat and automation layer. It has no change management, problem management, or CMDB, so enterprises that need those still run ServiceNow alongside it.

The short answer

Serval is a full-stack ITSM. Unlike Flow by ServiceNow, Serval runs change, problem, and major incident management, SLAs, a CMDB, and just-in-time access natively.
Flow is a conversation and automation layer. Flow handles requests and incidents only. It has no change or problem records and no CMDB of its own.
For ServiceNow customers, ServiceNow stays. Because Flow lacks those processes, they stay in the ServiceNow platform you keep paying for.
Serval's AI uses your tickets, assets, and access data. Catalyst builds automations from your existing ticket history, and proactive agents find and fix problems before they become tickets.

At a glance

Capability	Serval	Flow by ServiceNow
Resolves requests in Slack and email	Yes	Yes
Microsoft Teams support	Yes	Experimental
Resolves requests over phone/voice	Yes	Not publicly documented
Natural-language automation builder	Yes	Yes
Build automations from files	Yes	Not publicly documented
Test automations before publishing	Yes	Yes
Request and incident tickets	Yes	Yes
Assignment and lifecycle rules	Yes	Not publicly documented
Problem management	Yes	No
Change management with CAB approvals	Yes	No
Major incident management	Yes	Not publicly documented
SLAs	Yes	Not publicly documented
CMDB	Yes	No, asset inventory only
Access requests and approvals	Yes	Yes
Just-in-time access with automatic expiry	Yes	Not publicly documented
Proactive agents	Yes	Not publicly documented
Employee journeys	Yes	Not publicly documented
SOC 2 Type II	Yes	Not publicly documented
EU data residency	Yes	No, US only
Self-hosting	Yes	No, multi-tenant cloud only
Custom dashboards	Yes	Not publicly documented

Where Serval wins over Flow by ServiceNow

One platform for the whole ITSM: Serval manages tickets, SLAs, assets, access grants, and knowledge in one platform with one audit log. Flow has no change or problem management and no CMDB of its own, so ServiceNow customers must keep ServiceNow for those capabilities.
Automations built from your ticket history: Catalyst can pull your ServiceNow ticket history for whatever time range you choose, rank the most common requests, and build the workflows for them without migrating first. A weekly proactive agent keeps drafting new automations for review. Flow flags repeat requests in its own queue and turns a resolved conversation into an automation with a click.
Automations beyond the help desk: Catalyst can automate core ITIL processes such as assessing changes, root-causing problems, and ingesting CMDB data. It can also build custom dashboards, employee journeys, and configure the platform, from change models to access policies, through natural language.
Proactive agents: Serval's proactive agents run on a schedule toward a goal, like "find devices at risk." They investigate across your connected systems, fix issues with workflows you have approved, and draft fixes for anything else. A scheduled automation repeats steps you defined in advance. Flow's documentation describes scheduled automations, but no agents that investigate and act on their own.
One platform for IT, HR, Security, and more: Beyond IT, Serval can run onboarding/offboarding journeys for HR, automate JIT access for Security, and extend service management to any function with custom ticket types. Flow supports teams beyond IT, but documents no employee journeys, campaigns, or custom ticket types.

Full comparison

Serval and Flow by ServiceNow compared across 30+ capabilities, as of October 1, 2026.

Service management

Capability	Serval	Flow by ServiceNow
Ticket types	Five ITIL types plus custom: Request, incident, major incident, problem, change. Support for custom fields and custom ticket types.	Two types: Request and incident
Ticket routing and lifecycle	Automated: Assignment rules by category, priority, and schedule; custom statuses with transition rules and workflows	Manual: Six fixed statuses and manual assignment from queues; no assignment or transition rules documented
Change management	Built in: ITIL change models with CAB approvals, custom change models, and ability to add automations to change models	Not available: ServiceNow changes shown for context only
Problem management	Built in: Created from incidents, linked to changes and services	Not available: ServiceNow problems shown for context only
Major incident management	Built in: AI groups duplicates, broadcasts updates, and closes linked tickets together. Trigger automations upon declaration.	Not publicly documented
SLAs	Built in: Response and resolution targets on business-hours schedules with granular logic	Not publicly documented
Service catalog	Built in: Dynamic request forms, plus employees can order your existing ServiceNow catalog items	Separate catalog: Doesn't import or natively order your ServiceNow catalog items
Employee campaigns	Built in: Announcements over Slack, Teams, or email that collect responses and trigger workflows	Not publicly documented

CMDB and assets

Capability	Serval	Flow by ServiceNow
CMDB	Built in: CMDB, hardware, and software license databases with relationships mapped	Not available: No CMDB of its own; imports ServiceNow configuration items as asset records
Asset data	Any connected app: One-click imports from Jamf, Kandji, Intune, Apple Business Manager, Meraki, Cisco Catalyst Center, and more. Catalyst builds imports for the rest	Synced inventory: From Intune, Google Workspace, ServiceNow CMDB, Cisco Duo, Tanium

Access and identity

Capability	Serval	Flow by ServiceNow
Access requests and approvals	Built in: Multi-step approvals by user, group, manager, or custom workflow	Built in: Access requests with multi-stage approvals
Access profiles	Built in: Match by group, team role, or user attributes like department	Not publicly documented
Access policies	Built in: Approval rules, maximum access duration, and business justification per role or resource	Per catalog item: Each catalog item sets its fields and whether approval is needed
Provisioning	Four built-in methods: IdP groups, direct API, custom workflows, or manual tasks	Automations you build: An admin-built automation makes each change, for example in Okta
Just-in-time access	Built in: Access is removed automatically when it expires	Not publicly documented: Requests collect a duration; automatic removal isn't documented
Unused license reclamation	Built in: Flags unused access and removes it with configurable approvals	Not publicly documented

Enterprise service management: beyond IT

Capability	Serval	Flow by ServiceNow
Departments	Any department: IT, HR, Security, Finance, each with its own workflows and access	Any department: IT, HR, Finance, Legal, each with its own channels
Joiner-mover-leaver lifecycle	Journeys: Multi-step, multi-team workflows with task automation; can be triggered by external systems such as your HRIS	Single automations: No multi-team journeys documented
Org chart	Built in: Built from your identity provider and HR system	Not publicly documented

AI and automation

Capability	Serval	Flow by ServiceNow
Natural-language automation builder	Catalyst: Describe it in plain English and Catalyst builds it	Plain-language builder: Describe it and Flow builds it
Build from files	Built in: Start from SOPs, spreadsheets, or flowchart screenshots (PDF, DOCX, XLSX, Visio, images)	Not publicly documented
Finding what to automate	Builds from your history: Analyzes past tickets in ServiceNow, Jira Service Management, or Freshservice and builds the top automations	Suggests from its queue: Highlights repeat requests in Flow as candidates to automate
Proactive agents	Built in: Start from a goal, investigate across your systems, and fix or draft fixes	Scheduled automations: Run steps you define in advance; no goal-based agents documented
Testing before publishing	Test runs and reviews: Drafts until published, with optional approvals and checks	Simulated runs: Test in simulation before going live

Analytics and reporting

Capability	Serval	Flow by ServiceNow
Built-in analytics	Built in: Resolution rates, time and money saved, SLA compliance, and CSAT, with CSV export	Basic: One operations report with ticket volume, automation coverage, team breakdown, and automation runs
Custom dashboards	Built in: Build your own dashboards that combine Serval data with data from your connected apps	Not publicly documented

Channels and integrations

Capability	Serval	Flow by ServiceNow
Slack and email	Supported	Supported
Microsoft Teams	Generally available	Experimental: Limited in US government tenants
Voice/phone	Supported	Not publicly documented
Embed in homegrown app/portal	Supported	Not publicly documented
Two-way ticket sync	6 systems: ServiceNow, Jira, Zendesk, Freshservice, Salesforce, Linear	2 systems: ServiceNow, Jira Service Management

Security and deployment

Capability	Serval	Flow by ServiceNow
Compliance	SOC 2 Type II	Not publicly documented
Data residency	US or EU	US only
Self-hosting	Hybrid or self-hosted	Not available: Multi-tenant cloud only

Which one fits your team

Choose Serval if: You want one platform for your whole ITSM.
You need change and problem management for audits or compliance.
You want HR, Security, and Finance on the same platform as IT, with HR system integrations and cross-team onboarding and offboarding.
You want AI that builds automations from your full ticket history and runs proactive agents.
You need SOC 2 Type II, EU data residency, or self-hosting.
You plan to replace ServiceNow for IT, or run alongside it while you decide.
Flow by ServiceNow may fit if: You're a small team without an ITSM and only need chat-based requests and incidents.
You plan to keep ServiceNow as your ITSM indefinitely and only want a chat front door in Slack or email.
You already hold ServiceNow Assist credits, ServiceNow's AI usage credits, that you want to use.

Takeaway

Serval is an AI-native, full-stack ITSM: ticketing, change and problem management, a CMDB, and access management in one platform, with AI that builds and runs the automations. It’s built for enterprise IT teams replacing legacy ITSM.

FAQ

Which is better for enterprise ITSM: Serval or Flow by ServiceNow?

For enterprise ITSM, Serval. Serval runs change, problem, and major incident management, SLAs, and a CMDB, with SOC 2 Type II and US or EU data residency. Flow by ServiceNow is a conversational service desk for requests and incidents.

Is Flow by ServiceNow a full ITSM?

No. Flow by ServiceNow handles requests and incidents, but it has no change management, problem management, or CMDB of its own. Serval includes all five ITIL ticket types, SLAs, and a built-in CMDB.

Can Serval replace ServiceNow?

Yes, for IT service management. Serval includes the ITSM processes ServiceNow customers rely on: request, incident, major incident, problem, and change management, SLAs, a service catalog, and a CMDB. Teams can also run Serval alongside ServiceNow with built-in two-way ticket sync while they transition.

What is the best alternative to Flow by ServiceNow?

For teams that need more than a chat layer, Serval is an AI-native alternative to Flow by ServiceNow built for full ITSM. Serval matches Flow's Slack, Teams, and email support and plain-language automation, and adds change, problem, and major incident management, SLAs, a CMDB, HR system integrations, and self-hosting.