Moveworks vs Serval (2026)

Hundreds of named enterprise systems are connected under one layer, across seven classes, and the Assistant takes action in them, from resetting access to updating CRM records. Service desk and ITSM tools include ServiceNow, Jira, Freshservice, Ivanti Service Desk, BMC Helix Digital Workplace, ManageEngine and Cherwell. HR and finance cover Workday, Coupa, SAP Ariba, SAP Fieldglass and Oracle, and Salesforce covers CRM.

Identity and access providers include Ping Identity, Duo and BeyondTrust. Content and collaboration tools are Box, Confluence, Quip, Google Drive, LumApps, Igloo, Interact, Axero and Brightspot. Mail, calendar and chat cover Microsoft Outlook, Exchange Online, Gmail, Google Calendar, Google Chat and 8x8, and knowledge and data sources include Databricks, Upland RightAnswers, ComAround and BrainStorm QuickHelp, with DocuSign for signatures.

The Assistant is linked to thousands of action plugins and resolves requests end to end, resetting access and provisioning tools for IT, updating CRM data for sales, and automating expenses, purchase requests and approvals for finance. Those are authenticated writes into systems Moveworks does not own, and the Reasoning Engine chooses each tool call at run time rather than having it wired in advance.

Sourcemoveworks.com/us/en/platform/ai-assistant and /platform/integrations; moveworks.com/us/en/platform/integrationsread 2026-09-12

The integration catalog runs to 164 documentation pages, indexed at docs.serval.com/llms.txt, with a page per connector. Ticketing covers ServiceNow, Jira, Zendesk and Freshservice, bidirectionally, so a customer can keep existing tooling during migration. Identity covers Okta, Microsoft Entra, LDAP and Active Directory, plus SailPoint for governance and RSA SecurID for MFA. Endpoints run through Jamf and Tanium and HR through Workday.

Knowledge comes from Notion, Confluence, Google Drive and Slab, collaboration from Slack, Microsoft Teams and Google Workspace, and finance and operations connectors include Coupa, Salesforce, LaunchDarkly, Vanta and Presidio. Connectors take authenticated action rather than mirroring data.

For RSA SecurID, Serval stores the client key encrypted and attaches it automatically to every call it makes on the customer's behalf, and workflows drive a full MFA flow, starting, verifying, checking and canceling attempts on demand. For Presidio, Serval exchanges credentials for a short lived JWT and reads asset records on the customer's behalf whenever a Serval workflow runs, with the regional endpoint chosen by the workflow.

Both happen at execution rather than by background sync. Provisioning is the heaviest write path, with automated provisioning and deprovisioning via SCIM, direct API or custom workflows, and just in time access grants revoked automatically when the window ends. Access can also be revoked via API. Serval's AI knows the endpoint catalog and can help build workflows against it. Connector maturity is labeled, with RSA marked Beta in the integrations UI.

Sourcedocs.serval.com RSA SecurID and Presidio integration pages, with the integrations indexread 2026-09-12

The Reasoning Engine plans each request at run time, breaking it into steps and choosing the tools that carry them out across enterprise systems. It is an agentic AI system that orchestrates enterprise-ready LLMs and built-in tools for AI agents.

It identifies the employee's overall goal, works out the steps needed and breaks complex issues into smaller parts, then selects the tools for each, automating processes with many steps under strict security protocols and real time governance. Moveworks describes this as automation across the enterprise that plans, executes and adapts as it goes, and the Assistant handles complex requests in depth with extended thinking. Plans are built at run time, not coded in advance.

An employee asks, the Reasoning Engine plans, and agents built or installed through Agent Studio and the Marketplace carry out the work, while admins govern from a central console and plugins act in the systems of record. Developers can extend the sequence by building and deploying agents that plan, reason and execute securely across enterprise systems, and one example covers IT, HR and finance in a single conversational request. ServiceNow, which acquired Moveworks, adds orchestration across departments on its own platform.

Sourcemoveworks.com/us/en/platform/reasoning-engine, /platform and /platform/ai-assistantread 2026-09-12

A workflow can call another as a step through child workflow composition, workflow journeys can be viewed as dependency graphs, and workflows can be organized into folders, shared across teams, tagged, searched semantically and versioned with diffs. Temporal is listed among the required datastores as the workflow orchestration component. It is a durable execution engine, so a run survives process restarts and resumes, which holds long running, multi step work together when people interrupt it.

Workflows can pause for approval, and Serval also has conditional forms in Slack, criteria based assignment rules, a default triage team for ambiguous requests and ITIL aligned change management. The Automation Agent turns natural language descriptions into TypeScript, so automations build themselves from a description. Serval markets deterministic workflows rather than execution the model improvises, since the model writes the workflow and the workflow then runs the same way every time. Workflows and skills are managed as code in Git with version diffs.

The participants include the employee raising a request, three named agents with different jobs, approvers who can be delegated to or overridden by a team manager, assignment groups and external ticket subscribers. Work spans ticketing, just in time access, asset management, onboarding and offboarding, compliance workflows and campaigns, with Security, IT, HR, Finance and Operations each able to run isolated environments on the same platform.

Sourcedocs.serval.com release notes index and self-hosting prerequisitesread 2026-09-12

The Assistant reaches employees without being asked, through nudges and broadcasts, on web, chat and mobile among other surfaces, in over 100 languages. It anticipates what comes next and sends proactive nudges for recurring or time-sensitive tasks. Employee comms, a separate capability, lets internal communications teams broadcast timely, targeted messages to all or some users so they never miss a reminder to act. Each broadcast is a scheduled send to a chosen audience.

Employees can reach the AI Assistant on web, chat or company portals, as well as intranets, browsers and mobile. The Conversations API embeds the Assistant in applications Moveworks does not own, and a dedicated AI Assistant on web ships as its own release. The Reasoning Engine acts on requests from any of these surfaces, and nudges key on recurring and time sensitive conditions.

Sourcemoveworks.com/us/en/platform/ai-assistant, /platform and /platform/internal-communicationread 2026-09-12

Workflows can be triggered by events and by webhooks, which let any external system act as an event source, as well as by Slack reactions, SLAs and ticket assignment, and campaigns can be triggered directly from a workflow. Child workflow composition lets one flow start another, and tickets, access requests and onboarding events all start work. Schedules are a separate mechanism, covering recurring campaigns, assignment schedules, SLAs with business hours and pause conditions, and automatic ticket bumps for unresponsive requesters, a time based trigger acting without a person.

The Help Desk Agent covers intake and resolution across Slack, Teams, email, phone and portal. Further channels include an embedded widget with a live agent and multiple email intake addresses per team, along with Microsoft Teams notifications and reply routing improvements, conditional forms in Slack, dynamically rendered forms, a Serval Inbox consolidating notifications, and white label Slack bot customization. The UI ships in nine languages with on demand ticket translation.

Sourcedocs.serval.com release notes index and serval.com/insights buyer's guideread 2026-09-12

Answers come from the customer's own connected systems, filtered to what each asker may see, and a dedicated authoring product keeps that corpus up to date. Enterprise Search gives instant, context-aware answers across business apps, tailored to role, region, language and access level without relying on exact keywords or rigid filters.

The AI Assistant connects to the systems and content sources the customer uses, and a grounded knowledge system ties answers to the most up-to-date and trustworthy documentation available, with fact verification among the AI safeguards. Knowledge Studio generates grounded knowledge articles to fill content gaps and improve self service for FAQs, so the content grows over time, with gaps found from what employees actually ask. Retrieval respects permissions, so two people asking the same question can get different results. This is a retrieval structure over the customer's own estate that lasts between runs and scales far past any context window.

Sourcemoveworks.com/us/en/platform/enterprise-search, /platform/ai-assistant, /platform/ai-knowledge-management and /platform/securityread 2026-09-12

A native knowledge base, in beta, sits alongside the synced stores and is maintained in Serval, with knowledge base management, knowledge tagging within guidance, lexical and keyword search alongside semantic retrieval, cross team KB sharing, and a tag catalog with owners set for teams, resources and roles. Answers ground in help docs built in Serval or synced from Notion, Google Drive, Confluence and Slab, and reviewers can publish approved knowledge updates into Notion, Slab, Confluence, Freshservice and ServiceNow, so corrections flow back out to the systems of record.

Retrieval respects permissions at read time through knowledge source permission enforcement, so an employee cannot be answered from a document they are not entitled to see. The Help Desk Agent can also search the web, tickets, assets and access history are queryable alongside, and the Insights Agent analyzes ticket patterns. Serval's asset estate tracks hardware, software licenses, SaaS subscriptions and cloud costs in one schema the agent reasons over.

Sourcedocs.serval.com release notes indexread 2026-09-12

The Assistant uses four kinds of memory, and none is a lasting store per user, since conversation context is cleared every 24 hours. Semantic memory is knowledge of the content, entities and terminology the organization uses, shared across the organization rather than kept per user.

Episodic memory is billed as recalling past conversations with the user, but it is defined as awareness of the current conversation, meaning what questions and answers have been exchanged and what decisions have already been made. Context is automatically cleared every 24 hours from the reasoner, so anything older than a day is gone.

Procedure memory is knowledge of the tasks that can be performed and the business processes or rules to follow, meaning the plugin catalog and the customer's configured rules. Working memory is awareness of which operations are in progress and at what stage, with a framework that tracks variables such as business object IDs, which is run state inside a single execution. The context window is assembled fresh on each turn and the engine reads everything every turn, so nothing is carried in from an earlier store.

Sourcehelp.moveworks.com/agent-studio/agentic-ai/memory-constructs, /assistant-behavior-framework and /agentic-reasoning-engine/how-the-reasoning-engine-worksread 2026-09-13

Per team guidance, knowledge sources and configuration persist in Serval, but none of these is a memory that learns per user over time, and no agent memory is described. Guidance, now called Skills, is a set of written procedures and runbooks the customer authors so agents follow internal practice, with a diff view for suggested changes and version history. It persists because a person wrote it down, not because the agent retained anything.

The native knowledge base and the corpora synced from Notion, Confluence, Google Drive and Slab are the knowledge layer, and workflows, skills and settings managed as code in Git are authored artifacts. The runtime stack uses PostgreSQL as the primary application database, Redis for caching and ephemeral state, and Temporal for workflow orchestration.

Temporal keeps a workflow run alive through restarts, but that is state within one execution, and no component in the stack holds what an agent learned. There is no named memory layer, no retained preference the agents reapply for a user or requester, no decision trace carried between tickets, no stated scope or lifetime for anything held, and no customer surface to inspect, edit, export or purge agent state apart from tickets, skills and knowledge. Ticket history is a record of work.

Sourcedocs.serval.com self-hosting prerequisites and release notes indexread 2026-09-12

Guardrails surround what the agents do. A content moderation system filters harmful or inappropriate content, prompt protection guards against prompt injection attacks, and query risk assessment identifies and mitigates risks in user queries. Fact verification and identity validation add further checks, with authentication and authorization handled by deterministic systems and source-of-truth methods rather than LLMs. The Reasoning Engine operates within scoped action boundaries enforced at the infrastructure level.

Each of these limits what the agent may do, but there is no person in the loop. There is no approval queue, checkpoint or escalation on a risk threshold, and no human role is named, so no one signs off before the Assistant resets access, provisions a tool, updates CRM data or completes a purchase request, all actions it takes end to end. Enterprise permissions and scoped access govern who can reach what, and governance from ServiceNow belongs to the acquirer's platform.

Sourcemoveworks.com/us/en/platform/security and /resources/blog/why-autonomous-ai-agents-need-new-enterprise-security-modelread 2026-09-12

Workflows can pause for approval, so execution halts mid flow and waits for a person, and customers author these gates in a redesigned approval flow builder. Around them sit custom approval workflows, natural language workflow approvals, approval delegation, team managers able to override approvals from a ticket, and an approvals API for custom follow up logic. Multi step approvals apply to workflows and access requests alike.

Access requests route through approval before a grant is made, just in time access is time bound and revoked automatically when the window ends, and the access history export records the approver and the justification against every grant. Where approval is not requested, guardrails apply. Serval markets deterministic workflows with security layers, namely RBAC, approval gates, API scope limits and an air gap between help desk and builder.

That air gap means the agent that talks to employees cannot edit workflows or integration scopes, so a compromised conversation cannot widen the agent's own authority. Skills and runbooks hold agent behavior to the team's written procedures, with a diff view for reviewing changes the AI suggests before they take effect.

Sourcedocs.serval.com release notes index and serval.com/insights buyer's guideread 2026-09-12

Moveworks publishes ten certifications with their scopes and auditor marks. The ISO/IEC set covers 42001 for AI management, 27001, 27017, 27018 and 27701, SOC 2 Type 2 spans security, confidentiality, availability and privacy, CSA STAR Level 2 is held at Gold, and FedRAMP, GDPR and CCPA complete the list.

Controls cover access to how user data is processed and stored, encryption at rest and in transit, masking of sensitive PII, and identity validation that uses deterministic systems and source-of-truth methods for authentication and authorization, securing access to systems and data without LLMs. The design follows zero trust, never trust and always verify, with least privilege access and responses scoped to each person's permissions.

Assurance work includes application security reviews, vulnerability scanning and external penetration testing, red team exercises against enterprise and AI systems, and a HackerOne bug bounty open to all researchers at every severity level. The certification reports sit behind a Whistic profile reached through a demo request or an account executive. Security that ServiceNow's trust and controls add belongs to the acquirer.

Sourcemoveworks.com/us/en/platform/security and /platform/ai-assistantread 2026-09-12

Serval holds SOC 2 Type II, states adherence to HIPAA and GDPR, and documents HIPAA-oriented deployment and data controls. It points customers to its Trust Center for the current Type II attestation report, and a written BAA covers HIPAA workloads and a DPA covers GDPR. Access management is centralized, with SAML and SCIM for SSO and user provisioning, role based access control for least privilege permissions, customizable API scopes for app integrations, and multi step approvals for workflows and access requests.

Further controls include custom roles, scoped API keys, knowledge source permission enforcement, ticket visibility groups for access controlled routing, a read only agent role, default access profiles and app owners, skills gated by access profile, and sharable access reviews. Separation of duties takes the form of an air gap between help desk and builder, so the help desk agent that talks to employees cannot edit workflows or integration scopes or change what agents are allowed to do.

Sourceserval.com/updates/soc2, /insights/hipaa-compliant-itsm and the serval.com platform pageread 2026-09-12

Every system access and data event is logged for full visibility and can be reviewed to support compliance and incident response. The Reasoning Engine works within scoped action boundaries enforced at the infrastructure level, with detailed audit trails for compliance, so the agent's actions leave a retained, reviewable record.

Reasoning can be inspected per interaction, not only in aggregate, because the AI Assistant shows its work and a reader can follow how a request became an action. Employee Experience Insights gives program owners tools to identify issues, track metrics and improve the assistant with governance and analytics, and a self service admin console centralizes configuration and monitoring. Analytics that ServiceNow adds belong to the acquirer.

Sourcemoveworks.com/us/en/platform/ai-assistant and /resources/blog/why-autonomous-ai-agents-need-new-enterprise-security-modelread 2026-09-12

Every workflow run is logged step by step with inputs, outputs, status and duration. Serval offers a sample workflow run export with per-step detail and timestamps and an access history export with approver, justification, start/end and revocation reason, and its governance guidance tells customers to confirm that logs include per-step inputs and outputs, precise timestamps and CSV/JSON export for GRC integration.

An access record carrying the approver and the justification is an audit trail of a consequential agent action with the human decision attached. SIEM integration carries it into the customer's security estate, so evidence is generated when work happens rather than reconstructed before an audit.

Alongside sit agent powered run debugging, version diffs for workflows and skills, a guidance diff view for reviewing AI suggestions, automation suggestion history and workflow journeys viewable as dependency graphs, so a reader can see what ran, what changed and what the agent proposed.

Dashboards on request volume, time to resolution and SLA compliance measure the help desk operation, AI resolution rates show what the agent itself did, and the Insights Agent reports on ticket patterns and automation opportunities. Analytics dashboards are in public beta, with a refreshed home.

Sourceserval.com/insights SOC 2 governance page, with docs.serval.com release notesread 2026-09-12

Hosting is on AWS across seven named regions, with a commitment that customer data never leaves its region and a dedicated GovCloud environment for federal clients. The regions are US Commercial, US GovCloud and Canada in North America, EU Commercial and the UK in Europe, and Australia and Japan in Asia Pacific. All customer data remains in its region and is never transferred elsewhere. Moveworks GovCloud is a dedicated, secure environment built for government agencies and federal clients, backed by FedRAMP authorization. There is no on premises deployment.

Sourcemoveworks.com/us/en/platform/security and /solutions/ai-for-federal-governmentread 2026-09-12

Serval comes in four delivery models. Fully managed Serval Cloud has no infrastructure to manage, automatic updates and a 99.9% uptime SLA. In Hybrid Self-Hosted, the customer runs only the Serval worker inside its own infrastructure while Serval operates the backend, control plane, web app and database, so the worker is the only Serval component that ever touches the internal network or handles integration credentials.

Fully self hosted comes in two operating modes, Managed in Your AWS and Self-Managed on Your Kubernetes. It is single tenant in an AWS account the customer owns, the application runtime and all customer data remain in that account, and the customer's AWS credentials never leave its environment. Either the customer's team or Serval operates it, and the deployment is identical either way.

The deployment bundle holds Terraform, Kubernetes and Helm configuration and setup scripts, and the AWS stack is EKS, Aurora PostgreSQL, ElastiCache, OpenSearch, S3 and Secrets Manager. Customers can point at their own PostgreSQL, Redis, Temporal, OpenSearch or S3 compatible storage, with the upgrade cost of doing so spelled out, and DNS requirements go down to the app and API hostnames.

Private network patterns include Site-to-Site VPN, Direct Connect, Transit Gateway and private DNS resolution. The cloud product also offers a region choice, with EU data residency available to organizations, and Microsoft GCC High is supported for US government workloads. Installation and day two operations sit in a password protected area shared with customers and evaluators, while everything needed to evaluate the models is public.

Sourcedocs.serval.com self-hosting section and release notesread 2026-09-12

An AI Agent Marketplace at marketplace.moveworks.com offers a curated library of ready-to-use, pre-built, production-proof AI agents that are customizable and free to install, with quick connector setup and MCP. Each agent does work once selected, installs on its own through a stated path with no added license, and can be removed without affecting the rest.

Next to the catalog, Agent Studio lets developers build and deploy AI agents that plan, reason and securely execute actions across enterprise systems, and Knowledge Studio, Quick GPT and Brief Me ship as separately named units. Specialized AI Assistants, which create expert agents, are marked coming soon.

Sourcemoveworks.com/us/en/platform/ai-assistant, /platform/ai-agent-builder and marketplace.moveworks.comread 2026-09-12

Three named agents ship, each doing a different job. The Help Desk Agent handles intake and resolution across Slack, Teams, email, phone and portal, the Automation Agent turns natural language descriptions into TypeScript, and the Insights Agent detects patterns and suggests automations. Without the Insights Agent the help desk still resolves tickets, and without the Automation Agent the other two still work.

A browsable catalog of installable workflow bundles sits alongside them, with packs for specific estates such as LDAP/AD, Okta and Google Workspace, plus workflow backed catalog items and service catalog ingestion. An installable Okta workflow does work when selected, and removing it leaves the others whole. Workflows can be organized into folders, shared across teams, searched semantically and tagged. A native knowledge base and Skills add reusable content, though the customer writes those. The catalog comes from Serval, with no third party or community contribution path and no marketplace of externally built agents.

Sourceserval.com/insights buyer's guide, first party about Serval, with docs.serval.com release notesread 2026-09-12

Several language models are routed by the Reasoning Engine on the customer's behalf, but no provider is named and no choice is offered. The engine orchestrates enterprise-ready LLMs and built-in tools, so routing is plural, done by Moveworks and disclosed. Safeguards protect the LLMs against hallucination, data poisoning and prompt injection, and no customer data is used to train global generative models. Moveworks historically ran on its own reasoning stack.

There is no model picker, admin setting or bring your own key path, no model assigned per agent and no individual provider named. Orchestration is Moveworks' decision, made per task, and Moveworks presents that as value on day one with no model tuning, prompt chaining or advanced engineering required. Support for any model on the ServiceNow AI Platform belongs to the acquirer.

Sourcemoveworks.com/us/en/platform, /platform/ai-assistant and /platform/securityread 2026-09-12

Serval uses two model providers and splits the work between them, and the customer does not choose. In self hosted deployments, the customer provides its own keys for the providers Serval uses at runtime, an Anthropic API key as the primary provider for AI agents and help desk functionality and an OpenAI API key for embeddings, image description and specific model tasks. In Managed in Your AWS, the customer owns the AI provider keys and any customer-owned credentials supplied during onboarding, and an in product surface manages Anthropic usage.

The customer therefore owns the provider relationship, sees the spend and controls the data path to the model, but that is control over credentials, cost and data path, not model selection. Serval decides which provider handles which task, and there is no model picker, per agent model assignment, version pin or way to substitute another provider for either role. The key arrangement applies to the self hosted and hybrid models, and nothing says a Serval Cloud customer supplies keys.

Sourcedocs.serval.com self-hosting overview and prerequisitesread 2026-09-12

Outside applications can call the Assistant through the Conversations API, which extends it into another application, portal or intranet. Developer resources sit on four hosts, with a Developer Hub at moveworks.com/us/en/developers, help documentation at help.moveworks.com that includes a Moveworks Setup admin reference, a community at community.moveworks.com and training at academy.moveworks.com.

Agent Studio is a build surface where developers build and deploy agents and plugins that act across enterprise systems, and the Assistant is linked to thousands of action plugins. MCP ships as part of quick connector setup on the AI Agent Marketplace, so an outside assistant can reach Moveworks. The Conversations API is described on a product page, and Moveworks names no public reference for it.

Sourcemoveworks.com/us/en/platform/ai-assistant, /platform/ai-agent-builder and the developer estate linked in the site navigation; moveworks.com/us/en/developersread 2026-09-12

A large API lets outside callers reach Serval. The documentation index at docs.serval.com/llms.txt lists three sections, Documentation at 142 pages, Integrations at 164 pages and an API reference at 252 pages, and two OpenAPI documents, auth-openapi-spec.yaml and openapi-spec-v2.yaml, are served from the API reference section. Scoped API keys and customizable API scopes for app integrations grant access per integration rather than all or nothing.

An approvals API handles custom follow up logic, and access can be revoked via API and workflows, so an outside caller can drive a consequential action inside Serval. Beyond the REST API there is a CLI, which can raise access requests, and user MCP, which puts Serval inside the customer's own assistant. Webhook triggered workflows cover the event side, and workflows, guidance and configuration are managed as code in Git repositories.

Sourcedocs.serval.com llms.txt index, OpenAPI spec listings and release notesread 2026-09-12

Output is checked for accuracy at run time and admins get tools to tune the Assistant, but there is no way to test a change before employees see it. Fact verification improves the accuracy of generated information as a standing safeguard, alongside query risk assessment and a content moderation filter, all of which check what the agent produced.

Around it sits a tuning loop for the Assistant, as Employee Experience Insights lets program owners identify issues, track metrics and improve the assistant, and cutting-edge optimization tools let admins track metrics, resolve issues and make enhancements. There is no test environment, sandbox, holdout or simulation, and no versioning or scored result to compare.

Fact verification gives the customer no verdict to compare across versions, and nothing runs a new or edited agent against a known set before it reaches employees, though these agents reset access and provision tools.

Sourcemoveworks.com/us/en/platform/security, /platform and /platform/ai-assistantread 2026-09-12

Help Desk Agent evaluations are in beta, a harness aimed at the agent's own behavior. What an evaluation produces is not stated, with no score, pass rate, judge verdict or comparison format. Workflows and skills are managed as code in Git with version diffs, so a change can be reviewed before it lands.

Agent powered run debugging lets a failed run be inspected, and a guidance diff view for reviewing AI suggestions gates the agent's own proposed changes to its instructions. Serval markets deterministic workflows, so behavior repeats between runs.

Its commercial claim is a guaranteed automation rate, citing customer automation percentages, which measures how much of the customer's ticket volume the agent cleared.

Sourcedocs.serval.com release notes indexread 2026-09-12

The browser is a place the Assistant lives, not an interface it drives. Browsers are among the access surfaces alongside chat, intranets and service portals, and an AI Assistant on web ships as a destination employees open. On every path the employee opens the surface and types, and the Assistant answers and acts. Actions run through code, as the Assistant is linked to thousands of action plugins and the Reasoning Engine selects the right tools across hundreds of connected systems.

Resetting access, provisioning tools, updating CRM records and submitting purchase requests all run through those connectors and the Conversations API. Nothing clicks, fills in or advances a page, so a change in a target application's markup has nothing to break. There is no hosted or local browser session, desktop control, remote or local computer use, or RPA fallback.

Sourcemoveworks.com/us/en/platform/ai-assistant, /platform and /platform/ai-agent-builderread 2026-09-12

Integrations and APIs are how Serval acts, not driving a browser or a computer interface, and every connector works through an API. For RSA SecurID, Serval stores a client key and attaches it automatically to every call it makes on the customer's behalf, and for Presidio it exchanges credentials for a short lived JWT and sends it as a bearer token on every request. Provisioning runs via SCIM, direct API or custom workflows. Across 164 connectors the pattern is authenticated service to service calls, and the self hosted worker exists to reach internal APIs, LDAP and Active Directory over the network, not to operate a desktop.

Serval markets deterministic workflows compiled to TypeScript. It integrates Jamf and Tanium and runs device actions across managed endpoints, with every grant, device action and workflow run exportable, and those actions go through the MDM and endpoint platforms' own APIs. The CLI, which can raise access requests, is a way for people to reach Serval, not Serval operating anything. There is no hosted or local browser, desktop session, remote control, RPA or recorder.

Sourcedocs.serval.com RSA SecurID and Presidio integration pages, with the release notes indexread 2026-09-12