Ryvn

What do they actually do

Ryvn provides a deployment control plane and a lightweight Kubernetes agent that let B2B SaaS vendors install and operate their apps inside customers’ own clouds or on‑prem clusters. Teams define services, environments, release channels, and installations in a web UI/API; the agent makes egress‑only connections back to Ryvn and executes deployments locally in the customer environment (How it works, Quickstart, Ryvn Agent).

Today it supports server apps, jobs, Helm/chart deployments, and Terraform-based infrastructure services, plus automated provisioning into AWS/GCP/Azure (including BYOC/BYOVPC). It ships rollbacks, secrets, installation configuration, and a resource explorer/installation view for day‑2 operations (Quickstart, Terraform service, Changelog).

Ryvn centralizes sanitized logs and metrics across customer installations and integrates with existing CI/CD (e.g., GitHub Actions) so teams can push releases and monitor outcomes from one place. Public docs, GitHub tooling, and a dated changelog indicate an actively shipping, in‑use product (How it works, GitHub Actions integration, GitHub org, Changelog).

Who are their target customer(s)

• SaaS product teams selling into regulated industries (healthcare, finance): Customers demand deployments inside their own cloud accounts, and lengthy security reviews slow sales and upgrades; they need BYOC/BYOVPC workflows that keep data in-customer while preserving vendor control (YC profile, How it works).
• DevOps/platform engineers at B2B SaaS companies managing many customer environments: Coordinating deploys, rollbacks, and useful logs/metrics across dozens of customer clusters is manual and fragmented; they want a central control plane and agent model to standardize releases and observability (Quickstart, Changelog).
• Small engineering teams/startups without dedicated SRE: Building secure provisioning, CI/CD integration, and onboarding per customer is time‑consuming; prebuilt CI actions and provisioning flows reduce setup time and risk (GitHub Actions integration, Quickstart).
• Security/compliance leads vetting a vendor deployment model: They avoid inbound access and third parties holding sensitive data; an egress‑only agent, RBAC, and secrets handling keep data in the customer environment (Ryvn Agent, How it works).
• Vendors delivering infrastructure via code (Terraform) to customer accounts: Running Terraform safely across many customer accounts is error‑prone and hard to coordinate; centralized orchestration and Terraform service types standardize changes and auditing (Terraform service, Quickstart).

How would they acquire their first 10, 50, and 100 customers

• First 10: Run concierge pilots with a handful of regulated‑industry SaaS vendors, handling setup, security reviews, and BYOC/BYOVPC configuration end‑to‑end to unblock procurement (How it works, Changelog, Ryvn Agent).
• First 50: Turn pilot playbooks into repeatable templates/blueprints and CI examples so small teams can self‑serve while sales‑engineering covers security gating; drive inbound via public repos and quickstarts (GitHub Actions integration, GitHub org, Quickstart).
• First 100: Add customer success and sales engineering, ship compliance playbooks and least‑privilege templates, and partner with cloud consultancies/MSPs to navigate mid‑market procurement in regulated accounts (Ryvn Agent, How it works, YC profile—Jobs).

What is the rough total addressable market

Top-down context:

Global SaaS revenue is about $266B in 2024; if ~30% is in regulated verticals and 5–25% of those require customer‑hosted deployments, Ryvn’s revenue TAM is roughly $4B–$20B with a realistic midpoint around $12B (Fortune Business Insights, Mordor Intelligence).

Bottom-up calculation:

Assume a few thousand B2B SaaS vendors globally sell into regulated enterprises and need customer‑hosted options; at 3,000–10,000 target vendors with $100k–$200k annual spend on deployment/ops, the bottom‑up range is roughly $0.3B–$2.0B ARR, rising with higher ACVs and services. Broad enterprise Kubernetes/hybrid adoption supports feasibility of the agent/control‑plane model (Red Hat, CNCF).

Assumptions:

• ~30% of SaaS revenue is in regulated/enterprise verticals; 5–25% of that segment needs customer‑hosted deployments.
• Targetable vendor count is in the low‑thousands globally; average annual spend per vendor is $100k–$200k on deployment/ops for customer‑hosted.
• Enterprise Kubernetes/hybrid adoption remains high, sustaining demand for an agent + control‑plane approach.

Who are some of their notable competitors

• Replicated (KOTS): Packages and ships Kubernetes apps into customer clusters with an in‑cluster admin console and vendor portal—closest direct alternative for vendor‑delivered on‑prem/customer‑cloud installs (docs).
• Argo CD: Open‑source GitOps control plane used to push and reconcile manifests across many clusters; common DIY base for multi‑customer deployments instead of a vendor‑focused delivery product (docs).
• Rancher (SUSE): Multi‑cluster Kubernetes management with agents for target clusters; platform teams can build centralized deployments/policy on top of it rather than using a vendor delivery control plane (docs).
• Terraform Cloud / Enterprise: Runs and governs Terraform across workspaces/accounts with remote runs and agents; used to coordinate infra changes across many customer accounts (docs).
• Crossplane / Upbound: Framework and managed offerings to build control planes for cloud resources across clusters/accounts; a DIY path to similar provisioning/policy capabilities Ryvn packages for vendors (why control planes).