Linux via SSH
Standard SSH keys or password auth. Works with any Linux server that has Docker installed.
Agentless Deployment
Deploy to Servers Without Installing Agents
Connect to your Linux and Windows servers using standard protocols. Deploy containers with progressive strategies and roll back instantly when needed.
What this means for your business
Deploy to any Linux or Windows server without Kubernetes, agents, or cloud dependencies. Stella handles rollbacks, canary promotion, and evidence export for every target.
True Agentless Deployment
No daemons to install. No ports to open. Just connect using the credentials you already have.
Windows via WinRM
Native Windows remoting. Deploy to Windows Server with Docker or containers on Windows.
Zero footprint on your servers. Stella connects, deploys, verifies, and disconnects — leaving only your application running.
That describes deployment execution, which is agentless over SSH and WinRM — nothing is installed on your hosts. Continuous Watch verification is separate: the Stella Ops agent service reads the image digests actually running on the Docker daemons it can reach, and any host it is not reporting for is shown as unobserved rather than assumed good. Estate →
Why Agentless?
Agents mean more attack surface, more updates, more things that can break. Stella deploys without them.
Nothing to Install
No agent packages, no version mismatches, no “agent offline” alerts. Just standard remote access.
Reduced Attack Surface
Every installed daemon is potential attack surface. Stella connects only when deploying, then disconnects.
Full Audit Trail
Every deployment is logged with who, what, when, and why. Evidence for compliance built in.
Simple Operations
Use your existing SSH keys and Windows credentials. No new infrastructure to manage.
Progressive Delivery Strategies
Deploy with confidence using industry-standard strategies that minimize risk and enable quick recovery.
All-at-Once
Rolling
Canary
Blue-Green
Canary Deployments
Deploy to a small percentage of targets first (10%), check for issues, then expand to 25%, 50%, and 100%. A failed stage stops the rollout, and rollback returns every target to the last approved digest.
10% 25% 50% 100%
Blue-Green Deployments
Run two identical environments. Deploy new version to “green” while “blue” serves traffic. Switch instantly when ready. Switch back instantly if problems arise.
Blue (live) → Green (deploy) → Switch
Deploy with your preferred strategy
$ stella release deploy myapp-v2.1.0 --reason "canary rollout approved"
$ stella release promote myapp-v2.1.0 --to production
$ stella deployment show myapp-v2.1.0A/B releases
Run two versions side by side for real-world comparison before full rollout. Stella pins each side to a digest and records the outcome; it does not manage traffic.
- Traffic is split by your load balancer, proxy, or service mesh — the split is configured there, not in Stella
- Each side is pinned to an exact digest, so a comparison names artifacts rather than tags
- Shift the split in your own infrastructure as confidence grows; the deployed digests stay recorded either way
- Roll back to the last approved digest with one command
Instant Rollback
When something goes wrong, roll back to the exact previous version — not “whatever was there before” but the verified, known-good state.
- Rollback restores the exact container digest that was running before
- No re-pulling “latest” or hoping tags haven’t changed
- One command to return to known-good state
Digest-Verified Rollback
Because Stella tracks exact digests, rollback deploys the identical bytes that were running before. Same artifact, same behavior, guaranteed.
How Fast?
Blue-green: instant (traffic switch). Canary/rolling: seconds (parallel revert). The previous digest is always cached and ready.
Rollback with one command
$ stella release rollback myapp-v2.1.0 --reason "error budget exhausted"
Every Deployment is Evidence
Stella records what was deployed, who deployed it, and when — with cryptographic proof.
What
Exact container digests deployed to each target
Who
Authenticated deployer identity
When
Timestamped and signed deployment record
Adopt as CD first, prove later
Gating is switched per environment. You do not have to prove everything on day one.
Unverified (CD-only)
Stella deploys like a plain CD tool: no evidence gates, nothing blocks. Stages still record whatever the pipeline provides, and the spine shows Missing where evidence is absent.
Verified
Gates evaluate evidence before promotion. A release that cannot prove its claims stops at the gate, with the failing rule named.
Switch an environment to Verified once its spine is consistently Recorded or Signed. Production can be Verified while dev stays CD-only.
Ready to deploy with confidence?
Install Stella Ops and start deploying to your servers with progressive delivery and instant rollback.