New Tiers availableMore feature, Up to 10 Million AI-Tokens for free
Read blog postImage rights management
Free for 14 days or 100 files — no credit cardImage rights that travel with the file
Upload once. Fairu attaches the copyright holder, the license and the expiry date to the file itself, delivers it through a European CDN, and stops serving it the moment the rights run out — your fallback image goes out instead of a broken one.
With Fairu, we stopped wasting time on tedious image prep — no more manual resizing, cropping, or format juggling. It just works. Our team can finally focus on content, not logistics — and everything loads faster, too.
Mag. Miriam Kummer & Mag. Sabrina Klatzer
Co-Managing Director & Managing Director / Marble House GmbH
The stakes
The image is still live. The license is not.
Nobody is watching on the day a usage right ends. The photo stays in the article, the article stays in the archive, and the letter arrives eighteen months later.
01 / 03
The same photo sits in forty articles
Editors copy assets between systems, entries and campaigns. When one of them has to come down, nobody can say where the other copies ended up.
One block covers every copy
02 / 03
Licenses expire quietly
A usage right ends on a date in a spreadsheet nobody opens, and the file keeps being delivered until somebody outside the company notices.
Expiry enforced at delivery
03 / 03
A takedown needs an answer today
A rights holder writes. You have to find the file, show where it came from, and get it off every page it appears on before the deadline runs out.
Audit log and DMCA workflow
Every answer lands at the delivery edge
Fairu sits between your CMS and your readers. The rights live on the file, and the URL that serves it is where they are enforced — so nothing inside the CMS has to change.
Rights that still hold after publication
The part of asset management nobody demos: what happens to an image eighteen months after somebody dropped it into a folder.
- Rights travel with the bytes
- Block one file and every byte-identical copy in your account is blocked with it. Upload the same bytes again months later and the new file inherits the same rights.
- Licenses that expire on their own
- Give a license a start and an end. Fairu stops delivery on the end date, hands over to the successor license if you defined one, and mails the account owners a set number of days before that end date.
- A fallback image, not a hole in the page
- A blocked asset does not leave a broken image behind. The fallback you configured is served in its place, so the live page keeps working while you sort the rights out.
- AI provenance that survives delivery
- Fairu reads C2PA and IPTC provenance on upload, lets you mark older files by hand, and stamps a machine-readable AI marker into every rendered image — the labeling the EU AI Act asks for.
- Takedowns that close themselves
- Record a DMCA notice and Fairu tracks it. Still unanswered after 30 days, the file is blocked automatically — and every step stays in the file and account audit log.
And the fastest way to serve the same file
The URL that enforces the rights is the same one that resizes, crops and compresses — delivered from a European CDN.
- One URL per file, served from Europe
- Every upload gets its delivery URL straight away — cached at the edge, purged automatically the moment you replace the file.
- Resize, crop and convert in the URL
- Width, height, format and focal point are query parameters — for images, video, PDFs and vector files like EPS.
- Smaller files, same picture
- Automatic compression and WebP output, plus HLS streaming for video that has to play on a phone on a train.
- AI fills in what the upload left out
- IPTC extraction, alt texts, descriptions, tags and copyright detection — so the rights record is written at upload time, not at audit time.
- See every feature
- Unsplash import, galleries, RAKU S3 storage, workflows and more.
Four sides of the same file
Rights control, delivery, AI metadata and the API all read from one asset record — change it once and every screen agrees.
Rights enforced where the file is served
Manage usage rights at file, folder and delivery level. Fairu applies licenses, enforces restrictions and handles expiries without a spreadsheet. Need an asset gone? One click blocks every byte-identical copy in your account, and the fallback image you configured takes its place at the delivery edge.
Case studies
Eight Austrian titles, one asset platform
News, TV listings, food, motoring and lifestyle titles — each with its own CMS, its own archive and its own rights holders. Publishers running Fairu report up to 66% fewer bytes going out to the same readers.
Getting started
Live on three articles this afternoon
You do not migrate the archive first. You point a single template at Fairu and watch what happens to it.
01 / 03
Bring in one folder
Drag a folder in, or connect FTP, SFTP, S3 or a plain URL and let Fairu pull from it. IPTC data and existing copyright notices come along.
Files in the library
02 / 03
Attach the rights
Assign the copyright holder and a license with a start, an end and a successor. Set the fallback image once, for the whole account.
Rights on the file
03 / 03
Change one image URL
Swap the src in one template for the Fairu URL. REST, federated GraphQL, S3-compatible RAKU or the Statamic addon — whatever your stack already speaks.
Fairu URL live
The trial runs 14 days and covers 100 files, 5 disks, 0.5 GiB of delivered traffic and 5,000 AI tokens — enough to put one real template in front of real traffic, not enough to move an archive. Talk to us before you move the archive.
From the blog
Notes on rights, delivery and the boring parts
Core Web Vitals Are an Image Problem – And How Fairu Solves It
Release 1.109 - Now supports google + github login
Next step
Put one template behind Fairu this week
Twenty minutes with someone who has moved a publisher archive before — or a trial account in the time it took to read this page.
Plans and pricing
Pricing that grows with you
Every plan carries the full rights, delivery and API feature set. What changes is how much storage, traffic and how many disks come with it.
Start up
5.99EUR
Included
- 2 GiB storage
- 10 GiB outbound traffic
- 1,500,000 API read operations
- 10,000 API write operations
- 150 workflow runs
- 1,000 webhook deliveries
Extras
- €0.25 GiB per month* (storage)
- €0.25 GiB per month* (traffic)
- €1.00 per 100.000 tokens**
- €0.00016 per 1.000 API read operations
- €0.00016 per 1.000 API write operations
- €0.0015 per workflow runs
- €0.0002 per webhook deliveries
Popular
Pro
59.99EUR
Included
- 150 GiB storage
- 150 GiB outbound traffic
- 10,000,000 AI-Tokens
- 50,000,000 API read operations
- 500,000 API write operations
- 15,000 workflow runs
- 100,000 webhook deliveries
Extras
- €0.08 GiB per month* (storage)
- €0.06 GiB per month* (traffic)
- €1.00 per 100.000 tokens**
- €0.00012 per 1.000 API read operations
- €0.00013 per 1.000 API write operations
- €0.0012 per workflow runs
- €0.00015 per webhook deliveries
Business
259.99EUR
Included
- 1000 GiB storage
- 4000 GiB outbound traffic
- 10,000,000 AI-Tokens
- 500,000,000 API read operations
- 5,000,000 API write operations
- 100,000 workflow runs
- 1,000,000 webhook deliveries
Extras
- €0.06 GiB per month* (storage)
- €0.02 GiB per month* (traffic)
- €1.00 per 100.000 tokens**
- €0.00008 per 1.000 API read operations
- €0.00008 per 1.000 API write operations
- €0.001 per workflow runs
- €0.0001 per webhook deliveries
If you are on trial - your trial will automatically expire after 14 days, 100 files, 5 disks, 0.5 GiB of generated traffic or 5,000 AI tokens, whichever comes first. Please be aware the terms and conditions apply for any subscription. By activate a subscription you will terminate your trial immediately. Terms and Condition.
* The calculation of the used data volume is based on each commenced gigabyte (GiB) per month.
** The calculation of the used tokens volume is the sum of the token used (eg. for AI functions) during the period.