tectake's shop ran on Adobe Commerce Cloud (Enterprise), locked into Adobe's managed cloud pipeline and Enterprise licensing to serve 19 country storefronts and a second brand, dressforfun.de, off one codebase.
We rebuilt the platform from scratch as Magento Open Source with Hyva, self-hosted on Maxcluster, migrated search from Algolia to Typesense, and kept it feeding from the same Akeneo PIM.
run_as_root has managed tectake's Magento codebase since 2020. Over that time the shop grew into a pan-European home and furniture retailer running on Adobe Commerce Cloud, the Enterprise edition, deployed through Adobe's managed cloud pipeline.
That setup covered a demanding catalog: 19 country storefronts and a second brand, dressforfun.de, all on the same instance. It also meant every year of growth came with an Adobe Commerce Enterprise bill and a deploy pipeline tectake didn't fully control.
The old codebase was fully Enterprise: its composer root package was magento/project-enterprise-edition, pulling in magento/product-enterprise-edition and the full Magento Cloud metapackage, deployed to Adobe's own infrastructure.
That same repo already listed Hyva packages as dependencies. The move toward Hyva had started before anyone committed to leaving Adobe Commerce Cloud altogether.
Search ran on Algolia, and deployments went through Adobe's ece-tools and cloud-patches. None of it was broken, just expensive to license and awkward to fully own.
A new repository was started in June 2025 and seeded days later from the existing shop's code and configuration, rebuilt from the ground up as genuine Community Edition: composer root package magento/project-community-edition, no Enterprise-only modules like customer segments, target rules, or rewards anywhere in the lock file.
The commit history tells the story better than any announcement would. From June through December 2025, the new codebase saw a steady 25 to 36 commits a month, a quiet build phase. From January 2026 it accelerated hard: 69, then 60, then 90, then 189, 168, 176, and 261 commits in July 2026 alone.
That's a "build it right, then ship fast" curve, not a big-bang rewrite. 1,164 commits later, the repo sits at version ~v1.12.1.
The stack underneath is documented and current: PHP 8.3, Redis 7.2, RabbitMQ 4.1, OpenSearch 2.19, Varnish 6.0, Typesense 29.0.
This isn't a staging demo. We verified it directly against the live production host, read-only: Magento CLI 2.4.8-p5, release 2.10.2 shipped August 7 2026, release 2.11.0 shipped August 12 2026.
It's carrying real weight: 19 country storefronts (Germany, Austria, Switzerland, Belgium, France, Spain, Italy, the Netherlands, the UK, Czechia, Slovakia, Poland, Denmark, Sweden, Norway, Finland, Portugal, Slovenia, and Hungary) plus dressforfun.de, its own brand with its own Hyva theme package, on the same platform.
tectake's codebase has grown across two brands and 19 storefronts over six years. Swapping Enterprise for Open Source wasn't the hard part, the tooling discipline underneath it was.
~123 custom tectake/ modules living under src/tectake/ as composer path-repositories, covering things like EU eco-tax compliance, Content-Security-Policy hardening, Prometheus metrics export, a GTM/analytics data layer, and the Akeneo connector layer. Another ~10 vendor-fork namespaces (amasty, bizum, cadence, Ceymox, cplus, mageplaza, redchamps, sovendus) carry patched third-party integrations.
Static analysis with teeth: PHPStan level 8 with bleeding-edge rules, deptrac enforcing that Controllers and ViewModels only call down into Services and Models, never up. Magento2, PSR-12, and Slevomat coding standards, declare(strict_types=1) everywhere, no switch statements, early-exit pattern enforced, strict comparisons only.
Tests that actually run: a Playwright end-to-end suite alongside PHPUnit unit and integration tests, inside a GitLab CI pipeline that lints, runs static analysis, checks architecture, tests, builds, and deploys, scoping static analysis to changed files only to keep it fast.
Security didn't stop with the license: Adobe's own security bulletins and patches are still applied on top of the Open Source codebase, split per module, most recently for APSB26-92.
Book a 30-minute call where we look at your current Adobe Commerce Cloud setup and map out what a Magento Open Source + Hyva rebuild would take for your shop.
Technologies Used
Tags