Papirfly DAM review: fit, pricing model and integrations

What Papirfly is

Papirfly is a SaaS suite that stores approved brand assets and lets local teams produce campaign material from controlled templates. The pricing page sells three offers: Digital Asset Management, Templated Content Creation and the Full Papirfly Suite, which adds campaign management and performance analytics.

The help centre describes the platform as a set of modules named Point, Place, Produce, Plan Campaigns, Plan Approval Projects, Prove and Plus. Place is the asset library, where AI tags and face recognition filters live. Produce covers templates. Users reach the suite through a web interface and REST APIs.

Papirfly is also a group. Papirfly Group owns Keepeek, Brandpad and the former Adgistics, and its January 2026 release describes a move to a unified product suite.

Where Papirfly fits

Papirfly fits organisations where a central brand team must keep many local producers on-brand. DAMSelection places Papirfly in the brand and marketing DAM segment, and the vendor's own positioning names automotive, banking, pharma and retail networks.

DAMSelection assessment: Papirfly suits a buyer profile with these conditions.

• A central brand team serves 20 or more local markets, dealers or branches.
• Local staff need print, social and video output without design skills.
• The organisation wants templates, assets and campaign plans under one contract.
• EU hosting is a requirement.

DAMSelection assessment: another segment fits better in three cases. A buyer whose main job is packaging artwork or product imagery for e-commerce should look at product content platforms. A buyer with a large multi-brand content operation and heavy integration needs should compare enterprise content platforms. A French-speaking buyer focused on library depth should also read the Keepeek profile, since Keepeek belongs to the same group.

How Papirfly covers the core DAM jobs

Papirfly documents capabilities across all four core DAM jobs, with the most detail on rights and consent. The table maps each job to what Papirfly publishes.

AI Facial Recognition is documented in the help centre. It detects, groups and names faces on upload or across existing assets. Papirfly enables it on request through the Customer Success Manager, for images up to 15 MB and up to 100 faces per image.

Papirfly's AI page also presents conversational search, AI localisation, a duplication manager and image quality control. DAMSelection found no help-centre documentation for those features, so the facts file lists them as announced.

Product content and PIM integration

Papirfly lists 13 PIM systems on its integrations page, including Akeneo, Contentserv, inRiver, Pimcore, Quable, Salsify GDSN and Stibo Systems. Papirfly states that each DAM integration is Papirfly or partner supported, depending on the customer's solution.

Two facts limit what a buyer can assume. The pricing page says connectors are scoped against the existing stack and priced after scoping. The only Akeneo App Store listing found is Akepeek, published by Keepeek and labelled Beta, with no Papirfly-branded listing.

DAMSelection assessment: ask which product, Papirfly or Keepeek, sits behind each PIM connector you need. Then check the connector against the PIM and DAM Fit Map, which records connector depth per PIM.

Hosting, security and contract checks

Papirfly runs on AWS in Sweden and documents daily backups with disaster recovery from another EU location. The privacy policy also lists Lan-x AS in Sandnes, Norway as an operating service provider.

Papirfly holds ISO 22301 for business continuity. A help article from March 2024 says ISO/IEC 27001 certification has started, and Papirfly's own evaluation page still reports it as in progress. Papirfly's SOC 2 references describe AWS audits, which cover infrastructure only.

Confirm these points in contract, using the security review guide as the checklist.

• The current ISO/IEC 27001 status and the certificate scope.
• The DPA and the full sub-processor list.
• The AWS region for primary data, backups and AI processing.
• The SSO set-up and how MFA is enforced through your identity provider.
• The roadmap for the module you buy, given the group integration programme.

What to test in a scripted demo

A Papirfly demo should prove the template, rights and integration claims on your own assets. Use the demo script method and give Papirfly these scenarios two weeks ahead.

1. Build a locked template for a local dealer flyer, then let a regional user edit only the permitted fields and export print and social versions.
2. Set a consent expiry on a photo with an identified person, then show the variant link stop serving the image on the expiry date.
3. Enable facial recognition on a test archive of 200 images and show grouping, naming and the permissions needed to edit face names.
4. Upload 50 images of mixed quality and show which upload checks flag resolution, lighting and off-brand elements, and which are add-ons.
5. Connect the PIM you run and show a product image appearing on the right product record, naming who built and supports the connector.
6. Configure a brand portal in Dutch, German and English with version-controlled asset access.
7. Show the audit trail of one asset through approval, publication and expiry.

Pricing questions to ask

Papirfly publishes no prices and builds a tailored proposal from the solutions chosen and the organisation size. Agreements typically start at 12 months.

Ask these questions before comparing quotes in the TCO calculator.

• What does each solution cost on its own: DAM, Templated Content Creation and the Full Suite.
• Which metric drives price growth: users, markets, storage or brands.
• What do the Image Variants, facial recognition and asset quality checker add-ons cost per year.
• What does each PIM, CMS or e-commerce connector cost to scope, build and maintain.
• Which price protections apply at renewal and for added markets.

Worked example: a buyer with 30 markets wants DAM, templates and two connectors. The quote then has at least five lines: two solutions, the add-ons in use and two connector scopes. Request each line priced separately.