ProteinSE AB: growing 3.6× while keeping hosting simple and costs flat
How a Nordic multi-store Magento operation freed itself from vendor lock-in, simplified its entire hosting stack across two migrations, and scaled with confidence — all with zero downtime.
- Industry
- Sports nutrition / E-commerce
- Stores
- protein.se · protein.no · protein.fi · protein.dk
- Platform
- Magento 2 + Hyvä
- Infrastructure
- AWS (customer-owned account)
- Migrated
- October 2022
Results at a glance
- +260%
- Revenue growth Oct 2022 → Jan 2026
- +262%
- Order volume growth Oct 2022 → Jan 2026
- Flat
- Hosting cost base Quarterly reviews, stable throughout
- Zero
- Migration downtime Across both migrations
Two migrations, zero downtime
- Pre-2022 Divante-hosted VSF1 + Magento 2. Double vendor dependency.
- Oct 2022 Migration 1 luroConnect on AWS EKS. Kubernetes + autoscaling.
- 2023 Migration 2 Hyvä + standard server. Stack simplified.
- Today Stable & growing Customer-owned cloud. Flat costs, 3.6× revenue.
ProteinSE AB came to luroConnect in 2022 hosted by Divante — the agency that both built and hosted their site. This double dependency meant any desire to move infrastructure required moving away from their development partner too. luroConnect's managed-hosting model resolved this: ProteinSE would run on their own AWS account, with luroConnect handling the operational complexity.
The first migration in October 2022 moved the existing Magento 2 and Vue Storefront 1 stack onto a Kubernetes cluster on AWS EKS, with horizontal pod autoscaling and a cluster autoscaler to handle traffic peaks up to 20× the base load. MySQL remained managed by luroConnect. Crucially, both the migration itself and the ability to roll back to the old stack were executed with zero hosting downtime.
The second migration followed as Vue Storefront 1 became obsolete and Hyvä emerged as the modern Magento frontend. Moving to a server-driven, standard luroConnect Magento stack removed the need for five separate Node.js applications entirely. The stack became simpler, more stable, and easier to operate — again with zero downtime and full rollback capability throughout.
Challenges & how luroConnect responded
Double vendor dependency
Divante built and hosted the site — one supplier controlled both code and infrastructure. luroConnect provided a path to independence: the customer's own AWS account, managed by luroConnect.
Cloud cost anxiety
Moving to their own cloud felt financially risky. luroConnect modelled a plan at cost parity, and quarterly reviews have kept hosting costs flat even as revenue tripled.
Unstable PWA stack
Five Node.js apps alongside Magento was fragile. The move to Hyvä, guided by luroConnect, eliminated the complexity — near-zero downtime has been the norm since.
Traffic spikes up to 20×
During the EKS phase, horizontal pod autoscaling and cluster autoscaling handled extreme peaks without over-provisioning. The simplified server stack maintains the same resilience today.
Manual, error-prone deploys
Founders were logging into Bitbucket to trigger builds. luroConnect CI/CD replaced that entirely — per-store independent deployments with one-click rollback, no engineering involvement needed.
Staging & rollback safety
A full staging environment across all four storefronts means every release is tested before going live. Both migrations included the ability to roll back with zero downtime.
“After building over 500 websites, I have some experience with hosting. I've worked with more than five different Magento hosting providers. I like luroConnect because Pradip thinks differently — his solutions are smart and simple, not complex. That shows across the whole team. They get it. They move fast.”
Anton Perlkvist Co-Founder, ProteinSE AB