Here's a question that quietly breaks most "suites": where does a photo live? If Photos and Drive each keep their own copy, you've doubled your storage and guaranteed they'll drift out of sync. PolarHQ takes a different route — one stored object, two views.
A photo is a Drive file
Every photo asset and every Drive file points at the same underlying stored object. Upload a picture in Photos and it appears in your Drive tree. Drop a file into a Drive folder and, if it's an image or video, Photos picks it up. There's exactly one set of encrypted bytes in object storage, referenced from both places.
Bidirectional sync, no duplication
The two apps stay consistent through shared node and asset records:
- Move a file in Drive and the photo's location follows.
- Trash it in Photos and it lands in the Drive trash — and vice versa.
- Rename, version, restore — all operate on the same node.
┌──────────────┐
Photos ─▶│ stored object │◀─ Drive
│ (ciphertext) │
└──────────────┘
one set of bytes, two front doors
Because the object is encrypted once with its own content key, both apps decrypt it the same way client-side. No re-encryption, no second copy, no reconciliation job trying to guess which version is canonical.
Why this matters
This isn't just an efficiency win. It's what makes the suite feel coherent instead of like a bundle of separate products. Your storage quota is one number. Your trash is one place. Your backup is one set of objects. And the mental model is the one you already have: your photos are part of your files, not a walled garden beside them.
The best architecture is the one you never have to think about. Files and photos are the same thing — so we made them the same thing.
It also sets up everything that comes next. Documents are Drive files too. So are spreadsheets and presentations. Once "everything is a node in one encrypted tree," sharing, versioning, and sync only have to be built once — and every app in the suite inherits them.