Busabase
Busabase is an open-source (MIT) database and workspace for AI agents — data, docs, skills, and apps in one place. Run it locally, self-host it inside your network, or use Busabase Cloud, and turn age
翻訳待ち
Fastest time-to-market and rapid digitization with the enterprise data and experience management platform for PIM/MDM, DAM, DXP/CMS, CDP, and digital commerce.
翻訳待ち
データPHP · TwigGitHub @pimcoreオンライン所有者未確認
Have you tried it? One tap is enough. No sign-in needed.
Core Framework for the Open Core Data & Experience Management Platform (PIM, MDM, CDP, DAM, DXP/CMS & Digital Commerce)
翻訳待ち
Loading the full README. The saved excerpt is shown below.
Open Core Platform for Product Experience Management (PXM)
One platform. Any data. Any channel. Any process.Read the full README ↗Pimcore is an open core platform for Product Experience Management (PXM). It provides a solid, API-driven foundation for managing digital data and customer experience, combining a Core Framework with a modular set of Core Extensions covering PIM, MDM, DAM, CDP, DXP/CMS, and Digital Commerce — all licensed under the Pimcore Open Core License (POCL). Data is stored independently of the channel and delivered to any output: websites, commerce systems, mobile apps, print, digital signage, or headless consumers via REST and GraphQL. Pimcore Studio provides the unified administration interface for the entire platform.
Pimcore ships with rich out-of-the-box functionality and is designed to be fully customizable and extensible. You define your own data models, build your own templates or consume the APIs, integrate with any IT infrastructure, and tailor the platform to exact project requirements — from a single standalone implementation to a complex multi-system architecture.
All data in Pimcore is organized into three core element types that can be linked and related to each other:
Data Objects — manage any structured data based on a class-editor-defined model, either manually or via API. Covers products (PIM/MDM), categories, customers (CDP), orders (Digital Commerce), and articles (DXP/CMS). Delivers consistent data to multiple output channels from a single source.
Assets (DAM) — store and manage any file type. Preview 200+ formats directly in Pimcore, auto-generate channel-specific output formats, and enrich files with metadata and versioning.
Documents (DXP/CMS) — build pages with Twig templates and inline editables, with full multilingual and multi-site support, plus emails, newsletters, and web-to-print.
Pimcore is modular. Its modules ship as separate Composer packages (Core Modules & Extensions), all licensed under POCL:
See Pimcore Modules for the full list and Pimcore Editions for module availability per edition (Community, Professional, Enterprise, PaaS).
Pimcore follows a layered architecture where multiple interfaces — the Studio administration UI, server-rendered websites, and headless API consumers — all operate on the same core data layer.
Technology stack:
Two delivery patterns:
Both patterns can be used alongside each other in the same project.
See the Architecture documentation for full details including application layers and the data flow between them.
Each module has its own repository and is released independently. The pimcore/platform-version
package bundles a set of specific module versions that are tested and verified to work together, released as a single
version such as 2026.1. Major Platform Versions ship once per year; the documentation and demos are based on Platform
Versions. Starting with 2026.1, every module carries the same version number as the platform. New projects depend
on pimcore/platform-version by default.
Pimcore 2026.x uses Docker for local development. No local PHP or Composer installation is required.
Prerequisites: Docker and Docker Compose installed, and your user must be allowed to run Docker commands and change file permissions.
This is the beginning of the README. Read the rest at the original. Read the full README ↗