StepSecurity
Detect, prevent, and respond to software supply chain attacks across developer machines, packages, and CI/CD pipelines.
Website: https://www.stepsecurity.io/
Cover Block
Public sources
| Field | Value |
|---|---|
| Name | StepSecurity |
| Tagline | Detect, prevent, and respond to software supply chain attacks across developer machines, packages, and CI/CD pipelines. [StepSecurity, retrieved 2024] |
| Headquarters | Seattle, United States [Crunchbase, retrieved 2024] |
| Founded | 2022 [Crunchbase, retrieved 2024] |
| Stage | Series A [StepSecurity, November 2026] |
| Business model | SaaS |
| Industry | Security |
| Technology | Software (Non-AI) |
| Geography | North America |
| Growth profile | Venture Scale |
| Founding team | Co-Founders (2), Varun Sharma and Ashish Kurmi [StepSecurity, retrieved 2024] |
| Funding label | $10M+ |
| Total disclosed funding | ~$23,000,000 [StepSecurity, November 2026] |
Links
Public sources
Executive Summary
PUBLIC StepSecurity builds software supply chain security tooling for the environments where code gets built, and it merits investor attention now because it has moved from a GitHub Actions wedge into a broader platform just as enterprise demand is widening from CI/CD controls to developer endpoints, package flows, and agentic development surfaces [StepSecurity, October 2024] [StepSecurity, November 2026]. The company was founded in 2022 in the Seattle area by Varun Sharma and Ashish Kurmi, who according to the company met at Microsoft in 2009, and early coverage tied the initial product focus to securing GitHub-centric CI/CD workflows [StepSecurity, retrieved 2024] [GeekWire, May 2024].
The product case is straightforward: StepSecurity started with visibility and hardening for GitHub Actions, then expanded into a platform that the company says protects developer machines, package downloads, CI/CD pipelines, and AI-agent sandboxes, with named modules including Dev Machine Guard, Code Repo Security, Secure Registry, CI/CD Security, and Threat Intel [StepSecurity, October 2024] [StepSecurity, retrieved 2024] [StepSecurity, November 2026]. Its differentiation, based on public evidence, appears to rest less on model novelty and more on securing multiple software build surfaces under one control plane, while maintaining a free community tier through Harden-Runner that can seed open-source adoption before an enterprise upsell [GitHub, retrieved 2026] [StepSecurity, retrieved 2026].
The founding team is relevant to the problem set. A StepSecurity recruiting post describes Sharma as a former Microsoft security leader who spent 21 years at the company and led supply-chain security for Azure, while Kurmi is described as having 17 years of experience across Microsoft, Uber, and Plaid [LinkedIn, retrieved 2024]. That background does not prove go-to-market execution, but it does fit the technical depth required for a product selling into security and engineering teams.
On financing, the company announced a $3 million seed led by Runtime Ventures in October 2024 and a $20 million Series A led by Elephant in November 2026, bringing disclosed funding to $23 million according to the company; Axios Pro and InsideCyberSec independently reported the Series A round [StepSecurity, October 2024] [StepSecurity, November 2026] [Axios Pro, November 2026] [InsideCyberSec, November 2026]. The business model is SaaS, and the current public signal set suggests a classic open-source to enterprise motion, supported by company-reported usage of more than 3,000 open-source projects in 2024 and more than 20,000 projects on the Harden-Runner community tier by late 2026, although those adoption figures remain company-supplied [Help Net Security, May 2024] [StepSecurity, November 2026].
Over the next 12 to 18 months, the key public watchpoints are whether StepSecurity can convert community and open-source footprint into repeatable enterprise expansion, whether the broader platform beyond CI/CD hardening gains the same traction as Harden-Runner, and whether customer proof points extend beyond named logos such as Circle, Dexcom, Kong, Mercor, Mercari, Chainguard, and XBOW into durable multi-product adoption [StepSecurity, November 2026]. The setup is credible, but most operating evidence in the public record still comes from the company itself, so execution will matter more than category enthusiasm.
Company-stated, unverified -- This section relies materially on company announcements and company website claims, with partial independent corroboration from GeekWire, Axios Pro, and InsideCyberSec.
Taxonomy Snapshot
| Axis | Value |
|---|---|
| Stage | Series A |
| Business Model | SaaS |
| Industry / Vertical | Security |
| Technology Type | Software (Non-AI) |
| Geography | North America |
| Growth Profile | Venture Scale |
| Founding Team | Co-Founders (2) |
| Funding | $10M+ (total disclosed ~$23,000,000) |
How the Company Got Here
PUBLIC
StepSecurity presents as a software supply chain security company built around a fairly specific observation: the places where software gets assembled, developer machines, package flows, and CI/CD pipelines, are now material control points for enterprise risk [StepSecurity, retrieved 2024]. Public company materials say it was founded in 2022 and is headquartered in Seattle, United States [Crunchbase, retrieved 2024]. The business is positioned as SaaS, and the company site identifies co-founders Varun Sharma and Ashish Kurmi as the founding team [Crunchbase, retrieved 2024] [StepSecurity, retrieved 2024].
The milestone record is still short, but the chronology is reasonably clear. Company and funding materials indicate StepSecurity first gained visibility around hardening GitHub Actions workflows, then announced a $3 million seed round in October 2024 led by Runtime Ventures [StepSecurity, October 2024] [Crunchbase, retrieved 2024]. In November 2026, the company announced a $20 million Series A led by Elephant and said total disclosed funding had reached $23 million, alongside a broader product scope spanning developer machines, package downloads, CI/CD pipelines, and AI-agent sandboxes [StepSecurity, November 2026] [Crunchbase, retrieved 2024].
Independently corroborated -- Confirmed by Crunchbase and company website funding announcements.
Product and Technology
Sources and analysis
StepSecurity is easiest to understand as a software supply chain security product that started at the CI/CD layer and has since broadened outward. The company said its initial wedge was visibility and hardening for GitHub Actions workflows, and its public product materials now describe coverage across developer machines, package downloads, code repositories, CI/CD pipelines, and AI-agent sandboxes [StepSecurity, October 2024] [StepSecurity, retrieved 2024] [StepSecurity, November 2026]. That progression matters because the technical problem is not confined to a single build step. A compromised runner, an over-permissioned secret, or a malicious package can each become the entry point into the same development environment.
The publicly described product surface is relatively concrete, even if most of the detail comes from company materials. StepSecurity lists Dev Machine Guard, Code Repo Security, Secure Registry, CI/CD Security, and Threat Intel as product areas [StepSecurity, retrieved 2024]. Around that core, Harden-Runner appears to remain the best-documented entry product: the company says it provides network and runtime security for GitHub Actions workflows, offers a free community tier for public repositories on GitHub-hosted runners, and excludes private repositories from that community offering [GitHub - step-security/harden-runner, retrieved 2026] [Harden-Runner | StepSecurity, retrieved 2026]. Public examples of feature expansion include policy-driven pull requests to replace third-party GitHub Actions with StepSecurity-maintained equivalents, plus visibility into which GitHub Actions secrets are actually used and where OIDC could replace long-lived credentials [StepSecurity, retrieved 2024] [LinkedIn, retrieved 2026].
There is a credible product logic to that expansion, but readers should separate observed capability from broader platform ambition. Independent reporting supports the CI/CD hardening wedge and open-source adoption around GitHub-centric workflows, including use by more than 3,000 open-source projects according to Help Net Security's May 2024 coverage [Help Net Security, May 2024]. By contrast, the broader claims around developer machine protection and AI-agent security are currently supported primarily by StepSecurity materials and employee LinkedIn posts, which makes the direction visible but not yet deeply third-party validated [StepSecurity, November 2026] [LinkedIn, retrieved 2026].
Company-stated, unverified -- Product scope is described mostly through StepSecurity's website, blog posts, GitHub repository, and employee LinkedIn posts, with partial independent corroboration for the CI/CD security wedge from Help Net Security.
Where the Demand Sits
PUBLIC The market matters now because software supply-chain risk has moved from a narrow DevSecOps concern into a board-level control question, while the attack surface has expanded from CI/CD pipelines to developer endpoints, package ecosystems, and automated coding agents [GeekWire, May 2024] [StepSecurity, November 2026].
Public evidence in the supplied record does not support a direct TAM, SAM, or SOM for StepSecurity's exact category, so the cleaner way to size demand is through adjacent markets that budget owners already recognize. StepSecurity is positioned across application security, software supply-chain security, CI/CD security, and endpoint-style controls for developer machines, based on its own product descriptions and financing announcements [StepSecurity, retrieved 2024] [StepSecurity, October 2024] [StepSecurity, November 2026]. That matters because buyers are unlikely to create a net-new line item from scratch. More often, spend is pulled from existing AppSec, cloud security, identity, or developer tooling budgets, especially when the initial wedge is GitHub Actions hardening and workflow visibility rather than a full platform replacement [GeekWire, May 2024] [StepSecurity, October 2024].
The public market signal here is demand density rather than market precision. By May 2024, Help Net Security reported that more than 3,000 open-source projects, including projects associated with CISA, Google, Microsoft, Datadog, Kubernetes, Node, and Ruby, used StepSecurity to harden CI/CD pipelines [Help Net Security, May 2024]. By November 2026, the company said more than 20,000 open-source projects used its Harden-Runner community tier, and that the broader platform had expanded into developer machines, package downloads, and AI-agent sandboxes [StepSecurity, November 2026]. Those figures are company-reported, so they should be read as top-of-funnel adoption rather than a proxy for revenue, but they do suggest the problem is large enough to support a community-to-enterprise motion if conversion holds [StepSecurity, November 2026].
| Market lens | Public evidence | Relevance to StepSecurity |
|---|---|---|
| CI/CD and code repository security | StepSecurity began with visibility and hardening for GitHub Actions workflows [StepSecurity, October 2024] | Supports the initial wedge into build pipeline protection |
| Open-source package and dependency risk | The company says it now covers package downloads and secure registry controls [StepSecurity, November 2026] [StepSecurity, retrieved 2024] | Extends the product into package integrity and dependency governance |
| Developer endpoint security | The platform includes Dev Machine Guard and is described as protecting developer machines [StepSecurity, retrieved 2024] [StepSecurity, November 2026] | Opens budget adjacency with endpoint, device, and identity controls for engineering teams |
| AI agent security | StepSecurity says it protects AI-agent sandboxes and coding agents [StepSecurity, November 2026] [LinkedIn, retrieved 2026] | Creates a newer demand vector tied to autonomous code generation workflows |
The table points to a category that is broad in workflow coverage but still fragmented in budget ownership. That fragmentation can help an emerging vendor land with a specific pain point, but it can also slow expansion if the product spans several control domains before buyers standardize responsibility.
Demand drivers in the record are concrete. StepSecurity's seed announcement framed compromised CI/CD pipelines as a path to source code, credentials, build artifacts, and software updates, which is consistent with why security teams treat build environments as high-consequence assets [StepSecurity, October 2024]. GeekWire's May 2024 reporting adds that the company already had paying customers in crypto, healthcare, and cybersecurity, three sectors where software integrity and credential exposure carry disproportionate regulatory or operational cost [GeekWire, May 2024]. The enterprise customer names cited in the Series A announcement, including Circle, Dexcom, Kong, Mercor, Mercari, Chainguard, and XBOW, suggest demand across regulated, developer-led, and infrastructure-heavy environments, although those customer references remain company-supplied [StepSecurity, November 2026].
The substitute set is also clear from the way the product is described. A buyer could address parts of the same problem with native GitHub controls, broader CNAPP or AppSec suites, software composition analysis tools, developer endpoint management, secrets management, or identity-based workload protections, depending on where it sees the main exposure [StepSecurity, retrieved 2024] [StepSecurity, November 2026]. That cuts both ways. It expands the addressable budget pool, but it also means StepSecurity has to prove that software supply-chain security is best handled as a purpose-built layer rather than as a feature inside a broader platform.
Regulatory and macro forces support the category even without a precise market-size figure in the provided sources. The inclusion of CISA-linked open-source projects among reported users is not proof of a formal partnership, but it is a useful signal that public-sector and critical-software communities are paying attention to CI/CD hardening [Help Net Security, May 2024]. More broadly, the market backdrop is one where boards, auditors, and security leaders are treating software provenance, credential hygiene, and build-environment integrity as risk-management issues rather than developer convenience features, which helps explain why a company that started in GitHub Actions would now expand toward package downloads and developer machines [GeekWire, May 2024] [StepSecurity, November 2026].
Lightly corroborated -- This section relies on one independent publisher for adoption context and several company-authored sources for market framing, product adjacency, and demand signals [Help Net Security, May 2024] [GeekWire, May 2024] [StepSecurity, October 2024] [StepSecurity, November 2026].
Competitive Landscape
MIXED StepSecurity appears to be positioning itself less as a general DevSecOps tool and more as a control layer for the places where software gets built, a narrower wedge that sits between CI/CD security, developer endpoint security, and software supply chain protection [StepSecurity, October 2024] [StepSecurity, November 2026] [GeekWire, May 2024].
The competitive map is easiest to read in segments, because the company spans more than one budget line. In CI/CD security, StepSecurity’s public materials point to GitHub Actions hardening as the original entry point, with Harden-Runner focused on network and runtime security for workflows [StepSecurity, October 2024] [Who's Using Harden-Runner? | StepSecurity, retrieved 2026].
In developer machine and package protection, the field broadens further. The company says the platform now covers developer machines, package downloads, code repositories, CI/CD pipelines, and AI-agent sandboxes, which means buyers could compare it not only with dedicated supply chain security products but also with endpoint management, repository security, artifact-security, and cloud workload tools that touch the same attack surface from adjacent directions [StepSecurity, November 2026] [StepSecurity, retrieved 2024]. That breadth is strategically interesting, but it also means StepSecurity is unlikely to win simply by claiming full-stack coverage unless customers see clear integration value across those surfaces.
Where StepSecurity seems strongest today is domain credibility at the build layer. The founders’ public backgrounds are unusually aligned with the problem set: the company states that Varun Sharma and Ashish Kurmi met at Microsoft in 2009, and recruiting materials describe Sharma as a former Microsoft security leader who spent 21 years there and led supply-chain security for Azure, while Kurmi is described as having 17 years of experience across Microsoft, Uber, and Plaid [StepSecurity, retrieved 2024] [LinkedIn, retrieved 2024]. That matters because software supply chain buyers tend to reward technical trust and implementation fluency, especially when the product is asked to sit inside build systems and touch credentials. The edge looks real, but also somewhat perishable, because founder-market fit helps open doors early while longer-term defensibility usually shifts to product depth, ecosystem integrations, and renewal behavior, none of which are independently well documented in the public record here.
The other visible edge is adoption inside open source, though the evidence is uneven. StepSecurity said in October 2024 that more than 3,000 open-source projects use it to harden CI/CD pipelines, and Help Net Security reported a similar figure with named projects associated with CISA, Google, Microsoft, Datadog, Kubernetes, Node, and Ruby [StepSecurity, October 2024] [Help Net Security, May 2024]. By November 2026, the company said more than 20,000 open-source projects use the Harden-Runner community tier [StepSecurity, November 2026]. If that funnel converts into enterprise demand, the distribution advantage could become meaningful. If it remains mostly community usage, the signal is still useful for credibility but less durable as a moat.
The clearest exposure is breadth risk. A company that starts with GitHub Actions hardening can earn sharp product-market fit in one workflow, but expansion into developer machine security, package security, and AI-agent sandboxes raises the burden of proof on execution [StepSecurity, October 2024] [StepSecurity, November 2026]. Adjacent vendors with established ownership of endpoint, code repository, or package management budgets may have an easier time bundling overlapping controls, while platform vendors can absorb point features natively over time. StepSecurity’s public customer list, which the company says includes Circle, Dexcom, Kong, Mercor, Mercari, Chainguard, and XBOW, suggests it has crossed from open-source utility into enterprise consideration, but that is still company-supplied evidence rather than broad third-party validation [StepSecurity, November 2026].
Over the next 18 months, the most plausible competitive scenario is a category split rather than a winner-take-all outcome. StepSecurity is well placed if buyers increasingly treat build-system security as a distinct control plane and want one vendor spanning developer machines through CI/CD, especially if open-source adoption continues to feed enterprise conversion [StepSecurity, November 2026] [StepSecurity, October 2024]. GitHub is the likely winner if customers decide native workflow security is good enough inside GitHub-centric environments, because StepSecurity’s original wedge is tightly tied to GitHub Actions usage [GeekWire, May 2024]. StepSecurity is the likely loser if expansion beyond CI/CD dilutes product focus before the broader platform is independently validated in the market.
Company-stated, unverified -- This section relies heavily on company materials for product scope, adoption, and customer evidence, with limited independent corroboration from GeekWire and Help Net Security.
Opportunity
Upside case
PUBLIC The prize here is unusually large if StepSecurity can turn a CI/CD security wedge into a broader control plane for how software is built, because the company is targeting systems that sit close to source code, credentials, release pipelines, developer endpoints, and now AI-agent execution environments [StepSecurity, October 2024] [StepSecurity, November 2026].
The headline opportunity is to become a default software supply chain security layer across modern engineering workflows, first in GitHub Actions, then across developer machines, package consumption, and adjacent build surfaces. That outcome is still early rather than established, but it is not purely aspirational on the public record. StepSecurity says it began with visibility and hardening for GitHub Actions workflows, a narrow entry point that maps to a real pain point in source code protection and release integrity [StepSecurity, October 2024]. By November 2026, the company had expanded its public product scope to developer machines, package downloads, CI/CD pipelines, and AI-agent sandboxes, which suggests a product line moving outward from one workflow into a platform claim [StepSecurity, November 2026].
There is also some evidence that the initial wedge has reached meaningful distribution, even if most of it remains company-reported. Help Net Security reported in May 2024 that more than 3,000 open-source projects, including projects associated with CISA, Google, Microsoft, Datadog, Kubernetes, Node, and Ruby, were using StepSecurity to harden CI/CD pipelines [Help Net Security, May 2024]. StepSecurity later said more than 20,000 open-source projects use the Harden-Runner community tier, and named Circle, Dexcom, Kong, Mercor, Mercari, Chainguard, and XBOW as enterprise customers in its Series A announcement [StepSecurity, November 2026]. The combination matters because open-source adoption can seed trust at the workflow layer, while enterprise logos can fund the move into broader control surfaces.
| Scenario | What happens | Catalyst | Why it's plausible |
|---|---|---|---|
| Open-source wedge to enterprise standard | Harden-Runner becomes the default baseline for securing GitHub Actions in open-source and then converts a subset of teams into paid enterprise deployments across private repositories and adjacent controls | The free community tier for public repositories keeps adoption high, while enterprise-only features such as policy-driven pull requests create a clean upgrade path [GitHub - step-security/harden-runner, retrieved 2026] [StepSecurity, retrieved 2024] | Public evidence already shows a large top-of-funnel around GitHub workflows, with 3,000+ open-source projects reported by Help Net Security and 20,000+ community users claimed by the company later on [Help Net Security, May 2024] [StepSecurity, November 2026] |
| Expand from pipeline security into developer environment security | StepSecurity uses its credibility in CI/CD security to sell a broader platform that covers developer machines, package downloads, and AI-agent sandboxes inside the same buyer organization | The November 2026 product expansion provides the product catalyst, especially if security teams want fewer point tools across build-time attack surfaces [StepSecurity, November 2026] | The company has already repositioned publicly from a GitHub Actions tool to a broader software supply chain platform, and recruiting into solutions engineering and customer success suggests more enterprise implementation work rather than a single-feature tool [StepSecurity, November 2026] [StepSecurity, retrieved 2024] |
| Become the control layer for AI-assisted software development | StepSecurity's newer controls for AI-agent sandboxes and developer machines become relevant as more code generation and build activity is delegated to agents | Broader enterprise adoption of AI coding workflows increases demand for guardrails around package downloads, secrets, and execution environments [StepSecurity, November 2026] | The product language already includes AI-agent sandboxes and Developer MDM in public materials, which at minimum shows the company is aiming at a new spend category as it emerges [StepSecurity, November 2026] [LinkedIn, retrieved 2026] |
The compounding mechanism is straightforward if the company can execute it. A free or low-friction community product can spread inside open-source workflows, which creates familiarity with the StepSecurity brand and with its enforcement model at the exact point where developers configure actions, secrets, and third-party dependencies [GitHub - step-security/harden-runner, retrieved 2026]. From there, enterprise tiers can add controls that are hard to replicate manually, including support for private repositories and policy-driven pull requests that automatically replace third-party actions with StepSecurity-maintained equivalents [Harden-Runner | StepSecurity, retrieved 2026] [StepSecurity, retrieved 2024].
That matters because security products that sit in the build path can benefit from both workflow lock-in and a learning curve around policy coverage. The more repositories, workflows, and action patterns a vendor sees, the better positioned it may be to identify risky defaults, flag unnecessary secrets, and steer customers toward safer identity patterns such as OIDC, which StepSecurity team members have discussed publicly in product updates [LinkedIn, retrieved 2026]. None of that is a proven data moat yet on the public record, but the outlines of a usage-to-policy flywheel are visible.
The size of the win is easiest to frame through strategic value rather than a precise market model, because the provided public sources do not include a verified TAM study or a clean public comparable set for this specific segment. If Scenario 1 or Scenario 2 plays out, StepSecurity could plausibly become an attractive platform asset for a larger cloud security or developer infrastructure company that wants ownership of software supply chain controls close to code creation and release. The company had reached $23 million in total disclosed funding by November 2026 and had enough traction to attract Elephant for a $20 million Series A, with follow-on participation from earlier backers, which signals that outside investors see room for a meaningfully larger business than a single-feature GitHub utility [StepSecurity, November 2026] [Axios Pro, November 2026] [InsideCyberSec, November 2026]. A multi-hundred-million-dollar outcome is therefore plausible in scenario terms, not a forecast, if StepSecurity becomes a standard layer for software build security across both open-source and enterprise development environments.
Lightly corroborated -- Section relies on one independent publisher for adoption evidence, plus company announcements and public product materials for customer, product-scope, and funding details [Help Net Security, May 2024] [StepSecurity, October 2024] [StepSecurity, November 2026].
Sources
Public sources
[StepSecurity, retrieved 2024] StepSecurity - Detect, Prevent, and Respond to Software Supply Chain Attacks | https://www.stepsecurity.io/
[Crunchbase, retrieved 2024] StepSecurity - Crunchbase Company Profile & Funding | https://www.crunchbase.com/organization/step-security
[StepSecurity, November 2026] Protecting where software gets built: StepSecurity’s $20 million Series A | https://www.stepsecurity.io/blog/stepsecurity-20-million-series-a
[StepSecurity, October 2024] StepSecurity's Big Step: Announcing Our $3M Seed Funding! | https://www.stepsecurity.io/blog/stepsecurity-seed-funding
[GeekWire, May 2024] Former Microsoft engineers raise $3M for cybersecurity startup StepSecurity | https://www.geekwire.com/2024/former-microsoft-engineers-raise-3m-for-github-focused-cybersecurity-startup-stepsecurity/
[LinkedIn, retrieved 2024] Software Engineer at StepSecurity | https://www.linkedin.com/jobs/view/software-engineer-at-stepsecurity-4430010696
[Axios Pro, November 2026] Exclusive: StepSecurity raises $20M for supply chain attacks | https://www.axios.com/pro/enterprise-software-deals/2026/11/18/stepsecurity-supply-chain-cybersecurity
[InsideCyberSec, November 2026] StepSecurity raises $20m Series A to prevent supply chain attacks | https://insidecybersec.com/stepsecurity-raises-20m-series-a-to-prevent-supply-chain-attacks/
[StepSecurity, retrieved 2024] About StepSecurity | Software Supply Chain Security | https://www.stepsecurity.io/company
[LinkedIn, retrieved 2026] Rohan Prabhu - StepSecurity | LinkedIn | https://www.linkedin.com/in/rohan-prabhu05/
[Forbes Technology Council, retrieved 2026] Varun Sharma | Co-founder, CEO - Enterpret | Forbes Technology Council | https://councils.forbes.com/profile/Varun-Sharma-Co-founder-CEO-Enterpret/bec2ef5c-4a83-4ef8-95a8-3140edeea30e
[Forbes, March 2018] Women In India Are Putting A Face To Your Clothes, Is It Sustainable Fashion's Answer? | https://www.forbes.com/sites/westernbonime/2018/03/04/women-in-india-are-putting-a-face-to-your-clothes-is-it-sustainable-fashions-answer/
[LinkedIn, retrieved 2026] Puya Rajabian - Solutions Engineering at StepSecurity | https://ca.linkedin.com/in/puya-rajabian
[LinkedIn, retrieved 2026] Alexander V. - Security Engineering | https://www.linkedin.com/in/alexviktorov/
[LinkedIn, retrieved 2026] Ashish Malik - Tide | LinkedIn | https://www.linkedin.com/in/a5h15h/
Articles about StepSecurity
- StepSecurity's $23 Million Bet Is on the Developer Machine — The Seattle startup, founded by former Microsoft engineers, is expanding from CI/CD security to guard developer desktops and AI coding agents.