Pimcore Platform
Integrated digital asset and content management platform with configurable data models and publishing APIs.
7 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Use the documented Docker installation packages and configure your own hosting environment.
Runs in
Documented customer environment
Containerized PHP application with persistent database, file storage and caching services.
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
Operate hosting, database, files, caching, backups, updates and integrations; budget for implementation.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Pimcore deployment in an existing customer AWS account through Metaways ↗ · Source checked 2026-11-12
Pimcore identification of Metaways as a technology partner ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Use the documented Docker installation packages and configure your own hosting environment. |
|---|---|
| Infrastructure | Servers / containers Documented own hosting uses a Docker application environment with database and persistent files; classified as servers. |
| Licensing model | Source Available POCL is source-available with commercial and revenue-related conditions, not the former GPLv3 license. The current editions page describes free Community eligibility below EUR/USD 5 million annual revenue and for nonprofits/academic institutions. Check the applicable contract and module entitlements. |
| License | Pimcore Open Core License (POCL); free eligibility and commercial edition requirements apply. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
4 of 12 fields researched (33%) · 3 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Edition-dependentEvidence and scope for Single sign-on
The OpenID Connect enterprise bundle adds external-provider SSO to Pimcore Studio and requires an enterprise subscription. It is not a Community entitlement or a claim that every portal/front-end uses the same identity configuration.
Current 2026.3 enterprise Studio bundle; installation requires Pimcore 2026.1+ · Source ↗ · Enterprise bundle installation and prerequisites ↗ · Reviewed 2026-11-20
Edition-dependent · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The versioned 2026.2 guide documents the pimcore/skeleton Composer project and its Docker Compose environment. It is a local-development scaffold with placeholder credentials and mandatory product registration; hardening and commercial module access are separate.
Pimcore 2026.2 skeleton, not a production-ready enterprise DAM configuration · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
The current 2026.3 requirements list PHP 8.5+, database, Redis/search dependencies and a PHP memory_limit of at least 128M. That per-process setting is not a whole-server memory requirement; the reviewed guide does not establish a numeric production or 100-user/1-TB HA resource floor.
Current 2026.3 component prerequisites; full production topology/sizing remains open · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The published POCL model permits free Community use for qualifying organizations below EUR/$5 million annual revenue, non-profits and academic institutions. Professional/Enterprise use and enterprise bundles have separate commercial entitlements; confirm the applicable subscription and quote.
Published Open Core/Community eligibility and commercial edition positioning · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
Show all fields (8 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
Current editions use POCL rather than GPL. Enterprise blueprints require repository credentials; do not assume the free edition includes every advertised module. Pimcore 2026.3.5 hardens WebDAV asset permissions, document and object preview authorization, public-version ownership, password-field handling, document-editable deserialization, WebDAV delete logs, and stored-expression evaluation. Test calculated values, workflow guards, and custom document editables before rollout: unsupported expression methods are now rejected, and custom serialized classes must be allow-listed or converted to scalar or array storage. Operators on the 2026.x line should update to 2026.3.5 or later.
Category fit
- Digital asset management
- DAM capabilities include media storage, metadata, versions, asset workflows and distribution; feature availability depends on edition.
- Content management & CMS
- The platform combines traditional and headless content management with reusable content, multilingual sites and multichannel publishing.
Compare within Digital asset management
- Avalon Media SystemOpen-source audiovisual repository and access platform with an upstream AWS turnkey deployment.
- AWS
- Chevereto Self-HostedSelf-hosted image hosting and gallery management application.
- Hostinger
- Coppermine Photo GallerySelf-hosted web photo gallery and album application.
- Azure
- DamselflySelf-hosted photo asset catalog, indexing and recognition application.
- Azure
- Ente PhotosSelf-hosted encrypted photo backup and sharing backend with web clients.
- Azure
- Railway
- Hostinger
- FormKiQ Digital Asset Management Directory PublisherManage images, video, audio, and business media with a packaged DAM application, API integration, flexible metadata, approvals, and AWS deployment control.
- AWS
- HCL Digital Experience Cloud Native 9.5Commercial web content and digital asset management platform deployed by Helm to customer-operated Kubernetes.
- AWS
- Azure
- Google Cloud
- LibrePhotosSelf-hosted photo library with search and recognition.
- Hostinger
Showing 8 of 18 other listings in Digital asset management. These products address related workflows; read their category-fit notes before comparing scope. See all of Digital asset management →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- DAM and on-premises deployment ↗pimcore.com
- DAM and DXP content capabilities ↗pimcore.com
- Installation ↗docs.pimcore.com
- Own hosting setup ↗docs.pimcore.com
- Current edition license model ↗pimcore.com
- Pimcore upgrade notes ↗docs.pimcore.com
- Pimcore 2026.3.5 security release ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Pimcore deployment in an existing customer AWS account through Metaways ↗ · AWS
Partner evidence · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Pimcore technology partner Metaways explicitly offers the Pimcore platform in an existing customer AWS account, with cloud resources under customer control and optional/contracted partner operations. This establishes a customer-account hosting path, not an assurance that every edition is unrestricted or customer-operated by default. Review current POCL/module entitlements and the operations agreement. Azure is described as a future option and is not assigned.
- Pimcore identification of Metaways as a technology partner ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The Pimcore technology-alliance directory identifies Metaways as a partner. Pair that relationship with Metaways' explicit customer-AWS-account deployment statement; this partner listing alone is not the cloud evidence and does not establish current edition licensing.
- Pimcore deployment in an existing customer AWS account through Metaways ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked