GalaciaAn extra integration
Vault is another component in your Salesforce org and another connection to maintain. If Salesforce Files already does what you need, changing may not be worth it.
Why Galacia
Your files stay yours. The setup is done with you.
Two decisions shape Galacia Vault. File contents live in cloud storage your organisation owns, and Galacia installs and tests the product with you. Here’s what each one gives you and what it asks of you.
Customer-owned storage
The files behind your Salesforce records sit in a bucket that belongs to your organisation.
- File contents use an Amazon S3 bucket under your own provider account.
- You agree the region, access, retention and provider charges before onboarding.
- Salesforce keeps the file metadata and the link to the record.
- Your own people manage the storage settings your policies care about.
Assisted setup
Galacia does the installation with you, so the first working version is one that has been tested in your org.
- Galacia handles installation, API connections, bucket configuration and testing.
- Allow up to one working day once access and the agreed setup are ready.
- You get a handover recording the installed version and configuration.
- There’s no self-service installer and no AppExchange listing. Installation is always done with Galacia.
How a file moves
From the record page to your bucket.
This is the standard S3 path. A separately configured transfer gateway is a different path and needs its own assessment.
- Salesforce record page
Someone uploads or opens a file
They use the Vault component on the record they’re already working on.
- Vault in Salesforce
Access is checked
Salesforce code checks the file operation and the storage connection. The file’s metadata and its link to the record stay in Salesforce.
- Your S3 storage
Contents go to your bucket
File contents use the bucket and region you agreed. Your organisation owns the storage, its retention settings and its provider account.
The trade-offs
What you take on.
Owning the storage is a responsibility as well as a benefit. These are the costs to weigh.
Storage to look after
Owning the bucket means owning its settings: region, credentials, retention and the bill from your provider.
Recovery is still your plan
Storage ownership isn’t a backup. Agree who backs up file contents and Salesforce metadata, and who tests a restore.
File size limits
The standard upload path takes 1.5 MB per file. Larger files need separate qualification.
How it goes
Demo, written offer, assisted installation.
The same three steps for every customer.
See it in a demo
James shows uploading and opening files on a Salesforce record page. Bring a typical record, your user roles and a few non-sensitive files.
Agree a written offer
Storage, downloads, support and any migration are scoped in writing, with the price. You pay through Stripe once you’ve agreed it.
Galacia installs it
Galacia handles installation, API connections, bucket configuration and testing, then hands over a record of what was set up.
Plain facts
A small supplier, stated plainly
Galacia is operated by James Collard. He gives the demo, installs Vault and handles support during published UK support hours, with a 30-minute first-response target. There’s currently no backup cover.
That suits teams who want to speak to the person who built the product. If you need a supplier with certifications, a supplier portal or round-the-clock cover, say so early. This site doesn’t claim them. The enterprise buying guide lists what to settle in writing.
See Vault on a Salesforce record page.
Book a demo, bring a typical record and a few non-sensitive files, and decide from there.