Magento / Adobe Commerce
The Magento stack we wish someone else managed for us.
Varnish + Redis + ElasticSearch / OpenSearch + tuned MySQL. Indexers, message queues, and cron workers each on their own cgroup so the storefront stays responsive when the catalog reindexes.
What's tuned for Magento
Defaults that match the Magento DevDocs — not the cheapest config that boots.
Varnish 7 at the edge
ESI fragments, checkout bypass, customer-segment-aware caching. Configured by humans who can read VCL.
Redis split: cache + session
Two Redis instances, one for cache one for sessions. No more 'session lock contention degraded checkout'.
OpenSearch / ElasticSearch
Managed search cluster, snapshotted nightly. Re-indexing has its own worker slice.
Queue + cron isolation
bin/magento cron:run and consumers run on dedicated systemd slices. Long-running jobs don't choke web traffic.
Dedicated CPU floor
Magento needs every cycle during checkout. Your plan is your floor, not the average over five minutes.
Composer-first deploys
Atomic deploys with composer install --no-dev. Maintenance mode handled, generated content cached.
Magento migration
Considering Magento on managed hosting? Let's scope it.
We will do a free architecture review for stores over 20k SKUs and propose a migration plan with a rollback window.