Skip to content

Deploy for a team

Compare the deployment targets, data layers, and verified qualification boundaries.

Updated View as Markdown

Artifact Server provides five team deployment guides. The Compose guide covers compact and external-storage modes.

Choose a deployment

Deployment Data layer Verified qualification Guide
Cloudflare D1 and R2 Live staging passed Deploy on Cloudflare
Compact Compose SQLite and one file volume Automated runtime passed Deploy with Compose
External-storage Compose PostgreSQL and S3-compatible storage Automated runtime passed Deploy with Compose
Kubernetes PostgreSQL and object storage Helm and disposable kind-cluster verification passed Deploy on Kubernetes
AWS (Amazon Web Services) ECS Fargate, RDS, and S3 Default public stack passed live isolated qualification Deploy on AWS
Google Cloud (GCP) Cloud Run, Cloud SQL, and Cloud Storage Public stack passed live isolated qualification Deploy on Google Cloud

The AWS private-ingress variant has not passed its live lifecycle gate. The Google Cloud package rejects private ingress.

Use the Kubernetes guide for EKS, GKE, or AKS. Artifact Server does not provide a separate Azure installer.

Meet the remote deployment requirements

Configure one application origin

Use one HTTPS origin for the application, API, and MCP endpoint. People sign in at this origin.

Configure one isolated content domain

Use a separate registrable domain with wildcard TLS. Each artifact version receives its own hostname.

Read about the two-origin security boundary →

Configure one identity provider

Use WorkOS or one generic OIDC provider. Remote deployments do not use local-owner access.

Protect credentials

Store service credentials in the deployment platform’s secret store. Keep credentials out of source control and deployment outputs.

Configure coordinated backups

Back up metadata and artifact files as one recovery set. Verify a restore before production use.

Pin the release image

Pin production containers to an immutable image digest. Verify the release with the supply-chain guide.

Choose a data layer

Compact Compose uses one SQLite database and one file volume. Run one application process with this mode.

External storage uses PostgreSQL and object storage. Compose, Kubernetes, AWS, and Google Cloud support this data layer.

Cloudflare uses D1 and R2 through the Worker runtime. It uses the same product services as the other targets.

Continue after deployment

Navigation

Type to search…

↑↓ navigate↵ selectEsc close