Lolly
Отвори приложението

The trade we never agreed to

signed by Lollystatus-quo.htmlHTMLpixels, not shapes9 KBAI generatedgenerated by GeminiПровери самВземи подписания файл

Nobody sat us down and offered us the deal. It arrived one tool at a time, each step reasonable on its own, until the normal way to resize an image was to send it to a company none of us have met.

This is not a story about villains. Most of it was built by people making sensible decisions inside incentives that all pointed one way. The incentives are the problem.

We did this easily

  • We uploaded a logo to a free converter, waited through an ad and downloaded a file we hoped was the same picture.
  • We went back for artwork from eighteen months ago and found it behind a login for a plan the team had stopped paying for. The artwork was ours. The file was not reachable.
  • We accepted cookies we did not read, on a site we visited once, to do something that took eleven seconds.
  • We sent a near-final campaign to a colleague, who sent it onward, and the version everyone uses now is one nobody can point back to.
  • We clicked "not now" on the same upsell for a year.

The cost

  • Our content became the price. A tool that runs on someone else's server has to be paid for, so the bill arrives as a subscription, an ad, a data broker or a training corpus. The upload was never needed to resize a picture. Browsers have done that locally for years.
  • Our files became leverage. Work kept in a format only one program opens is leverage over the person who made it, and leverage that expires with a card is not a partnership.
  • Our consent became paperwork. Twelve toggles and a forty-page policy do not produce informed agreement. They produce legal cover, and one more task between us and the work.
  • Our proof went missing. For most of the last decade a file carried no reliable record of where it came from. You could live with that while making a convincing image still took a studio. You cannot now.

Living inside it gave the trade its textures. The quiet fear of picking the wrong colour or font for something that was meant to be simple. Every file stuck behind a busy queue, a slow tool or one more approval. An account before we could start, a subscription that outlived the job, pricing ladders built to hold our own work hostage.

The old way and the new way

Take the smallest job there is: a logo that needs resizing.

Two ways to resize a logo. The usual way uploads it to a server, where it rests on their disk under their retention rules. The bill arrives as ads, data or training, and you download a file you hope matches. Here, your device renders it and you have your file, with no second copy anywhere.Two ways to resize a logo. The usual way uploads it to a server, where it rests on their disk under their retention rules. The bill arrives as ads, data or training, and you download a file you hope matches. Here, your device renders it and you have your file, with no second copy anywhere.Open this in Diagram Builder

The same trade runs through everything else:

The usual wayHere
Upload, queue, sign in and dismiss the upsell, or else email a brief and wait days for one small graphicOpen a link and work. Fill in a few fields and the finished file is ready in seconds. See Make your first file
A subscription that outlives the job, the part you need locked behind an upgrade and a watermark you pay to removeFree, forever: a released version is licensed so it can never be taken back (How Lolly compares). What should change is yours to change; what should not is already handled (Constraints)
Files silently re-encoded and capped in resolution on the free tier, with a guess at the right font and colour that you hope passes reviewReal vector out, print-ready colour and the same render on every device. The design rules are built into the tool. They bend, not break
The same badge, card or banner re-made a hundred times by hand, then "which version is the latest?" hunted through chats and drivesPaste a spreadsheet and get a hundred finished, print-ready files at once (Using Lolly). The file is a link: same inputs, same file, every time (Reproducibility)
Pay the AI again for something it already made, and your work becomes training data or an ad profile by defaultIf AI helps make something once, the result is yours and re-making it is free (Our AI Stance). Nothing is collected, so nothing can be repurposed, and AI declares itself
A policy you have to believe, rewritable at any time without telling you, while the rules about your work change and you find out laterAn architecture you can check, a signed credential inside every export whose format can carry one, and the freedom to leave with everything at any time

Trust what you can verify

A promise is something a company can change on a Tuesday. An architecture is something you can check. Each row above rests on one:

What this is not

It is not a claim that everyone doing it the other way acts in bad faith. Server-side software is a legitimate way to build things, and plenty of it is made carefully by people who would rather not be collecting what they collect.

It is not a claim that Lolly does everything those tools do. It does a narrower set of things without the trade.

And it is not a request for your trust. Trust is the thing we are trying to make unnecessary. Everything above can be checked, the code is public and the Threat Model is honest about the limits.