Apache-2.0
Source and NOTICE in the repo. License check in CI.
For Magento teams who own the account
Agencies running several shops, and SME owners without a dedicated DevOps hire, who want Magento-shaped YAML instead of a blank infrastructure repo.
- Familiar config
magelift.yamlfollows ACC/Upsun habits Magento people already know. - Your invoiceCompute and data stay in your cloud. MageLift is the CLI, not a reseller.
- Destroyable previewsSpin a preview, share a URL, tear it down. Protected destroys need
--yes. - Honest matrixOnly certified cells are production-supported. Experimental stays labeled.
From install to preview
Certified path today: AWS ECS Fargate and GCP GKE Autopilot. Prefer free-tier-safe shapes until you mean to spend.
- Install with
go installuntil the first release tag, then prefer a release archive. Runmagelift version. - Copy
examples/sample-shop/magelift.yaml, fill account and secret refs, thenmagelift config validate. - Bootstrap once, then
preview/deployon a certified target. Destroy when the spike is done.
Certified targets
Multi-cloud means the two certified first-party targets below. Everything else in the matrix is experimental until it earns a certified cell.
| Target | Status |
|---|---|
| AWS ECS Fargate | Certified |
| GCP GKE Autopilot | Certified |
| AWS EKS / OVH MKS / Scaleway Kapsule | Experimental |
Trust that survives a staff review
Apache-2.0 source, NOTICE, and CI license checks. No mystery SaaS clause.
Release hygiene
First release ships archives with checksums and SBOM.
Digest promote
Build once, promote by digest. Mutable tags are not the happy path.
Independent
Not affiliated with Adobe. Product names are descriptive only.
Start with the docs, not a sales call
Install the CLI, validate the sample shop, then decide if a certified preview belongs in your account. Questions:SUPPORT.