// Platform

Jaws Deploy Stack

Own the deployment control plane. Jaws Deploy Stack runs on-prem or in your private cloud with the same release model as Jaws Deploy Cloud — no shared environment, no vendor hosting dependency.

Contact sales Start free on Cloud

Stack vs. Cloud: the same product, different hosting

Jaws Deploy Cloud and Jaws Deploy Stack use identical deployment logic. Projects, releases, environments, variables, targets, agents, and deployment history work the same way in both. The difference is who hosts and manages the application server.

With Cloud, Jaws Deploy manages the platform on your behalf. With Stack, your team installs and runs it — on a server you control, inside a network boundary you define, with authentication integrated into your existing identity provider.

Why teams choose Stack

Stack is the right choice when deployment metadata, release history, credentials, or platform access must stay inside a private environment. Common drivers include compliance obligations that restrict external SaaS usage, on-prem network architectures where deployment targets are not reachable from the internet, and internal policies that require a single-tenant deployment platform with no shared infrastructure.

Private by default Stack runs entirely on your infrastructure. Release records, deployment logs, credentials, and configuration never leave your environment.
Compliance-ready hosting No shared infrastructure means no cross-tenant exposure. Stack fits environments where deployment tooling must satisfy internal security review, audit requirements, or sector-specific compliance controls.
OIDC authentication Connect Stack to your existing identity provider through OIDC. No separate credential store for the deployment platform — your engineers log in with the same accounts they use everywhere else.
Works inside private networks Stack can operate without internet exposure. Agents reach the Stack server over your internal network, which suits air-gapped infrastructure and strict egress policies.
What to plan for

Stack requires a server you own and maintain.

Unlike Cloud, Stack puts platform operations in your team's hands. You choose when to update, how to back up, and how to expose the application to agents and users. For most teams this is a dedicated Linux server or VM — not a high-overhead operation, but a real hosting commitment.

Jaws Deploy provides installation packages and guidance. Your team handles the operating system, storage, network access, and update schedule.

  • A dedicated server or VM running Linux (Debian-based distributions recommended)
  • Outbound agent connectivity or internal DNS for agent-to-Stack communication
  • An OIDC-compatible identity provider or local admin credentials for initial setup
  • Storage for the application database and deployment logs

Minimum infrastructure requirements

Stack is designed to run efficiently on modest hardware. A single server or VM with 2–4 CPU cores, 4–8 GB RAM, and SSD-backed storage is sufficient for most team sizes. Linux on Debian or Ubuntu LTS is the recommended base — it gets the most testing and has the most straightforward installation path.

For larger organizations, Stack can be deployed behind an internal load balancer or reverse proxy. Database and log storage can be pointed at external volumes for easier backup and growth management.

Learn more

Jaws Deploy Cloud Jaws Deploy Agents

// Next step

Need the deployment control plane on your own infrastructure?

Contact sales Start free on Cloud