Built 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.yaml follows ACC/Upsun habits so Magento people can read the file without learning a new product dialect first.
Your invoice
Compute, data, and edge stay in your cloud. MageLift is the CLI and adapters, not a host that resells capacity.
Destroyable previews
Spin a preview, share a URL, tear it down. Production and protected destroys stay explicit with --yes.
Honest matrix
Only certified cells are production-supported. Experimental targets stay labeled. No fake green.
From install to preview
- Install with
go installuntil the first release tag, then prefer a release archive (checksums + SBOM). 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.
Full path:Getting started·Leave PaaS in a weekend
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 signals that survive a staff review
Apache-2.0
Source, NOTICE, and license check in CI. No mystery SaaS clause.
Release hygiene
First release ships archives with checksums and SBOM. Images on GHCR use the Cosign path once the image workflow publishes digests.
Digest promote
Build once, promote by digest. Mutable tags are not the happy path.
Independent
MageLift is independent of Adobe Inc. Magento and Adobe Commerce are Adobe trademarks, used only to describe compatibility.
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.