On-premises deployment

Your infrastructure. Your policy. Your records.

ShieldedStack is an on-premises product. Deploy the proxy, Portal, worker, and migrations in your environment with Docker Compose or Helm, and operate them to your standards.

Run the complete product on-premises

The proxy enforces package policy. The Portal hosts the console, API, and read-only MCP endpoint. The worker collects package intelligence and delivers alerts. The migration service keeps the database schema aligned with the release.

Policies, inventory, and audit records live in your own database.

Choose Docker Compose or Kubernetes

Docker Compose

Bring up the trial stack with externalised configuration and the bundled services. Use it to validate package-manager setup and workspace policy in your environment.

Helm

Deploy on Kubernetes 1.27 or later. For production, connect your own services and supply credentials through existing Secrets.

A bundled database and Keycloak are provided for trials. Production deployments should use database, identity, backup, and availability arrangements that meet your operational requirements.

Own the control plane and plan the external connections

No product telemetry or vendor-hosted control service is required. You operate the database, access controls, retention, and backups.

Normal operation contacts package registries, the ShieldedStack advisory service for vulnerability and malware lookups, and public license and package information sources. Advisory lookups carry public package coordinates only and are not recorded. Configured notification channels send alerts to their destinations.

Planning an air-gapped deployment? Talk to us about registry and intelligence updates first.

Roll out workspace by workspace

  1. Connect a representative pipeline. Configure its package managers and project API key, and confirm that requests appear in the logs.
  2. Review the controls. Choose vulnerability thresholds, denied licenses, release age, and any approved-package rules. Trust-Then-Verify permits missing evidence, but still enforces known policy violations.
  3. Verify before admission. Use Verify-Then-Trust where packages must meet evidence requirements before delivery. Validate exception and incident-response workflows with your team.

Container images require trusted signed SBOMs or explicit allow rules in either mode. Account for this when introducing image pulls.

Start with the deployment quick start →

Test it on your infrastructure

Use the 30-day on-premises trial to validate your package managers, policies, and operations. Prefer a first look? The separate 7-day hosted Portal evaluation uses synthetic package activity.