Keepeek vs Wedia: which DAM fits which team

Verdict

DAMSelection assessment: Keepeek leads on Akeneo depth, commerce connectors and release cadence, and Wedia leads on certification, tenancy and enterprise PIM reach. Both changed ownership in 2023 or 2024, so both need change-of-control clauses. See the Keepeek profile, the Wedia profile and the vendor directory.

Choose Keepeek when:

• Your PIM is Akeneo, where Keepeek publishes its own app with two-way metadata sync, rated level 4 in the Fit Map.
• Your commerce stack runs on commercetools, BigCommerce or Adobe Commerce, or you syndicate to GS1 GDSN through AGENA3000.
• Your marketing team wants DAM, brand portal and template-based content creation from one supplier.
• Your organisation prefers hosting in France, which Keepeek states for its private cloud.

Choose Wedia when:

• Your security review requires ISO 27001 or TISAX, both stated by Wedia.
• Your IT policy asks for single-tenant, container-based SaaS with data kept inside the EU.
• Your PIM is Stibo STEP, where Wedia builds the connector, or inriver, Contentserv or Pimcore, which its directory lists.
• Your identity team needs Okta, Microsoft Entra ID or another of six listed SSO options.

Where Keepeek and Wedia differ

Keepeek and Wedia differ in tenancy, product scope and connector catalogue. The template's facts table covers ownership, hosting and certifications, so this table adds the rest.

Product content and PIM integration

Keepeek holds a level 4 Fit Map connector for Akeneo, and Wedia holds a level 4 Fit Map connector for Stibo STEP and a level 3 cell for inriver. Level 4 means the DAM or PIM vendor builds and maintains the connector.

• Keepeek publishes the Keepeek DAM App for Akeneo PIM, with an asset picker and two-way metadata sync. The Akeneo App Store labels it Beta and lists no price.
• Keepeek's integrations catalogue also lists Contentserv and Centric Software PLM.
• Wedia builds its Stibo STEP connector, listed in the Stibo Connectivity Gallery, and a Wedia licence is required.
• Wedia's directory lists six PIM integrations without naming the builder or sync direction. The Fit Map rates the inriver listing level 3 for that reason.
• DAMSelection could not verify an Akeneo connector for Wedia, because the Wedia integration directory lists none.

DAMSelection assessment: match the vendor to your PIM first, because each vendor has one verified vendor-built connector. Check depth in the PIM and DAM Fit Map and read the Akeneo integration guide or the Stibo STEP integration guide.

Hosting and security differences

Wedia documents EU-only hosting and two certifications, and Keepeek documents French hosting with no certification for its own platform. Both host in Europe.

• Keepeek states that the platform runs on a French private cloud with redundant physical architecture, clustered applications and a daily full backup.
• Keepeek's large-file storage space uses Microsoft Azure storage, and the Azure pages name no region.
• Keepeek names no security certification for its own platform. The only ISO 27001 reference found dates from 2018 and covers its hosting provider at the time, Claranet.
• Wedia hosts SaaS data on AWS and Azure in several EU countries, with no transfer of data outside the EU.
• Wedia states ISO 27001 and TISAX certification, without publishing certificate scope.

DAMSelection assessment: ask Keepeek to name its hosting provider and data centres, and ask Wedia to name the EU countries and certificate scope. The data residency entry defines the terms, and the security review guide lists the evidence to request.

Ownership and contract risk

Keepeek and Wedia both changed ownership recently, which affects roadmap and contract terms. Both events are facts from vendor or financial press sources.

• Papirfly Group, majority owned by Verdane, acquired Keepeek in May 2023. Papirfly stated a plan to integrate Papirfly features with the Keepeek DAM. Papirfly also sells its own brand platform, profiled at Papirfly.
• Cathay Capital Private Equity bought the controlling block of Wedia in 2024. Wedia left the stock market after a simplified tender offer in November 2024.
• Wedia now markets its DAM as Lyvio, so proposals and contracts may use either name.

DAMSelection assessment: write roadmap, data return and change-of-control terms into either contract with the contract clauses guide.

Pricing model differences

Keepeek and Wedia both quote on request and publish no prices. Keepeek documents more about contract shape.

• Keepeek prices by the solutions chosen, DAM, templates or both, and by company size.
• Keepeek contracts typically start with a 12-month term.
• Keepeek sells facial recognition and media quality control as optional add-on modules.
• Wedia states that its core offer includes automatic translation, advanced statistics, validation workflows, customer success and a dedicated account manager.

DAMSelection assessment: storage, egress and AI credit consumption drive five-year DAM cost more than licence fees. Ask both vendors for storage tiers, CDN traffic terms and AI usage limits. Model both quotes in the TCO calculator.

AI capabilities documented for each

Keepeek documents three shipped AI features, and Wedia documents one, built on Anthropic's Claude. Neither facts file records announced AI features.

Keepeek

• Shipped: AI auto-tagging that describes objects, places and emotions and generates tags at import.
• Shipped as an add-on: media quality control that checks resolution, framing and file size and blocks non-compliant media.
• Shipped as an add-on: facial recognition that tags people in photos to support consent management under GDPR.

Wedia

• Shipped: AI captioning and automatic metadata tagging, introduced in 2024 and built on Anthropic's Claude.
• Listed integrations: AWS Rekognition, Google Gemini, Anthropic Claude, DeepL and Azure Translation.

What to test to separate them in a scripted demo

A Keepeek and Wedia demo should prove hosting, PIM sync and AI on your own assets. Use the DAM demo script and run these scenarios.

1. Show the infrastructure diagram and name the data centres for primary data, backups and AI processing.
2. Link 50 images to SKUs in your PIM, change one image in the DAM and show the update in the PIM.
3. Change a metadata field in the PIM and show whether it writes back to the DAM.
4. Auto-tag 200 of your images and show the review step and tag accuracy.
5. Set up SSO with your identity provider and show role mapping for an agency user.
6. Produce one localised campaign asset from a template and show the approval steps.