Deployment Options

RunWhen offers flexible deployment options to meet your security, compliance, and operational requirements. All options use the same RunWhen Local agent architecture -- the difference is where the Platform backend runs.

Architecture Summary

In every deployment model:

• RunWhen Local runs inside your Kubernetes cluster(s) as a set of pods

• RunWhen Platform coordinates troubleshooting, hosts the UI, and runs AI analysis

• Communication is outbound-only from RunWhen Local to the Platform over HTTPS (TLS 1.3)

• Credentials never leave your environment -- only task metadata and results cross the trust boundary

Option 1: Multi-Tenant SaaS

The fastest way to get started. RunWhen hosts and manages all Platform infrastructure. Your workspace is logically isolated with a separate database.

Features:

• Fully managed infrastructure, upgrades, and monitoring

• Zero-downtime automatic updates

• Multi-AZ high availability

• SOC 2 Type II certified

• Data residency: US or EU regions

Best for:

• Fast POC and evaluation

• Small to mid-size teams

• Teams without dedicated Kubernetes platform expertise

• Standard compliance requirements (SOC 2, GDPR)

Not suited for:

• Air-gapped environments

• Custom compliance requirements (FedRAMP, etc.)

Get started: Sign up at app.beta.runwhen.com and follow the Quick Start guide.

Option 2: Single-Tenant SaaS

Dedicated infrastructure, managed by RunWhen. Best balance of convenience and isolation. You get a dedicated VPC, dedicated database, and custom network options.

Additional features over Multi-Tenant:

• Physical isolation from other customers

• VPC peering and private endpoints (AWS PrivateLink)

• Dedicated IP addresses

• Scheduled maintenance windows

• Customer-managed encryption keys (BYOK)

Best for:

• Mid-size to large enterprises

• Specific compliance requirements

• Performance-sensitive workloads

• Organizations needing dedicated resources without managing infrastructure

Get started: Contact sales@runwhen.com to discuss requirements.

Option 3: Self-Hosted

Deploy RunWhen Platform entirely in your own infrastructure. Complete control and customization.

Features:

• Air-gapped operation supported

• Deploy in any region or data center

• Source code access available (enterprise license)

• Full compliance control

• Complete network isolation

System Requirements (Minimum / POC):

• Kubernetes 1.25+

• 3 nodes, 4 CPU / 16 GB RAM each

• 100 GB storage

• PostgreSQL 14+, Redis 6+

System Requirements (Production):

• Kubernetes 1.27+

• 6+ nodes, 8 CPU / 32 GB RAM each

• 500 GB SSD-backed storage

• PostgreSQL 15+ (HA), Redis 7+ (HA)

Best for:

• Large enterprises and regulated industries

• Air-gapped or classified environments

• FedRAMP, FISMA, or custom compliance needs

• Teams with existing Kubernetes expertise

Get started: Contact sales@runwhen.com for trial license and prerequisites.

Hybrid Deployments

Many organizations run hybrid configurations:

• Platform in SaaS, RunWhen Local agents in multiple clouds or data centers

• Dev/test on multi-tenant SaaS, production self-hosted

• Multiple RunWhen Local instances reporting to a single workspace

All RunWhen Local instances communicate outbound to one Platform endpoint, regardless of deployment model.

Comparison

Migration Paths

• Multi-Tenant to Single-Tenant: Database migration performed by RunWhen. Approx. 15 minutes downtime.

• SaaS to Self-Hosted: Export workspace, install self-hosted platform, import, redirect RunWhen Local agents. Approx. 1 hour (or parallel run for zero downtime).

• Self-Hosted to SaaS: Reverse of above process.

All migration paths are supported. Contact info@runwhen.com for migration planning.