Apivom Blob — object storage that keeps every customer’s files apart
Blob is the object storage layer behind the Apivom products. Quotes, invoices, attachments and exports are kept in separate areas, one storage space per organisation, and shared through time-limited links. Blob is included with the products and is not sold separately.
Infrastructure layerFiles with a clear home
Documents, attachments and exports stop living in scattered places. Each kind of file has its own area inside the organisation’s own storage space.
A storage space per organisation
In Iris, every customer organisation gets its own storage space, created automatically when it is first needed. Files of one organisation are not mixed with another’s.
10 content areas
Documents, quote documents, exports, support attachments, mailboxes, mail images, feedback files, invoices and credit notes, quote templates and company files each have their own area.
Time-limited download links
A download link works for a short time, covers only one folder and always downloads the file instead of opening it in the browser.
Shared branding area
Organisation logos and icons live in a shared area that the application only reads, writes and deletes in. It never creates storage spaces on its own.
Used across the products
Iris, Halo, Mars and the apivom.com website all keep files in Blob, as do Staff and Odin for their archives and backups.
Watched like the rest of the platform
Blob reports its own metrics, has a health check, and has a dashboard of its own, so the team sees problems early.
How the Apivom products use Blob
You do not set Blob up on its own. It is where the products keep the files they create or receive. Here is what lives in it today.
- Iris. Documents, quote documents, invoices and credit notes, support and mailbox attachments, exports, feedback files and organisation branding. Autodesk export files are staged here too.
- Halo. Scanned WhatsApp media, a quarantine area for files that are not yet cleared, data-export downloads, a locked area for erasure requests and generated images and video.
- Mars and apivom.com. Mars stores the media it renders for posts and videos. The apivom.com website serves its blog and page images from Blob.
- Staff and Odin. Staff archives workflow history in Blob, and Odin copies its backups there.
Each organisation’s files in a space of their own
Blob keeps files apart by organisation and by purpose, and hands them out only through links that expire. The result is a file store that is easy to reason about.
- One space per organisation. Each customer organisation has its own storage space in Iris.
- Areas by purpose. Quotes, invoices, support files and mailbox attachments do not share a folder.
- Links that expire. Downloads are shared through short-lived links limited to one folder.
Frequently asked questions
What is Apivom Blob?
Blob is object storage for documents and files. Each customer organisation gets its own storage space, content is split into separate areas such as quotes, invoices, exports and attachments, and downloads are shared through time-limited links. The Apivom products use it to keep the files they create or receive.
Is Blob sold separately?
No. Blob is an infrastructure layer that is included with the Apivom products. You do not buy or set it up on its own. If you want to know how it supports your use of Iris, Halo or Mars, talk to us.
How are files kept apart between customers?
In Iris, every customer organisation has its own storage space, created automatically when it is first needed. Inside it, files are split into 10 content areas, so quote documents, invoices, support files and mailbox attachments are not mixed together.
How are downloads shared?
Through time-limited links. A link works for a short time, is limited to one folder and always downloads the file instead of opening it in the browser. When the time is up, the link stops working and a new one has to be issued.
Which Apivom products store files in Blob?
Iris keeps documents, quotes, invoices, attachments, exports and branding there. Halo keeps media, exports and generated images and video. Mars stores rendered media, and apivom.com serves its blog and page images from it. Staff archives workflow history and Odin copies its backups to Blob.
How is Blob monitored?
Blob exposes metrics that Otto collects, has a health check, and has its own dashboard in Ping. That is how the team notices problems with the file layer early, as it does for the other parts of the platform.
Files that stay where they belong
Blob comes with the Apivom products. Talk to us about the documents and files you want to keep in order.