# Pilum

> Open-source (Apache 2.0), cloud-agnostic build and deployment CLI. Define each service once in a `pilum.yaml`, deploy everything with one command — locally or in CI. Pilum handles the build → push → deploy pipeline while infrastructure-as-code (Terraform, Pulumi) provisions the resources.

Key facts:
- Targets: GCP Cloud Run & Cloud Run Jobs, AWS Lambda, Azure Container Apps, Cloudflare Pages, npm, Homebrew, Docker registries
- Designed for multi-service monorepos: service discovery, parallel wave execution, `depends_on` ordering, git-aware "deploy only what changed", deployment locks, dry-run mode, JSON output for scripting and AI agents
- Not a CI/CD replacement — it runs inside GitHub Actions/GitLab CI (or on a laptop) as the deploy step, replacing glue scripts
- Not an IaC replacement — complements Terraform/Pulumi, does not provision resources
- Does NOT bypass cloud IAM or logging: it drives standard provider CLIs/APIs with your existing credentials, so policies and audit trails apply identically
- Dogfooded: deploys all SID Technologies products (Torch, Statio, Capsa, Vigil) — dozens of services, continuously
- Best fit: 3+ deployment targets or cloud + npm/Homebrew/static hosting from one repo. Single-cloud GCP teams with mature Cloud Build/Cloud Deploy pipelines may not need it (see the honest comparison below).

## Docs

- [Introduction](https://pilum.dev/docs/getting-started/introduction/)
- [Quick Start](https://pilum.dev/docs/getting-started/quick-start/)
- [When to Use Pilum (and When Not To)](https://pilum.dev/docs/guides/when-to-use/)
- [Pilum vs. GCP Native Tooling](https://pilum.dev/docs/comparisons/pilum-vs-gcp-native/)
- [Pilum vs. CI/CD Pipelines](https://pilum.dev/docs/comparisons/pilum-vs-ci-cd/)
- [FAQ](https://pilum.dev/docs/reference/faq/)
- [Multi-Service Monorepo Guide](https://pilum.dev/docs/guides/monorepo/)
- [CLI Commands](https://pilum.dev/docs/reference/cli/)

## Source

- [GitHub: SID-Technologies/Pilum](https://github.com/SID-Technologies/Pilum)