Less source database work
98%
fewer MySQL operations
186 → 4 operations per request
Magento without Axle → Magento with Axle
A faster server response
32%
lower time to first byte
228 → 155 ms median TTFB
Magento without Axle → Magento with Axle
Measured on the same category page showing 12 products, in a lab catalog of over 100,000 products. Local results; performance on your store requires evaluation.
Local lab results and methodology
Both cards describe the area-rugs category page displaying 12 products. MySQL profiler operations decreased from 186 to 4 (97.85% fewer); median TTFB decreased from 227.70 to 155.16 ms (31.86% lower). Percentages and displayed timings are rounded. MySQL counts include connection, session setup, freshness validation and source batching; local native reads are reported separately and are not counted as MySQL operations. Rounded medians from 20 alternating pairs after three warm-up pairs, recorded on 10 October 2026. MageOS 3.5 / Hyvä 1.5.2, production application mode, compiled DI, warm PHP OPcache and two single-child PHP-FPM pools. Full-page and block HTML caches were disabled. Direct loopback FastCGI measurements exclude public-network, proxy and browser latency and concurrent load. These are specific lab results; performance on your store requires evaluation. The live comparison below uses a different request setup.
Hyvä + Axle
Performance on both sides of the page.
Hyvä: a lighter frontend
Hyvä uses Alpine.js and Tailwind CSS to reduce the JavaScript and CSS shoppers’ browsers need to load and process. It focuses on the storefront experience on their devices.
Explore Hyvä’s frontend approachAxle: faster backend catalog reads
Axle reduces request-time MySQL work by serving supported catalog reads from prepared local data through a native PHP extension. It focuses on the server work before the page reaches the browser.
Explore Axle’s backend technologyThe comparison uses the same Hyvä theme on both sides, so it shows what Axle adds to an existing Hyvä storefront. It does not measure a theme migration or isolate Hyvä’s frontend gains.
For the people running and building stores
Keep your storefront. Reduce the work behind it.
For merchants
Combine Hyvä’s lightweight storefront with Axle’s backend catalog acceleration. Reduce both browser work and supported request-time database work.
- Magento still renders your theme and product pages.
- Supported reads do less request-time work against MySQL.
- Evaluate the results on your catalog and configuration.
For agencies and developers
Build the frontend with Hyvä’s Alpine.js and Tailwind CSS stack, then evaluate Axle beneath Magento’s resource calls to address backend catalog work.
- A background worker prepares supported catalog data.
- Diagnostics and observe, shadow, on and off modes support evaluation.
- Unsupported or invalidated reads fall back to MySQL.
Try the verified MageOS / Hyvä lab
See what Axle adds to Hyvä.
Compare Hyvä with and without Axle on a catalog of over 100,000 products. Browse either storefront to compare the same catalog page. Both faster and slower results are shown.
Page performance · warm requests
Waiting for both storefronts…
Same hardware. Page caching disabled.
Both sites run on the same machine and share the same CPU, memory, database and storage. Full-page cache and block HTML cache are disabled on both sites. Normal Magento includes 805 ms of simulated hosting latency per dynamic request. Displayed timing differences include this artificial delay. Public pages are requested once to warm each server, then requested again for measurement. Displayed TTFB and LCP exclude the warm-up wait; total browser timings remain in Page details. Cart and other actions use a single request. Adjusted LCP is a warm-server demo measurement, not a production Core Web Vitals result.
| MEASUREMENT | Normal Magento | With Axle | DIFFERENCE |
|---|---|---|---|
| Largest paint LCP | — | — | — |
| Time to first byte TTFB | — | — | — |
| Database queries | — | — | — |
Normal Magento
PAGE
/Page details Normal Magento
Waiting for this page…
With Axle
PAGE
/Page details With Axle
Waiting for this page…
Your page visits
Compare results as you browse.
| PAGE | LCP · NORMAL → AXLE | TTFB · NORMAL → AXLE | DATABASE QUERIES |
|---|---|---|---|
| Your completed page comparisons will appear here. | |||
How it works
Prepare once. Read locally. Render with Magento.
- 01
MySQL source data
Your source database remains authoritative.
- 02
Background preparation
The worker exports supported data and publishes prepared datasets.
- 03
Native local reads
Eligible resource calls read the prepared data through the PHP extension.
- 04
Magento rendering
Magento hydrates its models and renders your storefront.
Unsupported reads and data that fails freshness checks use MySQL. Checkout, customer, order and session operations remain live through Magento.
Under the hood
The stack, in the open.
Axle accelerates supported catalog reads. It does not replace Magento’s business logic or your search engine.
Axle components
- Rust
- Read admission, translation, preparation and native integration.
- PHP + ext-php-rs
- A native PHP extension and a Magento PHP module bridge supported resource calls.
- Embedded SQLite
- The broader prepared read engine executes against indexed, immutable local datasets.
- LMDB
- The original attribute-read path uses local key-value storage.
Storefront and lab
- MySQL
- The authoritative source database and fallback for live or unsupported reads.
- OpenSearch
- Continues to provide Magento’s search and layer selection.
- MageOS + Hyvä
- The comparison demonstrates MageOS 3.5 with Hyvä 1.5.2, using Alpine.js and Tailwind CSS, and a 107,815-product lab catalog.
- Linux + PHP 8.4 NTS
- Linux is the assumed evaluation environment. Build the native extension against the running PHP ABI and verify compatibility on your configuration.
Compatibility and early access
What to know before evaluating Axle.
How do Hyvä and Axle work together?
Hyvä focuses on frontend performance with less JavaScript and CSS for the browser. Axle focuses on backend performance by reducing supported catalog database work before Magento renders the page. The lab runs both together; its side-by-side results measure Axle’s additional effect with Hyvä held constant.
Which configurations have been verified?
Magento Open Source 2.4.8-p5 has collection and storefront coverage for the original attribute-read path. MageOS 3.5 / Hyvä 1.5.2 has broader prepared-engine coverage, including six product types in the large lab. Broader Adobe Commerce, other versions, MSI configurations and merchant extensions require evaluation.
What does installation involve?
A Magento PHP module, a native extension built for the running PHP ABI, a preparation worker and local persistent storage. Tracking requires MySQL permissions. Current setup is intended for controlled staging evaluation; a production installer and signed release binaries are not yet available.
How does Axle handle catalog changes?
Transactional tracking records supported source changes. Requests validate the prepared revision; changed dependencies fall back to MySQL until fresh data is prepared. Supported catalog reads pin a revision for the request. This is not a strict transactional snapshot across prepared reads and live fallbacks.
Does Axle replace full-page caching?
No. The comparison disables full-page and block HTML caches to show underlying request work. Axle can coexist with page caching, but a warm full-page hit is a cache result and does not demonstrate native catalog acceleration.
Will it work with our extensions?
Compatibility must be checked on your configuration. Unknown query families and guarded custom implementations use ordinary execution. Integrations that bypass the guarded database adapter require verification before acceleration is enabled.
Is Axle open source?
Axle is being built for open source release by On Tap. The release licence and public release date have not been confirmed.
What does joining the waitlist offer?
You can request early evaluation access as a merchant, agency or developer and hear about the open source release. Joining does not guarantee immediate access, an assisted pilot or a release date.
Merchants · agencies · developers
Get early access to Axle.
Join the waitlist to request early evaluation access and hear about the open source release.
Tell us whether you run a store or build for others. Access is for evaluation; availability and release timing are not yet confirmed.
The waitlist form is not connected yet. Please check back for early access requests.
Open the waitlist form in a new tab