Serval Acquires Ensignia for Enterprise Automation Security

The approval click outlasts the conversation that produced it. At Serval, an IT administrator can use natural language to build a workflow, then publish the tools an agent will use to act on employee requests. That relationship makes the person responsible for security part of the product's operating story.

Serval announced on October 6, 2026 that it had acquired Ensignia and appointed Sam Stewart Head of Security. The San Francisco enterprise service-management company is bringing a software supply-chain security founder into a role covering its own defenses and the controls governing agents in customer systems. Financial terms were not disclosed.

The acquisition connects two questions enterprise buyers have to answer together: whether the software reaching production can be trusted, and whether that software is allowed to perform the requested work. Serval's choice to bring the expertise in-house gives those questions a shared organizational home. How the acquired technology will be integrated remains undisclosed.

What Serval's acquisition of Ensignia changes

Sam Stewart's new responsibilities include detection and response, corporate security, application security and infrastructure security. Serval also places agent permissions, guardrails and audit trails inside his remit. The scope matters because the company is asking customers to let automated systems handle work across IT, HR, finance, legal and security, where a support request can carry consequences beyond the help desk.

Serval cofounder and CTO Alex McLeod describes security as foundational to the systems IT connects, including access, credentials and endpoints. Bringing an experienced security founder into that operating layer is a leadership decision with a product consequence: the teams building automation now have a security function responsible for how those agents touch customer environments. Stewart's remit puts security decisions alongside the product work that creates those customer actions.

For Ensignia, the public change is more visible. Its current website says the company has closed its doors and directs visitors to Serval. The notice offers no standalone-product continuation plan, while the acquisition announcement gives no detailed customer-migration schedule. Customers evaluating continuity will need information about support, product availability and contractual arrangements that the public acquisition record does not yet supply.

From software delivery to workflow permission

Ensignia's earlier work addressed the software that eventually reaches production. Its official company background describes software supply-chain security for applications built with open-source components and deployed through increasingly complex pipelines, with SLSA as a guiding verification framework. That history explains why Stewart's experience belongs near an automation platform's engineering decisions, without establishing that any particular Ensignia tool is already running inside Serval.

A 2023 CyRise profile identified Stewart, Ivan Vanderbyl and Lainie Vinikoor as Ensignia's founders. The accelerator described a product combining delivery-stage controls, build-pipeline integrity and visibility into dependencies. Those are historical company and product details; the October acquisition announcement names Stewart's new role but does not establish current Serval positions for the other founders.

Serval's present product description addresses a different part of the operating chain. Catalyst helps administrators build code-based workflows from natural-language prompts, while the help desk agent uses tools administrators have published. Serval says actions against customer systems run through deterministic workflows that admins have expressly approved. Administrators retain the publishing decision in the company's described architecture.

The distinction has practical value. A workflow can have a legitimate business purpose while depending on software that needs verification; trusted software can also be given inappropriate access. A review therefore has to connect the origin of the executable work with the authority under which it runs. Stewart's background and expanded remit place those conversations closer together as Serval develops its platform.

Prior capital financed Serval's broader ambition

Serval was founded in 2024 by CEO Jake Stauch and CTO Alex McLeod, who had worked together at Verkada. In Sequoia Capital's founder account, their early discussions centered on IT teams that wanted to automate work but were occupied by the queue already in front of them. The customer problem gave the company a reason to build workflow creation alongside service management.

The capital behind that ambition predates the Ensignia transaction. Serval's December 11, 2025 funding announcement reported a $75M Series B led by Sequoia at a $1B valuation. The original company release and Sequoia's contemporaneous investment publication establish the December timing. The round is financing context, and Serval has not disclosed how much it paid for Ensignia.

Sequoia's investment rationale emphasized IT teams' ability to build automation that extends into other departments. Serval's current site markets the platform both as a replacement for incumbent service-management systems and as an automation layer that can work with an existing ITSM. That gives customers different adoption paths, each carrying its own integration and authorization work.

Security expertise sits inside that expansion because the support function has become a place where software can perform operational changes. The acquisition adds a named executive accountable for that responsibility. Enterprise customers can evaluate the scope of his role alongside the controls they can inspect in the platform, while the commercial and technical integration develops.

The buyer's review follows the workflow

For an IT leader, the useful starting point is the work employees want handled and the systems that work touches. An administrator reviewing a proposed automation needs to understand its permissions, execution path and records of activity. Procurement and security teams then need enough evidence to connect the vendor's description with the organization's own requirements and environment.

The acquisition also puts supply-chain expertise near that review. Build provenance and dependency integrity concern how the software arrives; permissions and audit records concern what it does after deployment. Treating these as connected responsibilities can make the vendor conversation more precise, while each still requires its own supporting evidence. Neither the purchase announcement nor a new executive title settles the implementation questions for a particular customer.

DevCuration's coverage of Rein Security's agent runtime-security financing and Hilt's data-movement governance Seed round explores adjacent operating questions. Those companies address different mechanisms; their funding records supply context rather than proof about Serval or Ensignia. The common buyer concern is being able to explain an automated action in the environment where it occurred.

Serval has made a specific organizational choice by putting Stewart inside that environment's vendor. His earlier company's verification work now informs a security mandate that reaches customer-facing automation. As an IT team prepares its next published workflow, the review can follow the software from its delivery pipeline into the permissions and activity record the customer will depend on afterward.