Akeneo PIM hosting explained: Akeneo Cloud (SaaS) vs managed hosting vs VPS

At Tandemite, we assess hosting for Akeneo as an implementation partner, focusing on how your product information management (PIM) platform will process data and connect to other applications. Those workloads determine what your PIM system needs to run reliably.

TL;DR

• Akeneo SaaS includes hosting and platform maintenance provided by Akeneo.
• Akeneo Community Edition requires infrastructure and ongoing maintenance arranged by you or a partner.
• Managed Akeneo hosting delegates agreed operations; an unmanaged VPS leaves them with your team.
• Compare Akeneo hosting options by total cost of ownership, including upgrades, backups, and incident response.
• SaaS minimizes administration, managed hosting offloads CE upkeep, and a VPS requires in-house technical skills.

Hosting for Akeneo: choose the edition first, the server second

Does Akeneo need hosting? Only if you run Community Edition or maintain an older installation built to be self-hosted. With the SaaS editions, Akeneo hosts and runs the application for you. So step one is figuring out which edition fits your processes, and on what terms it's delivered and maintained.

Akeneo's current package comparison lists three tiers within Akeneo Product Cloud: Growth, Advanced, and Premium. The documentation still uses the older names. Akeneo Growth Edition maps to the Growth package, while Akeneo Enterprise Edition sits behind Advanced and Premium. Product Cloud is the umbrella name for the broader offering, which covers the PIM and related products.

Akeneo Flexibility was a platform-as-a-service (PaaS) offering that allowed application customization. Akeneo has stopped releasing new versions of Flexibility and Enterprise on-premises. Its published schedule lists September 30, 2026, as the end-of-support date for version 7 of those offerings; CE follows a separate release cycle.

SaaS editions: Akeneo Product Cloud

Software as a service (SaaS) provides access to software over the internet. With Akeneo Cloud, Akeneo operates the application and infrastructure, delivers updates, and manages resources under the service agreement.

You remain responsible for the data model, user accounts, permissions, and connections to other systems. Integrations and custom extensions still need technical ownership, even when Akeneo PIM itself runs as SaaS.

Akeneo Community Edition: infrastructure and maintenance are your responsibility

Akeneo Community Edition (CE) is the open-source edition of the PIM, available with no license fees. To run it, you need a server and a configured environment, plus someone to maintain both over time. Self-hosting means you're responsible for all of that, although you can outsource it to an external provider.

CE is worth considering when its features cover your requirements, you need access to the source code, and you have the budget to support the application. New CE releases are published in Akeneo's repository; at the time of writing, the latest release there was v2026.4.

What Akeneo PIM needs from its infrastructure

elf-hosted Akeneo PIM is a PHP/Symfony application backed by MySQL and Elasticsearch, and much of its load comes from background jobs rather than user traffic. When sizing infrastructure, plan for imports, catalog updates, and exports running at the same time as users working in the PIM.

The Akeneo technology stack

• PHP and Symfony run the application; PHP-FPM manages PHP processes handling web requests.
• MySQL stores application data; Elasticsearch supports search and filtering indexes.
• Queue workers process background jobs and need monitoring and restart mechanisms.
• Node.js supports frontend build tools used during deployment.
• A web server, such as Apache, and a configured Linux environment support the application.

Check the official Akeneo system requirements and match them against the CE release you've chosen. Older guides may reference different component versions. Before using MariaDB, Nginx, or a specific Debian or Ubuntu release, confirm it's compatible with your Akeneo version. If you run Akeneo in Docker, you'll also need a configuration prepared for production use.

What drives resource use: imports, queues, and indexing

Importing a large file hits the CPU during validation and transformation, memory during processing, and the disk during writes. Mass edits work the same way: a single user action can trigger many database and index updates.

Recalculating product completeness, which checks required attributes for each channel and locale, adds even more data operations. Reindexing Elasticsearch needs CPU, memory, and fast disk I/O. Keep plenty of free disk space and schedule reindexing so it doesn't collide with critical exports.

Exports read data, generate files, and push them to their destinations. Image processing and thumbnail generation consume CPU, memory, and storage. If your project includes an external DAM (Digital Asset Management) system, some of that work can happen outside Akeneo.

When automated product data processes in Akeneo span many workflows, you need to define their order and deadlines. Say your morning export to the online store must include data from the overnight import. If the import runs late, the store may receive stale information, even though the PIM itself stays up. That's why a performance test should confirm the entire job chain finishes before its deadline.

How to size an Akeneo server

Sizing depends on how your catalog is built and how your data moves, not on website traffic. Factor in:

• the number of SKUs (stock keeping units) and how your variants are structured;
• the number of attributes and product families, which group products sharing the same attributes;
• locales (language and regional versions) and distribution channels;
• the number of concurrent users and the kind of work they do;
• import volumes and how often data flows through the API, the interface that connects applications;
• the size of media files, indexes, and backups, plus expected data growth.

When planning for scaling Akeneo for B2B, ask for the proposed configuration to be tested against data and jobs that reflect how your company actually works. Base decisions on vCPUs (virtual CPUs), RAM, and disk capacity on the results of that test.

Option 1: Akeneo Cloud (SaaS), where Akeneo handles the hosting

Akeneo Cloud is a SaaS service in which Akeneo hosts and maintains PIM, also documented as Akeneo Serenity. You configure your catalog and use the capabilities included in your package.

Akeneo is responsible for the infrastructure, the databases, and standard application updates. The subscription covers PIM hosting as described in the offer. Budget separately for integrations, extensions, and any environments they need to run. Review the subscription terms for the specific feature set and support level you need.

In SaaS, you extend Akeneo through the API and apps rather than by modifying core code. When evaluating performance, account for API rate limits: exceeding them can cause requests to be rejected, so integrations should retry after an appropriate wait. Akeneo also recommends batching operations to reduce the number of calls.

Before choosing a package, verify that your integrations can move all the data you need within your time windows. Vendor lock-in, meaning the cost and difficulty of switching providers, also depends on which features you rely on and how easily you can export your data.

This option makes sense when your company has limited capacity to run the system in-house and the SaaS features match your processes. SaaS can even cost less overall than CE if self-hosting plus building the missing features would exceed the subscription. A fair comparison uses the same functional requirements, integrations, and time horizon for both.

Option 2: Managed Akeneo hosting, or Community Edition without an in-house DevOps team

Managed Akeneo hosting means a specialized provider runs your PIM infrastructure within an agreed scope. For Community Edition, that can include server configuration, component updates, monitoring, and backups.

The application runs on resources covered by the service, such as a VPS or dedicated servers. The fee covers infrastructure and administration, while work on Akeneo code and major upgrades may be billed separately. Whether you can change server settings or install extra components depends on the provider's terms. This option suits companies that choose CE and want to outsource the environment.

Who's responsible for what in managed hosting

Your contract should separate server maintenance from application maintenance, including updates to Akeneo and its extensions. Test the split with one concrete question: you can still log in to the PIM, but the export to your online store has stopped. Who acts? Name who detects the problem, who starts the diagnosis, and who coordinates getting the process back up. The table below helps you assign responsibilities in each model.

Questions to ask a managed Akeneo hosting provider

• Which Akeneo releases do you support, and who checks dependency compatibility?
• Do backups cover the database, media, and configuration, with tested restores?
• Where are backups stored, and how long are they retained?
• What does the service-level agreement (SLA) cover, including incident response times?
• Does monitoring detect stalled queues, failed imports, and delayed exports?
• Is a separate staging environment included?
• Who upgrades Akeneo and tests custom extensions?
• Where is data stored, and who has administrative access?

When planning your Akeneo implementation, agree on the maintenance scope up front, including the integrations and processes the system will support.

Option 3: Akeneo on a VPS, with full control and full responsibility

A VPS (virtual private server) is a virtualized slice of a physical server that behaves like a dedicated machine, with its own operating system and an allocated share of resources. Running Akeneo on VPS means you install and maintain the application yourself. Root access gives you full administrative rights over the operating system, while a hypervisor such as KVM handles virtualization on the physical host.

In a simple setup, the application, MySQL, and Elasticsearch all run on one machine. The VPS fee covers only the allocated resources; administration, backups, and application support are separate line items. If a VPS offer includes server administration (managed VPS hosting), evaluate it against the same criteria as managed hosting.

When an Akeneo VPS makes sense

Akeneo on a VPS is worth considering when you've chosen CE, can estimate your workload, and have a Linux administrator working closely with the team that develops the application. A VPS also works well as a development or test environment. Before going live, test performance and confirm you can restore the system within a timeframe the business can accept.

Infrastructure examples include Hetzner, DigitalOcean, and Contabo. Compare resource allocation, storage performance, data center locations, and support terms for the specific plan.

Risks: a single server, upgrades, and noisy neighbors

When MySQL, Elasticsearch, and import jobs share one machine, they compete for memory and disk. Running at the same time, they can squeeze each other's available RAM and read/write throughput (I/O). Running out of RAM can kill a process or slow the application to a crawl. And if that machine fails, every component on it stops: it's a single point of failure.

The noisy neighbor problem occurs when heavy workloads from other customers on the same physical host degrade your performance. How much it matters depends on how the provider allocates resources. On top of that, your own team has to plan CE upgrades, test extensions, and respond to failed jobs.

What about Public Cloud (AWS, GCP)? Akeneo on IaaS is still self-hosting

IaaS (Infrastructure as a Service) lets you rent computing resources from providers such as Amazon Web Services, Google Cloud Platform, or Microsoft Azure. Unlike SaaS, it gives you building blocks like virtual machines, storage, and networking, and leaves running the application to you. If every Akeneo component runs on a single Amazon EC2 instance, one failure can take the whole system down.

A more resilient architecture can include a separate database, such as Amazon RDS running a compatible MySQL version, a dedicated Elasticsearch service, and media storage such as Amazon S3 once the integration is in place. High availability (HA) requires redundant components, failover mechanisms, and monitoring. With pay-as-you-go pricing, also factor in data transfer, backups, and add-on services.

Akeneo SaaS vs managed hosting vs VPS: side-by-side comparison

The three models differ in what the service covers and who is accountable for keeping the PIM running. Because managed hosting can itself run on a VPS, "VPS" in this comparison means the option without provider administration. Always evaluate each offer on its own terms.

The right Akeneo hosting model is the one that matches your edition, your maintenance capacity, and your required availability at a comparable total cost.

Under the GDPR, personal data in a PIM can include user accounts and information stored in logs. When evaluating a provider, review the data processing agreement (DPA), subprocessors, administrative access, and any transfers outside the European Economic Area (EEA). If you require EU data residency, the requirement should cover backups too; server location alone doesn't make the whole process compliant. If the provider is subject to US jurisdiction, also consider how the US CLOUD Act could affect government access to data, even when it's stored in the EU.

What does Akeneo hosting cost? Compare total cost of ownership

Total cost of ownership (TCO) includes implementation and ongoing operation over a defined period. Compare 12 and 36 months using the same catalog, integrations, and availability requirements.

Estimate administration costs as monthly hours multiplied by the fully loaded hourly rate. Model two scenarios: routine maintenance, and a period that includes a major upgrade or an outage. In both, include extra environments, testing, and disaster recovery (DR), meaning the restoration of operations after a serious failure.

Then find the break-even point: how many hours of work make self-managed CE as expensive as managed hosting or SaaS. If a small increase in hours flips the result, your decision hinges on that assumption. The 12- and 36-month model should also account for catalog growth and the business cost of downtime, such as delayed product launches. With SaaS, integration support still needs its own line in the budget.

How to choose Akeneo hosting: 5 questions to answer first

Your edition, workload, and operating capabilities narrow the options. Use these questions to request comparable proposals.

1. Which edition meets your requirements? SaaS means Akeneo hosts the PIM. With CE, you need to decide who owns the infrastructure and who is accountable for the application.
2. How many SKUs, locales, and channels will you manage? With CE, a large catalog means checking whether a single VPS is enough or whether components need to be split across several servers. With SaaS, confirm that the package matches your catalog size and growth plans.
3. How large and frequent are imports and integrations? If large CE imports overlap with other jobs, your team or managed hosting provider should monitor resource usage and adjust schedules. With SaaS, check API limits and integration mechanisms against your planned data flows.
4. Do you have an administrator or DevOps team? A self-managed VPS requires people who are available to maintain both the application and the infrastructure. Without those skills, compare SaaS with fully managed CE.
5. What availability and data residency do you need? If the business can tolerate only brief interruptions, check how the SaaS provider or your CE team ensures continuity and data recovery. In every option, and especially on a single VPS, review the technical safeguards, the contractual guarantees, and where data and backups are stored.

Three typical scenarios

These examples show how hosting choices map to common business situations.

A manufacturer with a simple catalog and one channel. If CE covers the features you need and you have an administrator, a VPS can be a sound choice. The rollout should then include monitoring setup and a test restore from backup.

A B2B company with multiple markets and an ERP integration. If you choose CE and don't have an in-house administrator, consider managed hosting that includes application support. You'll need to coordinate ERP (enterprise resource planning) syncs with catalog exports to your sales channels.

An enterprise group with multiple teams and strict permission requirements. Evaluate SaaS for user collaboration, data governance, and support coverage. If the project also involves a CMS (content management system) or a B2B portal, first decide which platform will own which functions. Our Pimcore vs Akeneo comparison can help you weigh the options.

Switching models later: migrating Akeneo between a VPS, managed hosting, and the Cloud

The scope of an Akeneo migration depends on whether the edition and version change and whether custom code needs to be adapted. In your timeline, estimate environment setup separately from the cutover window needed for the final sync and switching over integrations. A trial migration lets you measure transfer time, verify catalog completeness, and determine when users can get back to work.

VPS to managed hosting. With a compatible environment, the migration covers the database, media, configuration, and application code. You'll need to rebuild indexes, set up job schedules, start the queue workers, and reconnect external systems, then test imports and exports. The cutover plan should define when changes to the old system freeze, how the final data sync works, and the conditions for rolling back. The main risk is missing files or processes that live outside the application directory.

Community Edition to SaaS. This move requires mapping your data model and features to the chosen package, then transferring data through supported import mechanisms or the API. PHP extensions and changes to the CE core need a separate review: configuration will replace some of them, while others must be rebuilt as integrations or apps. Plan for a trial migration, data reconciliation, and business process testing. Confirm the extent of Akeneo's support and the available migration tools for your specific project.

SaaS to self-hosting. First, check that the features you need are available in CE and that you can export your data, media, and configuration. Recreating SaaS features may require additional development work. Also agree on how long you'll keep access to the service after the contract ends, so you can run final tests and retrieve your data.

Summary: your hosting model is a decision about responsibility

Your Akeneo hosting model determines who maintains the environment, delivers upgrades, and restores service after an incident. Start with required features and the edition, then assess catalog complexity, integrations, and availability. Workload tests, a clear division of responsibilities, and a realistic TCO comparison provide a practical basis for choosing. Together, they show whether your budget and operating team can support the system after launch.

Plan maintenance alongside implementation, because data structures and integrations shape infrastructure needs. Our approach to implementing and maintaining Akeneo connects requirements analysis, integration, and ongoing application support.