// Technology stack
The stack we build on — and why
We deliberately keep our stack narrow. Shopware, PHP/Symfony, Node.js, React and Vue — chosen because they are stable, well documented, hire-able and still fast in ten years. No framework of the month, no lock-in you cannot leave.
// Layers
Six layers, one team
Every project touches most of these. Because the same team owns all of them, nobody can hide behind an interface boundary.
E-Commerce
Backend
Frontend
Data & Integration
Cloud & DevOps
Quality & Security
// Shopware
Shopware 5 vs. Shopware 6 — an honest comparison
Both are good platforms. Which one is right depends on where your shop is today, not on what is newest.
| Topic | Shopware 5 | Shopware 6 |
|---|---|---|
| Core framework | Zend / Enlight, Smarty | Symfony, Twig, Vue.js admin |
| Templating | Smarty templates, LESS | Twig templates, SCSS, Bootstrap 5 |
| API | REST API, limited coverage | Admin API + Store API, fully headless-capable |
| B2B features | B2B Suite plugin, customer groups, price rules | B2B components, Rule Builder, Flow Builder, advanced pricing |
| Best for | Stable, heavily customised shops that still earn well | New builds, headless plans, long-term investment |
| Our recommendation | Keep maintained & secure while you plan the move | Default choice for anything new |
// Engineering principles
Rules we do not break
No core hacks
Everything goes into plugins, bundles or app-level code. Your shop must stay updatable — a core hack is a debt that comes due on the next security release.
You own the repository
Code lives in your Git, with readable commits and a README that lets another developer set the project up in an afternoon.
Staging before production
Nothing reaches the live shop without a staging deploy you have seen and approved. Deployments are scripted, never manual FTP.
Data model first
Before UI work starts we agree on entities, relations and the source of truth for every field. Most integration pain is a data-model problem in disguise.
Performance is a feature
Indexed queries, HTTP caching, lazy loading and a Lighthouse budget agreed up front. A slow B2B shop costs orders every single day.
Boring where it counts
Payment, pricing, stock and invoicing get the dullest, most tested code we can write. Creativity belongs in the UX, not in the money path.
// FAQ
Stack questions we get often
Yes. We maintain and extend existing Shopware 5 shops (PHP, Smarty, Enlight) and build new stores on Shopware 6 (Symfony, Twig, Vue.js administration). We also handle the migration between the two.
Yes. We regularly take over projects written by other agencies. We start with a code and infrastructure review, document what we find, and then work in your repository following your conventions and branching model.
Where it pays off. A headless React or Vue storefront on the Shopware Store API makes sense for very custom UX, app-like shops or multi-channel setups. For a standard B2B shop, a well-built Twig theme is usually faster to deliver and cheaper to maintain — we say so openly.
We work with Docker-based environments, Git-driven deployments and CI pipelines. We can deploy to your existing hoster, to a managed Shopware host, or to AWS / Hetzner infrastructure that we set up and document for you.
Not sure which stack fits your shop?
Send us your current setup — we will tell you honestly what to keep, what to replace and what to leave alone.