Lolly can extend a digital asset management system into governed content production. Customers keep the DAM as their source of record and use Lolly tools to make permitted variants from the assets exposed to them. Lolly Work adds organisation-controlled access, shared projects, review and delivery.
For a DAM vendor or implementation partner, the opportunity is to help customers use their approved library in more of their everyday production work. Content sovereignty describes the customer's continuing control over that arrangement, including the choice to retain or change systems.
A joint customer workflow
A designer creates an event-card layout and chooses which fields other people may change. The DAM administrator curates the source imagery and logos. A marketer selects an exposed asset, enters the event details and makes the required variants. A configured delivery can then submit the exact finished file for approval before sending to an organisation destination.
The template's constraints, source access, use rights and output approval need their own checks. The worked production sequence explains how to evaluate those checks together.
Agree responsibilities before connecting
| Responsibility | What a joint implementation should establish |
|---|---|
| Source authority | Which DAM records and files are authoritative, with supported approval and availability mappings |
| Member access | The audience exposed through a shared source credential, tested across listings, previews and originals |
| Production rules | Who maintains the design system, templates and editable inputs |
| Review | Who approves source use, catalog admission and finished delivery, without treating those as one decision |
| Writes and retries | Supported destinations, separate write credentials and reconciliation after an uncertain result |
| Operations | Hosting, support ownership, release compatibility, refresh expectations and recovery |
| Portability | What the customer can keep or move, with source licences and missing history made explicit |
What can be offered today?
Lolly and Lolly Work are open source under MPL-2.0. A partner can evaluate and operate them with a customer's design system and supported catalog sources. Hosting, integration work, maintenance and support still need an agreed owner and budget.
The provider directory lists implemented sources and open live checks. Supported sources are normally read-only; organisation delivery has separate adapters. A provider entry is not a certification or an announced commercial partnership. Brandfolder has successful use reported at SUSE, documented in the deployment account; that evidence does not qualify unrelated tenants or operations.
Evaluate one recurring task
Choose a real customer task and a small permitted asset set. Agree how success will be observed before starting: for example, whether a marketer can produce the required variants without a manual file handoff, and whether an administrator can withdraw further access.
Run the source qualification checks, demonstrate the complete workflow and record unresolved limitations. Measure approved-asset reuse, completed outputs, correction work and administrator effort only where the deployment's privacy and telemetry choices permit those measurements. Compare against the customer's existing process.
Does the customer have to stay with the DAM?
The customer chooses. The integration can remain in place, and supported migration paths are available when the customer decides to move. Portability remains part of the product's purpose. It should be discussed openly in the integration agreement, with no assumption that read access grants permission to copy or redistribute every source.
Start with Use Lolly with your existing DAM. For technical evaluation, continue to Work architecture and What Lolly Work does today.