Release Orchestration
Environment-aware workflows, policy gates, and digest-first identity. Every release decision exports a cryptographically signed Decision Capsule.
Most deployment tools tell you what was deployed. They can't tell you why it was safe to deploy.
Digest-firstRelease identity based on immutable content hashes (SHA-256 digests) rather than mutable tags — ensuring byte-identical deployments identity — immutable, auditableReleases are identified by content-addressed SHA-256 digests, not mutable tags. Same digest = same artifact = same evidence.
Model your pipeline as environments with promotion rules. Dev → Stage → Prod with evidence gates at each step.
EnvironmentA logical deployment target (e.g. dev, staging, prod) that tracks its own release history, promotion rules, and policy gates-specific policy profilesPromotions require passing gates. Security verdicts, approval signatures, and freeze windows are all evaluated.
OPAOpen Policy Agent — an open-source policy engine that enables fine-grained, context-aware policy enforcement across the stack/Rego policiesRoll back to a previous digest with full evidence trail. Know exactly what you're returning to.
Decision CapsuleA signed, exportable evidence bundle that seals every input and output of a release decision for offline audit and deterministic replayProgressive rollouts with evidence at every step. A/B testing, canary, and feature-flag deployments with rollback safety.
Every promotion command outputs structured evidence.
$ stella release promote api-gateway --to staging --approve
Promoting api-gateway (sha256:abc123...) to staging
Security gate: PASSED — 8 reachable CVEs below threshold
Approval gate: PASSED — signed by jsmith@example.com
Freeze window: PASSED — no active freeze
Deployment to staging-cluster started...
Deployed successfully
Decision Capsule exported: staging-abc123-2026-01-20.yamlStep graphs with parallel and sequential execution.
Built-in steps plus custom automation.
Reusable workflows across projects.
Bash and .NET scripting for custom logic.
Calendar-based deployment blocking.
Compliance-ready evidence bundles.
Every promotion sealed in an exportable, replayable evidence bundle.
Re-run any promotion decision 6 months later with identical results.
Approvals, verdicts, and artifacts bound by cryptographic hashes.
Route traffic between two release versions. Compare metrics, then commit to the winner with evidence.
Roll out to a small percentage of targets first. Promote wider only after evidence gates pass.
Maintain two identical environments. Switch traffic atomically after policy evaluation.
Revert to the last-known-good digest instantly. Evidence from both forward and rollback promotions is preserved.
Start with environment setup and your first promotion.