DAM Wiki
Side-by-side comparison

MediaBeacon vs Pimcore

Built only from the frontmatter of each solution’s overview and API pages, which cite their sources. The two records differ on 23 of 25 fields recorded for both. No ranking or recommendation: follow the links to read each fact in context.

MediaBeacon

Esko (MediaBeacon product line) · Belgium (Esko HQ, Ghent); MediaBeacon originated in Minneapolis, MN (USA)
Overview verified 2026-10-01 · API page verified 2026-10-01

Pimcore (Digital Asset Management)

Pimcore GmbH · Salzburg, Austria
Overview verified 2026-10-29 · API page verified 2026-10-29

Key differences

Fields recorded for both whose values differ · 23 of 25
Fields where MediaBeacon and Pimcore have different recorded values
FieldMediaBeaconPimcore
VendorEsko (MediaBeacon product line)Pimcore GmbH
HQBelgium (Esko HQ, Ghent); MediaBeacon originated in Minneapolis, MN (USA)Austria (Salzburg)
Founded19892013
Ownershipsubsidiary of Esko, part of Veralto (NYSE VLTO) since 2023-09-30independent (venture-backed; Series B led by Nordwind Growth, 2022)
Target marketEnterpriseMid-market, enterprise
DeploymentSaaS, On-premiseOn-premise, Private cloud, PaaS
Pricing modelquote-only (vendor cloud subscription or on-premise licence)annual subscription per edition (no per-user fees); Community free below EUR/USD 5M revenue; PaaS tiers
Public pricingNoYes
SSOSAML, LDAPOIDC
Analyst coverageForrester Wave DAM for CX Q2 2018: Strong PerformerGartner MQ PIM 2026: Visionary (vendor-reported) · Gartner MQ MDM 2026: Niche Player · Gartner MQ DXP 2025: included (placement not stated) · Gartner Peer Insights VoC DXP 2024: Customers' Choice
API style (overview)RESTREST, GraphQL, webdav
OpenAPI specNoPartial
Webhooks (overview)NoYesDatahub Webhooks, Enterprise edition only
Official MCP serverNoYesself-hosted, experimental: Datahub Simple REST MCP endpoint (Enterprise) and Pimcore Agent MCP tool groups
API base URLhttps://{tenant}/wf/restapi/v2/{endpoint}https://{host}/pimcore-graphql-webservices/{config} · https://{host}/pimcore-studio/api
API stylesRESTREST, GraphQL, WebDAV
AuthenticationAPI key, Basic auth, Session loginAPI key, Session login, OAuth 2.0 PKCE, Personal token
Token lifetimeAPI keys permanent by default; expiring keys can be created from workflowsOAuth 2.1 (experimental): access 1 h, refresh 30 days (defaults); API keys static
Rate limitNot publicStudio API 500 req/min per IP, MCP 3,000/min (defaults, configurable); Datahub: none documented
Paginationpage index (pageIndex + pageSize, default 100) on search endpointsGraphQL first/after offset; Studio page/pageSize; Simple REST page_cursor (search_after)
Webhooks (API)none; server-side workflow triggers on asset events insteadDatahub Webhooks (Enterprise): UI-configured, custom headers, no signature, one attempt
API specnone public (JSDoc / Javadoc HTML reference only)OpenAPI 3.1 for Studio API on GitHub (POCL, not archived); GraphQL schema per endpoint
Official SDKsnone official; server-side Workflow JS API and browser Client JS APInone official (PHP API in-process; Studio UI SDK for plugins)

Same recorded value: Hosting regions, Certifications.

All fields side by side

From overview.md and api.md frontmatter · “—” = not recorded yet
MediaBeacon and Pimcore: all comparison fields
FieldMediaBeaconPimcore
Company
Vendor (values differ)Esko (MediaBeacon product line)Pimcore GmbH
HQ (values differ)Belgium (Esko HQ, Ghent); MediaBeacon originated in Minneapolis, MN (USA)Austria (Salzburg)
Founded (values differ)19892013
Ownership (values differ)subsidiary of Esko, part of Veralto (NYSE VLTO) since 2023-09-30independent (venture-backed; Series B led by Nordwind Growth, 2022)
Product
Target market (values differ)EnterpriseMid-market, enterprise
Deployment (values differ)SaaS, On-premiseOn-premise, Private cloud, PaaS
Hosting regionsNot publicNot public
Pricing model (values differ)quote-only (vendor cloud subscription or on-premise licence)annual subscription per edition (no per-user fees); Community free below EUR/USD 5M revenue; PaaS tiers
Public pricing (values differ)NoYes
SSO (values differ)SAML, LDAPOIDC
CertificationsNone publishedNone published
Analyst coverage (values differ)Forrester Wave DAM for CX Q2 2018: Strong PerformerGartner MQ PIM 2026: Visionary (vendor-reported) · Gartner MQ MDM 2026: Niche Player · Gartner MQ DXP 2025: included (placement not stated) · Gartner Peer Insights VoC DXP 2024: Customers' Choice
Integration
API style (overview) (values differ)RESTREST, GraphQL, webdav
OpenAPI spec (values differ)NoPartial
Webhooks (overview) (values differ)NoYesDatahub Webhooks, Enterprise edition only
Official MCP server (values differ)NoYesself-hosted, experimental: Datahub Simple REST MCP endpoint (Enterprise) and Pimcore Agent MCP tool groups
API
API base URL (values differ)https://{tenant}/wf/restapi/v2/{endpoint}https://{host}/pimcore-graphql-webservices/{config} · https://{host}/pimcore-studio/api
API styles (values differ)RESTREST, GraphQL, WebDAV
Authentication (values differ)API key, Basic auth, Session loginAPI key, Session login, OAuth 2.0 PKCE, Personal token
Token lifetime (values differ)API keys permanent by default; expiring keys can be created from workflowsOAuth 2.1 (experimental): access 1 h, refresh 30 days (defaults); API keys static
Rate limit (values differ)Not publicStudio API 500 req/min per IP, MCP 3,000/min (defaults, configurable); Datahub: none documented
Pagination (values differ)page index (pageIndex + pageSize, default 100) on search endpointsGraphQL first/after offset; Studio page/pageSize; Simple REST page_cursor (search_after)
Webhooks (API) (values differ)none; server-side workflow triggers on asset events insteadDatahub Webhooks (Enterprise): UI-configured, custom headers, no signature, one attempt
API spec (values differ)none public (JSDoc / Javadoc HTML reference only)OpenAPI 3.1 for Studio API on GitHub (POCL, not archived); GraphQL schema per endpoint
Official SDKs (values differ)none official; server-side Workflow JS API and browser Client JS APInone official (PHP API in-process; Studio UI SDK for plugins)

Sources

Company, product and integration fields come from each overview, where every fact carries its citation. API fields are backed by these sources:

MediaBeacon:S1S2S3S4S5All MediaBeacon sources →

Pimcore:S56S57S58S59S60S62S63S64S67S69S70S71S73S74S76S77S90All Pimcore sources →

Search the wiki