_Last checked: August 2026._
Lolly is not a replacement for a brand portal like Bynder, Frontify, Marq or Brandfolder, though it does what most people need one for: handing someone who is not a designer a locked template and getting an on-brand file back.
Where they overlap
Both give a non-designer a template that bends only where it is allowed to bend, and both keep the approved brand assets somewhere a whole team can reach them. What differs is where the template lives and who meters it.
What brand portals do better today
Governed org-wide asset storage, approval workflows, rights management, versioning and usage analytics, with the administration around them: Marq publishes a Team tier at $12 per user per month, gates advanced template locking to Team and API, then puts SSO and SCIM on Enterprise. Lolly has none of that. An organisation that needs a reviewed, rights-managed library with reporting on who used what should buy one.
What Lolly does instead
The templating and the locking are the engine itself, free, with no per-seat meter and no procurement round. Most portals are quote-priced: 2026 procurement data puts Bynder's enterprise average near $124,700 a year with typical yearly escalation of 22 to 23 percent, Frontify's median contract near $32,400 on active-user pricing and Brandfolder's near $24,700. Lolly's tools and brand assets are files you hold in version control rather than records in a vendor database. The render happens on your own device.
The two sit together well: the portal holds the library and the approvals, Lolly makes the files. This page describes a category rather than one product, and the vendors named are examples quoted from their published facts. See How Lolly compares for the capability-by-capability picture and Lolly compared, tool by tool for the rest of this set.