Photos, video and delivery · Your Own Storage
Your company registers its own storage account (Amazon S3, Cloudflare R2, Backblaze B2, Wasabi, DigitalOcean Spaces or any other compatible provider) and chooses, gallery by gallery, where the photos live. Galleries on that storage pay Partiu nothing per GB: they pay only for the facial recognition used, per processed photo, per search and for faces stored each month. With no choice made, the gallery stays on Partiu storage, as always.
The problem and the fix
If any of these situations sounds familiar, it is because they happen in almost every graduation company, until the right system comes in.
The company already pays for cloud storage and then pays per GB for the photos again on the platform.
Galleries stored in the company's account pay Partiu nothing per GB. Storage and traffic are paid directly to the provider you already use.
Moving everything at once is too risky to test.
The choice is per gallery: each new gallery chooses where to store its photos, and existing ones change only if you want. Photos already uploaded don't move.
A wrong key only shows up when photos stop opening in the app.
Before activation, the test writes, opens and deletes a real file, from the server and from the browser. Only then does the storage become available to galleries.
Without platform storage, facial recognition becomes a hard bill to predict.
The pricing table shows the cost per processed photo, per selfie search and per thousand faces stored each month, and the dashboard estimates usage over the last 30 days.
Nobody knows who changed the storage settings or when.
The history logs when, what and who for every change, and an alert email notifies the team when something fails.
In practice
Everyday situations at graduation companies, from the problem to the result, using the modules on this page.
A company with its own storage contract wanted to stop paying twice per GB for its ball galleries.
They registered the account, tested it, activated it and set it as the default. New ball galleries started out with that storage already selected.
New photos went to the company's account, Partiu's charges on those galleries became facial recognition only, and the rest of the archive stayed as it was.
The company wanted to keep one branch's galleries in a separate account.
They registered two active storages and, on each one's screen, chose which galleries live there.
Each gallery stayed in a single storage, and the dashboard showed how many galleries and photos are outside Partiu.
The company had to change plans with its provider and wanted to stop sending photos there for a few days.
They paused the storage: new photos from its galleries went back to Partiu, and those already in the account kept opening from there.
No photo stopped opening for graduates during the switch, because the key remained valid.
How it works
Every step is a real module, and what comes out of one goes into the next without anyone typing it again.
Module by module
8 modules and 42 features on this page, all running on the same class, graduate and event records.
The account your company already has or prefers.
Account details kept secure.
Proof that the account works before it receives a photo.
Each gallery in its place, no mass changes.
Control without breaking the archive.
A snapshot of what's outside Partiu.
No GB at Partiu, only the facial recognition you use.
Everything agreed before activation.
Compare the modules and choose the setup that fits your operation.