Mage-OS + Hyvä vs. Magento + Luma: Real Performance Numbers

david-lambauer — Tue, 09 Jun 2026 00:00:00 GMT

During a recent client pitch, a question came up that vendor benchmarks couldn’t answer cleanly: how much faster is Mage-OS with Hyvä than Magento with Luma under real concurrency?

I decided to find out properly. That meant identical AWS infrastructure for both stacks, a controlled k6 load test, and Full Page Cache deliberately disabled so PHP actually renders every request.

What was tested

Two stacks, zero shared resources. Each ran on its own dedicated EKS node group: four m6i.2xlarge nodes (8 vCPU, 32 GB each). Same Magento 2.4.7-p9 base. Same catalog generated by magento setup:perf:generate-fixtures: 5,000 products across 100 categories. The Luma database was generated first, then dumped and imported into the Hyvä schema to guarantee identical data.

Stack A was standard Magento with Luma: RequireJS, KnockoutJS, jQuery, layout XML with deep block nesting. Stack B was Mage-OS with Hyvä, Alpine.js, Tailwind CSS, and Typesense replacing OpenSearch for storefront search.

The key difference at the PHP level: Luma processes layout XML with complex UI component hierarchies on every request. Hyvä replaces the entire frontend layer with simpler PHTML templates and Alpine.js directives. The server-side rendering path is shorter.

Both stacks had Full Page Cache and Varnish disabled. With FPC on, both serve cached HTML at near-identical speeds. That benchmarks your cache layer, not your platform. Disabling it forces every request through the full rendering pipeline.

The results

250 virtual users, ramped over six minutes, sustained for five minutes, across a realistic traffic mix: 30% browse (homepage + category), 25% search, 25% product detail pages, 20% add-to-cart via REST API. Both stacks ran in parallel in the same time window.

Metric	Luma	Hyvä	Difference
p50 (median)	1,040 ms	201 ms	5.2x faster
p90	6,610 ms	3,580 ms	1.8x faster
p95	8,000 ms	3,680 ms	2.2x faster
Throughput	36 req/s	51 req/s	+42%

The median is the number that matters most for most users. At p50, Hyvä responded in 201 ms while Luma took 1,040 ms. Five times faster, same hardware.

The 42% throughput gap is the capacity planning number. Same infrastructure, same VU count, but Hyvä completed 40,021 requests to Luma’s 28,147 over the 13-minute test. Faster rendering frees PHP-FPM workers sooner, so more requests get through per second.

Neither stack hit a CPU or memory ceiling. Peak CPU on both was around 20-25%. The bottleneck is PHP-FPM worker concurrency, not compute.

Per-page breakdown

The improvement isn’t isolated to one slow endpoint. Every page type shows the same gap.

Page	Luma p95	Hyvä p95	Ratio
Homepage	7,545 ms	3,698 ms	2.0x
Category	7,899 ms	3,738 ms	2.1x
Search	8,320 ms	3,646 ms	2.3x
Product detail	8,121 ms	3,703 ms	2.2x
Add to cart (API)	7,754 ms	3,670 ms	2.1x

Search shows the largest gap at 2.3x. Part of that is the Typesense module returning results faster than OpenSearch for storefront queries. Typesense is also the foundation for the RAG-based AI features described in the companion post about the Shopify pitch.

What the database data shows

Both stacks shared the same RDS MySQL 8.0 instance with separate schemas. Hyvä executed fewer SQL queries per HTTP request (43 vs 56 for Luma) but examined more rows per query. Despite 7x the row I/O, Hyvä’s response times are still 2.2x faster. PHP rendering overhead dominates. Database behavior matters for optimization, but frontend architecture is the bigger lever for perceived performance.

The RDS instance stayed well below its limits throughout. Threads running peaked at 8-10, slow queries were near zero.

I ran this benchmark on 2026-04-12, using Mappia for Kubernetes deployment.

How a Mage-OS Pitch Beat Shopify Without a Feature War

david-lambauer — Tue, 02 Jun 2026 00:00:00 GMT

The marketing department had just taken over responsibility for the online shop. Within weeks, they had one request: Shopify.

Their reasoning wasn’t irrational. The existing Magento installation was several years behind on upgrades. No Hyvä. None of the modern features that had shipped since. When a competing integrator demoed a Business Central connection they’d stood up in 50 minutes, the pitch looked even more compelling.

I walked into that pitch with something different from a features list.

Stop comparing today

The feature comparison game is one you can’t win against a larger SaaS platform. Shopify has a big app store, polished dashboards, and years of marketing spend telling merchants it’s the easy choice.

So I didn’t play that game.

My first move was to reframe the question entirely. Instead of “which platform has a better page builder today?”, I asked: “What will your competitors look like in 12 months?”

My answer: AI is about to commoditize every feature on any comparison spreadsheet. ChatGPT, Claude, and their successors are available to every merchant and every competitor equally. Everyone has access to the same knowledge.

The only thing that can’t be copied is your data.

What the pitch actually showed

The demo wasn’t a 50-slide deck. I assembled it in roughly 20 minutes from things the Mage-OS community had already built.

The first piece was the Hyvä Commerce admin. The page builder question came up early. My answer was direct: every platform needs CI work to match a brand’s design. That’s true whether you pick Shopify, Hyvä, or anything else. That’s not a differentiator. The performance gap is.

The differentiator was what came next.

I showed an agentic admin proof-of-concept built by the Mage-OS team. The idea: type a prompt inside your e-commerce admin, and the system creates a landing page skeleton using content it already knows about your store. Products, categories, past purchase behavior, brand tone. You finish the last 20% in the page builder.

The room’s reaction was immediate. Marketing people don’t care how the plumbing works. They care about getting from “we have new Easter products” to “we have a live landing page” without a two-week agency sprint.

The second demo was product data enrichment. A common pain: every new product needs a name, description, short description, SEO description, and schema markup. The AI enrichment feature takes a raw input and fills the rest automatically.

The third was reporting. Forget opening a reports tab, exporting an Excel file, and pivoting a table. I showed a chat interface inside the admin: ask a natural language question, get an answer. “What were the top five bestselling categories over the last three months?” is a question you type, not a dashboard you configure.

Handling the objections nobody puts on the agenda

Every pitch like this has two people in the room who never lead with their actual concern.

There’s always someone who cares about data privacy. The answer: Mage-OS runs on infrastructure you control. You host your own LLM on AWS Frankfurt or wherever you need it. Your store’s data never trains a competitor’s model.

There’s usually someone who asks about sustainability. Hetzner and many managed cloud providers power their infrastructure with green energy. Covered.

And then there’s the quiet “but is this thing actually backed by anyone?” anxiety that SaaS platforms benefit from without earning. I used the Linux distribution analogy. Adobe Commerce is Red Hat: enterprise-grade, expensive, built for a specific bracket. Mage-OS is closer to Ubuntu: community-driven, SMB-focused, and moving fast. The Hyvä and Mollie integrations add credibility for a European merchant audience.

None of these objections derailed the meeting.

What other agencies can take from this

The demo that won this pitch was built from community work. AI data enrichment, the agentic content creation proof-of-concept, and the Typesense integration are all being built into Mage-OS core. Any agency can show up with the same story.

The technical parts aren’t the hard part. A chat interface that answers questions about your store’s data isn’t a multi-year project. A working version can be built in days with the right stack.

The hard part is the reframe. When a client is already sold on Shopify, meeting them on the features battlefield gives you a losing hand. Shift the conversation to what e-commerce actually looks like when AI is everywhere and SaaS vendors control your data.

That’s the pitch that won.

Mage-OS Hyvä