Skip to content

Roadmap

Pilum supports 10 deployment targets across GCP, AWS, Azure, Cloudflare, npm and Homebrew. This page tracks what has shipped recently and what comes next.

Deployment Targets

TargetRecipe (type)Status
GCP Cloud Rungcp-cloud-runSupported
GCP Cloud Run Jobsgcp-cloud-run-jobSupported
GCP Cloud Run (from image)gcp-cloud-run-from-imageSupported
GCP Artifact Registry imagegcp-artifact-registry-imageSupported
GCP Managed Instance Groups (Compute Engine VMs)gcp-mig-containerSupported
AWS Lambda (SAM)aws-lambdaSupported
Azure Container Appsazure-container-appsSupported
Cloudflare Pagescloudflare-pagesSupported
npmnpmSupported
HomebrewhomebrewSupported
Docker Hub / GHCR—Planned
AWS ECS / Fargate—Planned
GitHub Releases—Planned
AWS S3 static sites—Planned
Fly.io—Planned
Kubernetes (manifests or Helm)—Exploring

Each supported target has a page under Providers in the sidebar.

Recently Shipped

FeatureReleased
Automatic build cache warming for Go, npm, pnpm, Yarn, Bun, uv, pip, Gradle, Maven, .NET, Cargo and Composer (guide)Oct 2026
Zero-downtime container rollouts to Managed Instance Groups (guide)Oct 2026
pilum init templates for 12 languages, including Bun, Java, Kotlin, .NET, PHP, Ruby, C and C++Oct 2026
Cloud Run: HTTP/2 end-to-end, explicit container port, staged deploys (no_traffic, revision tag)Oct 2026 (v0.7.12–v0.7.14)
pilum rollback for Cloud Run services, Cloud Run Jobs and MIGs (guide)Sep 2026 (v0.7.10)
Cloud Run service identity (service_account)Sep 2026
Cloud Run networking: VPC connectors, egress, ingress, private-by-default servicesAug 2026 (v0.7.9)
Subset deploys report dependencies they didn’t build, instead of a silent successAug 2026
Cloud Run sidecars, deploy from a prebuilt image, publish-only Artifact Registry imagesJun 2026
pilum compose: generate a docker-compose.yml with infrastructure dependencies (guide)Apr 2026
Memory- and Docker-aware worker sizing for parallel buildsApr 2026

Up Next

FeatureDescriptionStatus
Registry-backed Docker layer cacheBuild images with BuildKit and keep the layer cache in the same registry as the image (--cache-from/--cache-to), so a fresh CI runner pulls only the layers that changed. Works the same with Artifact Registry, ECR, ACR and Docker Hub.Planned
Explicit image platformBuild images for linux/amd64 whatever machine runs Pilum, so an image built on an Apple Silicon Mac runs on Cloud Run and x86 VMs.Planned
Build and push in one stepPush from the image build itself instead of uploading a second time.Planned
Rollback beyond GCPpilum rollback for AWS Lambda and Azure Container Apps.Planned
Shared deployment historyHistory and locks a team shares, instead of .pilum/ on one machine.Exploring

Requesting a Target or Feature

Open an issue on GitHub with the provider-request label for a new target, or describe the feature you need. Until a target ships, a custom recipe can usually cover it.