Below is a ranked list of 15 open-source PIM systems and commerce frameworks with PIM capabilities, sorted by GitHub star count. Each entry includes the repository, star count, description, key features, e-commerce integrations, and notes on project activity. The list distinguishes between dedicated PIMs — purpose-built for multi-channel product enrichment — and commerce frameworks whose product modules can serve PIM functions. All projects are actively maintained as of June 2026 (projects with no commit or release within 12 months are excluded).
1. Medusa (medusajs/medusa) – 32.9k★
Repository: medusajs/medusa Stars: 32.9k Type: Commerce framework with product module
Description: TypeScript/Node.js commerce platform with a decoupled, modular architecture. The v2 release includes 17 commerce modules, with a standalone product module that can be adopted independently. Its bundles, bulk editor, and rich product modeling make it usable as a PIM-like product data backbone.
Key Features:
- Flexible product types, options, and variants with custom modules and link modules
- REST/Admin API (v2 dropped the GraphQL store API) for headless product data delivery
- Sales channels with multi-currency and multi-region support
- Basic file module for product media (not a full DAM)
E-Commerce Integrations: Medusa is the storefront backend (Next.js starters). It functions as a Shopify alternative, not a connector into existing platforms like Magento or Shopify.
Project Activity: Very active — frequent 2.x releases through 2026; ~4,400 forks; large contributor base.
2. Bagisto (bagisto/bagisto) – 27,448★
Repository: bagisto/bagisto Stars: 27,448 Type: Commerce framework with product module
Description: Laravel + Vue.js e-commerce framework whose product engine supports multiple channels, locales, currencies and custom attributes — features that overlap directly with PIM work. Built by Webkul, the same company behind the dedicated PIM UnoPIM (entry #6).
Key Features:
- Custom attributes, attribute families, and category trees
- REST + GraphQL APIs via the headless-ecommerce package
- Multi-channel, multi-locale, and multi-currency product management
- Product media management (not a standalone DAM)
E-Commerce Integrations: Bagisto is the platform itself. Supports Next.js and Vue Storefront headless front ends. The UnoPIM Bagisto connector syncs PIM data into Bagisto stores.
Project Activity: Very active — commits through June 2026; ~3,200 forks; MIT license.
3. Saleor (saleor/saleor) – 23,024★
Repository: saleor/saleor Stars: 23,024 Type: Commerce framework with product module
Description: Python/Django, GraphQL-only, API-first headless commerce platform. Marketed with batteries-included PIM capabilities: a rich content model for large catalogs, dynamic attributes and metadata, and native multichannel control of product/pricing/stock per channel.
Key Features:
- Dynamic product types with custom attributes and metadata
- GraphQL-only API with 160+ webhook events for integration
- Native multichannel architecture with per-channel pricing and inventory
- Product media management with translations support
E-Commerce Integrations: Saleor is the commerce engine. Extensible via apps and webhooks. Not designed as a connector into other carts.
Project Activity: Very active — production line is 3.x; ~6,000 forks; BSD-3 license.
4. Spree Commerce (spree/spree) – ~15.1k★
Repository: spree/spree Stars: ~15.1k Type: Commerce framework with product module
Description: Ruby on Rails, API-first, modular commerce platform. Product and catalog features — metafields, CSV importer/exporter, digital products, product tags, bulk operations — let it act as a product data hub feeding multiple sales channels.
Key Features:
- Products with metafields and variants; CSV import/export for bulk operations
- REST API with TypeScript SDK (OpenAPI 3.0 spec)
- Multi-store, markets, multi-currency, and multi-language support
- Active Storage media management
E-Commerce Integrations: Spree is the platform. Includes a Next.js storefront and integrations with Stripe, Adyen, and PayPal.
Project Activity: Active — repo updated late 2025; ~4,900 forks; BSD-3 license.
5. Alokai / Vue Storefront (vuestorefront/vue-storefront) – ~10.9k★
Repository: vuestorefront/vue-storefront Stars: ~10.9k Type: Frontend/middleware layer (marginal PIM relevance)
Description: TypeScript/Vue/Nuxt (and Next.js) Frontend-as-a-Service plus an Express middleware layer. This is a storefront and integration layer, not a PIM — it has no product data store of its own. It consumes product data from a backend rather than managing it. Included because it connects to multiple commerce backends and can aggregate product data at the frontend layer.
Key Features:
- GraphQL middleware that unifies product data from multiple backends
- No native data model or product storage
- Frontend-level i18n and localization
- No DAM capabilities
E-Commerce Integrations: Native connectors to Magento 2, Shopify, Shopware, commercetools, BigCommerce, and SAP Commerce.
Project Activity: Very active — updated June 2026; ~2,000 forks; MIT license.
6. UnoPIM (unopim/unopim) – 10,000+★
Repository: unopim/unopim Stars: 10,000+ Type: Dedicated PIM
Description: A purpose-built, Laravel 12-based open-source PIM from Webkul, explicitly engineered for catalogs of 10 million+ products. The strongest dedicated PIM by star count, with active development of AI-assisted product management features in 2026.
Key Features:
- Families, attributes, and attribute groups (Akeneo-like canonical data model)
- REST API with official PHP client for integration
- Dedicated UnoPIM DAM module for digital asset management
- Multi-channel, multi-locale, and multi-currency product scoping
E-Commerce Integrations: Official Shopify connector and official Bagisto connector. REST API for custom platform targets. No native Magento 2 connector identified as of June 2026.
Project Activity: Very active — v2.1.0 released May 13, 2026; ~117 forks; MIT license.
7. Sylius (Sylius/Sylius) – ~8.5k★
Repository: Sylius/Sylius Stars: ~8.5k Type: Commerce framework with product module
Description: PHP/Symfony headless commerce platform built on API Platform. Its product model — products, options, variants, attributes, channels, locales, currencies — is robust enough to serve as a product data source for multi-market stores.
Key Features:
- Products with variants, options, and custom attributes
- REST API via API Platform (GraphQL feasible through the same layer)
- Multi-channel, multi-locale, and multi-currency product management
- Basic product media management
E-Commerce Integrations: Sylius is the platform. Plugin marketplace for extensions.
Project Activity: Very active — v2.2.6 (security release) on June 2, 2026; MIT license.
8. Vendure (vendure-ecommerce/vendure) – ~6.9k★
Repository: vendure-ecommerce/vendure Stars: ~6.9k Type: Commerce framework with product module
Description: TypeScript/NestJS headless commerce platform with a GraphQL API. Catalog modeling — products, facets, custom fields, channels — plus a customizable admin panel make it usable as a product information backbone.
Key Features:
- Products, variants, facets, and custom fields for flexible catalog modeling
- GraphQL API as the primary interface
- Asset management with pluggable storage backends
- Multi-channel and multi-language support
E-Commerce Integrations: Vendure is the platform. Plugin ecosystem with storefront starters for Remix, Qwik, Angular, and Next.js.
Project Activity: Very active — v3.x; GPLv3 license (with plugin license exception).
9. Pimcore (pimcore/pimcore) – 3.8k★
Repository: pimcore/pimcore Stars: 3.8k Type: Dedicated PIM/PXM platform
Description: PHP/Symfony open-core platform combining PIM, MDM (Master Data Management), DAM, CDP and CMS in a single system. The most feature-complete dedicated PIM on this list and the only one with first-class DAM and GraphQL delivery built in.
Key Features:
- Fully custom data model via the class editor and Data Objects — the most flexible modeling on this list
- REST + GraphQL (Datahub) APIs for product data delivery
- Native DAM with previews for 200+ formats, versioning, and channel-specific output
- Channel-independent data with full multilingual support
E-Commerce Integrations: API and Datahub integration to any system. Community Magento 2 bridge module available. Pimcore Commerce framework for native storefront use.
Project Activity: Very active — v2026.1.5 released June 9, 2026; ~1,500 forks; Pimcore Open Core License.
10. Shopware (shopware/shopware) – 3,373★
Repository: shopware/shopware Stars: 3,373 Type: Commerce framework with product module
Description: PHP/Symfony + Vue.js open commerce platform. Its Data Abstraction Layer (DAL), custom fields, properties and media manager allow it to function as a product data and asset hub. Recent releases add AI-powered product feed (JSONL) export channels.
Key Features:
- Data Abstraction Layer entities with custom fields and properties
- REST Admin API + Store API for headless integration
- Media manager with DAM-level capabilities
- Sales channels with multi-language support
E-Commerce Integrations: Shopware is the platform. Over 3,100 community extensions. Alokai/Frontends for headless storefronts.
Project Activity: Very active — 6.7.11.0 released June 2026; ~1,180 forks; MIT license.
11. Akeneo Community Edition (akeneo/pim-community-dev) – 1,024★
Repository: akeneo/pim-community-dev Stars: 1,024 Type: Dedicated PIM
Description: The reference open-source PIM. PHP/Symfony with CalVer versioning (vYYYY.Minor). Despite a modest star count relative to commerce frameworks, Akeneo CE has the best native e-commerce connector story of any dedicated open-source PIM and defines the canonical PIM data model that other projects (UnoPIM, AtroPIM) have adopted.
Key Features:
- Families, attributes, and attribute groups with scopable (channel) + localizable (locale) attributes — the canonical PIM model
- REST API for all product data operations
- Basic media and file attributes in CE (full Asset Manager is an Enterprise feature)
- First-class channel and locale scoping throughout the data model
E-Commerce Integrations: Official Magento 2 connector (akeneo/magento2-connector-community). Shopify connector via Akeneo Apps. REST API for custom targets.
Project Activity: Very active — v2026.3 released March 30, 2026; ~538 forks; OSL-3.0 license.
12. Catmandu (LibreCat/Catmandu) – ~194★
Repository: LibreCat/Catmandu Stars: ~194 Type: Data-processing toolkit (niche, non-commerce)
Description: A Perl data-processing toolkit from the LibreCat project, designed for libraries, archives and museums (MARC, JSON, YAML, OAI formats). This is a metadata ETL/conversion toolkit, not an e-commerce PIM. It lacks product-attribute modeling, channels, DAM and store connectors. Included for completeness as a data-processing option that could theoretically feed product data into other systems via its Fix transformation language.
Key Features:
- Schema-agnostic record processing via the “Fix” transformation language
- CLI and Perl module interfaces (no product API)
- Support for MARC, JSON, YAML, OAI and other metadata formats
- No DAM, no channels, no locale support
E-Commerce Integrations: None. No Magento, Shopify, or any e-commerce platform connectors.
Project Activity: Maintained but slow — ~2,502 commits; latest release 1.2025 (July 7, 2025); ~17 contributors; GPL/Artistic license.
13. AtroPIM (atrocore/atropim) – 187★
Repository: atrocore/atropim Stars: 187 Type: Dedicated PIM
Description: A highly configurable, modular open-source PIM that runs as a module on the AtroCore data platform (PHP). In active development since 2018, maintained by AtroCore GmbH. Offers the broadest native e-commerce connector matrix of any dedicated PIM on this list.
Key Features:
- Fully configurable entities, attributes, relations, and layouts
- REST API for all operations (GraphQL integrations via modules)
- AtroDAM module for digital asset management
- Multi-channel and multi-language product data scoping
E-Commerce Integrations: Documented integrations to Adobe Commerce (Magento 2), Shopware, PrestaShop, WooCommerce, Shopify and Sylius via modules — the widest connector coverage among dedicated PIMs.
Project Activity: Active — ~5,136 commits; latest release 1.13.0 (April 11, 2026); company-maintained; GPLv3 license.
14. OpenPIM (openpim/server) – ~76★
Repository: openpim/server Stars: ~76 Type: Dedicated PIM
Description: A small but genuinely dedicated PIM. Node.js/TypeScript application server exposing a GraphQL API, backed by PostgreSQL using JSONB for a flexible object model. Lightweight enough to deploy with a single Docker command.
Key Features:
- Flexible JSONB-based object model with configurable types, attributes, and channels
- GraphQL (primary) + REST APIs
- File storage for product images and files
- Channels concept with multilingual support
E-Commerce Integrations: Integration via GraphQL/REST APIs. No widely-documented turnkey Magento or Shopify connectors — custom middleware required.
Project Activity: ~834 commits; 8 contributors; no GitHub releases (versioned via Docker image tags); Apache-2.0 license. Note: exact last-commit date could not be independently verified — confirm on GitHub before adoption.
Excluded After Verification
Ergonode (github.com/ergonode/backend, ~105 stars, PHP/Symfony) — excluded as abandoned. The repository was archived by the owner on February 13, 2023 and is now read-only. Its last release (1.3.0) dates to January 28, 2022, and the frontend repository was last committed roughly four years ago. With no commits within the last 12 months, it fails the activity threshold despite being a well-designed PIM in its day. Ergonode remains widely referenced in “open-source PIM” lists, so its exclusion here is deliberate.
Comparison Table
| Platform | Stars | Language | Type | API | Magento | Shopify | DAM | Last Release |
|---|---|---|---|---|---|---|---|---|
| Medusa | 32.9k | TypeScript/Node | Commerce | REST | No | No | Basic | 2026 (2.x) |
| Bagisto | 27,448 | PHP/Laravel | Commerce | REST + GraphQL | No | No | Basic | 2026 (2.x) |
| Saleor | 23,024 | Python | Commerce | GraphQL | No | No | Basic | 2026 (3.x) |
| Spree | ~15.1k | Ruby/Rails | Commerce | REST + SDK | No | No | Basic | 2025 (5.x) |
| Alokai | ~10.9k | TypeScript/Vue | Frontend | GraphQL | Yes (frontend) | Yes (frontend) | No | June 2026 |
| UnoPIM | 10,000+ | PHP/Laravel | Dedicated PIM | REST | No | Yes | Yes (module) | v2.1.0 (May 2026) |
| Sylius | ~8.5k | PHP/Symfony | Commerce | REST | No | No | Basic | v2.2.6 (June 2026) |
| Vendure | ~6.9k | TypeScript/NestJS | Commerce | GraphQL | No | No | Yes (assets) | 2026 (3.x) |
| Pimcore | 3.8k | PHP/Symfony | Dedicated PIM | REST + GraphQL | Community module | Via API | Yes (native) | v2026.1.5 (June 2026) |
| Shopware | 3,373 | PHP/Symfony | Commerce | REST | No | No | Yes (media mgr) | 6.7.11.0 (June 2026) |
| Akeneo CE | 1,024 | PHP/Symfony | Dedicated PIM | REST | Yes (official) | Yes (Apps) | Limited | v2026.3 (March 2026) |
| Catmandu | ~194 | Perl | ETL toolkit | CLI | No | No | No | 1.2025 (July 2025) |
| AtroPIM | 187 | PHP | Dedicated PIM | REST | Yes (module) | Yes (module) | Yes (AtroDAM) | 1.13.0 (April 2026) |
| OpenPIM | ~76 | TypeScript/Node | Dedicated PIM | GraphQL + REST | No | No | Basic | Docker-tagged |
Dedicated PIMs are highlighted in bold.
How to Choose a PIM for Your E-Commerce Stack
The choice between a dedicated PIM and a commerce framework’s product module comes down to how many systems consume your product data.
Team size and engineering capacity. Akeneo CE and Pimcore are heavyweight Symfony applications requiring PHP ops expertise. AtroPIM and UnoPIM are lighter but still need a managed Linux server. OpenPIM (Docker, single command) is the lowest-friction to stand up. Commerce frameworks require Node (Medusa, Vendure), Python (Saleor), Ruby (Spree), or PHP (Sylius, Bagisto, Shopware) competency respectively.
Catalog complexity. Pimcore’s class editor and Akeneo’s family/attribute/scopable model handle deep, multi-locale, multi-attribute catalogs. UnoPIM is explicitly built for 10M+ products. Commerce-framework product modules suit moderate catalogs tied to a single storefront.
Existing commerce platform. Running Magento 2? Akeneo CE (official connector) and AtroPIM (module) provide the most direct integration path, with Pimcore available via a community bridge. Running Shopify? UnoPIM, AtroPIM, and Akeneo (Apps) connect natively.
Headless vs. monolith. Headless-first stacks favor GraphQL-native options: Saleor, Vendure, OpenPIM, or Pimcore Datahub. Full-stack deployments favor Bagisto, Spree, Sylius, or Shopware.
Single source of truth. Choose a dedicated PIM (Akeneo CE, Pimcore, UnoPIM, AtroPIM, OpenPIM) when multiple downstream channels consume one enriched product source. Use a commerce framework’s product module when a single platform is both the system of record and the storefront.
FAQ
What is a PIM and why do e-commerce stores need one?
A Product Information Management system is a central repository where teams aggregate, enrich, validate and syndicate product data — attributes, descriptions, media, translations — to multiple sales channels. Stores need one when product data lives in spreadsheets or is duplicated across channels, causing inconsistency, slow time-to-market and localization errors.
Which open-source PIM has the best Magento 2 integration?
Akeneo Community Edition — it ships an official, maintained Magento 2 connector (akeneo/magento2-connector-community). AtroPIM also offers an Adobe Commerce (Magento 2) integration module, and Pimcore can connect via a community bridge.
Can I use a PIM with Shopify?
Yes. UnoPIM and AtroPIM ship Shopify connectors, Akeneo connects via Akeneo Apps, and Alokai integrates Shopify on the frontend layer. Any PIM with a REST or GraphQL API can sync to Shopify via the Shopify Admin API with custom middleware.
What’s the difference between a PIM and a DAM?
A PIM manages structured product data — attributes, SKUs, pricing fields, relationships. A DAM (Digital Asset Management) manages rich media files — images, video, documents — with metadata, versioning and format derivatives. Some platforms combine both: Pimcore has a strong native DAM, and UnoPIM (module), AtroPIM (AtroDAM) and Shopware include DAM-grade media management.
Should I choose a PIM based on GitHub star count?
No. Stars measure popularity and visibility, not fitness for your use case. Commerce frameworks accumulate far more stars than dedicated PIMs because of broader developer audiences. Weight maintenance activity (recent commits and releases), data-model fit, channel/locale support, API type and connector availability more heavily than star count.
Star counts reflect June 2026 readings. GitHub stars change daily — verify against the live repository before making adoption decisions. Community Edition features are assessed; several platforms gate additional capabilities behind Enterprise or commercial editions.
