PrestaShop, cyber_Folks, Sylius and BitBag: What the Acquisition Really Means

On 18 February 2026, cyber_Folks announced it had completed the acquisition of 100% of PrestaShop, together with Sylius and BitBag, through its subsidiary cyber_Pixel. If you run a PrestaShop store, the natural reaction is a small jolt of anxiety: does my platform still have a future, and do I need to do anything? This is the honest, developer's-eye answer to that question — what is actually confirmed, what is still just a press-release promise, and what (if anything) it changes about how you run and build on PrestaShop right now.

Last updated: June 2026.

Short version: keep running your store, keep it updated, and judge the new owners by what ships — not by what they announce. The longer version is more interesting, especially if you build modules or run shops for clients, because the deal is a clear bet on a larger European open-source ecommerce ecosystem.

What is actually confirmed

It's worth separating the verifiable facts from the interpretation, because most of the noise around this deal blurs the two.

• Buyer: cyber_Pixel, a subsidiary of cyber_Folks.
• Seller: Fortidia / MBE Worldwide.
• Asset acquired: 100% of PrestaShop SA.
• Grouped with: Sylius and BitBag, under the same cyber_Pixel umbrella.
• Stated scale: investor communication describes a combined ecosystem above 700,000 customers and around EUR 35 billion annual GMV supported by group technologies. Treat the GMV figure as the buyer's own framing of the whole group, not a PrestaShop-only number.

The cyber_Folks investor announcement frames PrestaShop as one of the world's largest open-source ecommerce platforms, and GESSEL (which advised the buyer) published a transaction summary covering all three properties. Everything beyond those facts — roadmap promises, "AI-driven innovation," ecosystem ambitions — is direction, not delivery.

Who actually bought it, and why that's reassuring

cyber_Folks is a Polish technology group built on hosting, domains, SaaS and ecommerce services. The group is connected to Shoper, and Jakub Dwernicki is publicly described as president of both cyber_Folks and Shoper in PAP/Bankier coverage. So what does that mean for you? This is not a financial holding company that bought a logo. It's an operator that already runs hosting, merchant billing, app marketplaces and software distribution at scale. The deal logic is coherent in a way that a private-equity flip usually isn't — and that lowers (without eliminating) the risk of the platform being milked and starved.

That said, "owner who understands ecommerce" is a reason for cautious optimism, not a guarantee of good execution. Shoper is a closed SaaS product; PrestaShop is self-hosted open source. The interesting tension is whether the new owner treats those as complementary or eventually nudges PrestaShop toward a more managed, hosted, monetized shape.

Will PrestaShop stop being free or open source?

This is the question that actually keeps store owners up at night, so let me be precise. There is no credible signal that PrestaShop is about to close its source or become a SaaS-only product. PrestaShop's own March 2026 monthly update explicitly frames the future around open source, and the cyber_Folks investor messaging repeatedly describes PrestaShop as an open-source platform. In a live Q&A with Mikolaj Krol and Olivier Binet, the new direction was summarized around four themes: a clearer roadmap, stronger technology partnerships, AI-driven innovation with a continued commitment to open source, and a central role for the ecosystem.

But here's the honest nuance most coverage skips: "open source stays open source" is not the same as "everything stays free." The GPL license on the core is one thing; the commercial surface around it is another. Ownership can shift priorities on hosting bundles, the official Addons marketplace, cloud services and which features land in core versus a paid tier. The license protects your right to keep running and modifying the code you already have. It does not promise that every future convenience will be free. That's not a reason to panic — it's a reason to keep your store on a footing where you're never dependent on a single vendor's roadmap, which is good practice regardless of who owns the platform.

The one practical thing this changes today: nothing

Let me make the boring point loudly, because it's the correct one. An ownership change is not a migration trigger. Your store runs on the exact same code the day after the deal as the day before. There is no patch to apply, no setting to flip, no "acquisition mode" in Advanced Parameters → Information. If a vendor or consultant uses this news to push you toward re-platforming, treat that as a sales tactic, not analysis.

What does deserve a few minutes of your attention is the discipline that makes any ownership transition a non-event for your shop:

• Keep your version maintained. Track which branch you're on (the footer of your back office and Advanced Parameters → Information show it) and stay current within it. A store on a fully patched supported branch, or a legacy branch with an explicit maintenance plan, is far safer than a frozen one, whoever owns the brand.
• Avoid core overrides where you can. Every file in /override and every hard theme fork is a future upgrade tax. The lighter your customization sits on top of core — modules and hooks rather than patched core classes — the more painlessly you absorb whatever the new owners ship.
• Watch 9.1 and 9.2 adoption, but don't be first. The new direction will show up in releases. Let the early adopters find the regressions; you adopt once your modules confirm compatibility.
• Test native features on staging. The most-hyped near-term core change is a native one-page checkout in 9.2. Before you trust it on a live store, exercise it on a copy — covered below.

The native one-page checkout question — don't conflate it with the deal

Because the acquisition Q&A name-checked checkout and "ecosystem," a lot of merchants have mentally bundled "new owners" with "I'll finally get a real one-page checkout for free." Two separate things. PrestaShop's move toward a native one-page checkout is a roadmap item that predates and outlives this deal, and crucially, the default checkout you have today is not a true one-page checkout — it's a single URL with four collapsed gates (the order controller's stepped flow). If checkout friction is costing you orders now, the acquisition changes nothing about your timeline. We laid out exactly what the platform gives you, what it doesn't, and your realistic routes in our PrestaShop one-page checkout guide — the decision of whether to wait for native 9.2 OPC or act today stands entirely on your own conversion numbers, not on who signed the deal.

The real developer signal: a bigger, more coherent ecosystem

For module authors, agencies and integrators, this is where it gets genuinely interesting. In a PAP/Bankier interview, Jakub Dwernicki noted that Shoper already had app partners building for roughly 20,000 customers, and that combining the platforms multiplies the addressable merchant base. The argument isn't "development continues" — it's "a larger pool makes it more worthwhile to build serious apps and integrations."

Sylius and BitBag fit that thesis from a different angle. They serve a market PrestaShop traditionally doesn't:

In theory these complement rather than cannibalize: PrestaShop for owners who want to assemble a store from ready modules, Sylius for projects that need code-level control, BitBag bridging the two. The watchpoint for independent developers is the usual one — whether the official marketplace and platform partnerships stay fair enough that building for PrestaShop remains worth the investment. That fairness, not the headline GMV figure, is what determines whether the ecosystem grows or hollows out.

One ecosystem theme worth flagging without over-reading it: "AI-driven innovation" appeared repeatedly in the new direction. I'd put that in the watch-it column rather than the act-on-it column for now. If you're thinking about how AI actually fits into day-to-day PrestaShop work today — independent of any platform roadmap — that's its own discussion, and I wrote up where I landed in AI tools for PrestaShop work in 2026.

How we're reading it as a module developer

We build commercial modules for PrestaShop, so we have skin in this. The opportunities a healthier, better-funded ecosystem opens up are concrete: checkout, B2B, performance and caching, integration connectors, migration tooling and upgrade safety are all areas where merchants pay for capability the core doesn't ship. A bigger merchant base makes that work more sustainable, which is good for everyone who relies on third-party modules.

The flip side is real too: a more centrally-managed platform usually means stricter compatibility expectations and faster-moving APIs. So what does that mean for you as a buyer of modules? It raises the value of vendors who keep pace with core — who actually test against new branches, ship updates, and answer you directly when something breaks. Our own answer to that pressure is to support PrestaShop 1.6.1 through 9.1 (PHP 7.1+) across the catalog and to handle support without a middleman, because upgrade safety is exactly the thing that gets harder when a platform speeds up. If you want the background on how we operate, that's in our grand opening post.

My take: cautiously optimistic, evidence-pending

PrestaShop genuinely needed more focused ownership, tighter roadmap discipline and better developer communication. cyber_Folks has a real ecommerce reason to invest rather than extract, the open-source commitment is on the public record, and the Shoper/Sylius/BitBag logic holds together strategically. That's a better starting position than most platform acquisitions.

But optimism isn't endorsement. The things that would convert "promising" into "good" are all measurable and none have happened yet: smoother upgrades, fewer regressions, stable and well-documented APIs, maintained native modules, and a marketplace that stays fair to independent developers. Those show up in GitHub activity, release notes and migration guides — not in announcements. So the practical posture for both merchants and developers is the same: carry on, stay current, and keep score against real releases.

If you're following our coverage of the platform and the business behind these modules, we collected the why-we-do-this and where-to-find-us pieces too: why we started this blog and where to follow us.

Frequently asked questions

Do I need to migrate off PrestaShop now that it's been acquired?

No. An ownership change is not a migration trigger. Your store runs on the exact same code the day after the deal as the day before — there's no patch to apply, no setting to flip. If a vendor uses this news to push you toward re-platforming, treat it as a sales tactic. The sensible response is the same discipline that makes any ownership transition a non-event: stay current within your branch, avoid core overrides, and test new releases on staging before adopting.

Will PrestaShop stop being free or open source?

There's no credible signal that PrestaShop is about to close its source or go SaaS-only. PrestaShop's own March 2026 update and the cyber_Folks investor messaging both frame the future around open source. The honest nuance: "open source stays open source" is not the same as "everything stays free" — ownership can shift priorities on hosting bundles, the Addons marketplace and which features land in core versus a paid tier. The GPL protects your right to keep running and modifying the code you already have.

Who actually bought PrestaShop, and is that reassuring?

cyber_Pixel, a subsidiary of the Polish technology group cyber_Folks, bought 100% of PrestaShop SA from Fortidia / MBE Worldwide, grouped with Sylius and BitBag. cyber_Folks runs hosting, domains, SaaS and ecommerce services at scale and is connected to Shoper — so it's an operator with a real ecommerce reason to invest, not a financial holding company that bought a logo. That lowers, without eliminating, the risk of the platform being milked and starved.

Does the acquisition mean I'll finally get a native one-page checkout for free?

Don't conflate the two. PrestaShop's move toward a native one-page checkout is a roadmap item that predates and outlives this deal. The default checkout you have today is not a true one-page checkout — it's a single URL with stepped, collapsed gates. If checkout friction is costing you orders now, the acquisition changes nothing about your timeline; that decision stands on your own conversion numbers.

What should module developers and agencies actually watch?

Not the headline GMV figure — watch whether the official marketplace and platform partnerships stay fair enough that building for PrestaShop remains worth it, and whether upgrades get smoother, regressions fewer, and APIs stable and well-documented. Those show up in GitHub activity, release notes and migration guides, not in announcements. The practical posture for everyone is the same: carry on, stay current, and keep score against real releases.

Sources

• cyber_Folks investor announcement about PrestaShop
• GESSEL transaction summary for PrestaShop, Sylius and BitBag
• PrestaShop Monthly March 2026 — Q&A and new direction
• PAP/Bankier interview with Jakub Dwernicki on R&D and ecosystem scale