Ready for onboarding

Files on the Salesforce record. Stored in your own cloud.

Your team uploads, finds and downloads files in a component on the Salesforce record page. The file contents sit in an Amazon S3 bucket your organisation owns. Everfrost installs it, connects it and tests it with you.

Where people work
The Vault component on Salesforce record pages
Where files live
An Amazon S3 bucket your organisation owns
Who sets it up
Everfrost. Allow up to one working day once access and the agreed setup are ready.
Illustration with example names and dates. Each key is a base path, a random ID and the file name.

One upload, two places.

The file’s details stay on the Salesforce record. The contents go to storage you own.

  1. 1Salesforce record pageA user opens Vault on the record and asks to upload or download a file.
  2. 2Vault in SalesforceSalesforce code checks the file operation and the user’s connection access. File metadata and the record association stay in Salesforce.
  3. 3Your S3 storageFile contents use the agreed bucket and region. The standard connection uses a Salesforce Named Credential for storage access.
Illustration of the standard S3 path. Your agreed configuration is recorded at handover.

Five things Vault does today.

Each point describes the product’s behaviour in the standard assisted setup, with the control names your users will see.

Files stay with the record

People choose Upload files in the Vault component on the record they’re working on. Later they find the file in the same list and download it from its action menu.

  • Upload files
  • Browse Files
  • Download
  • Preview

The storage is yours

File contents go to an Amazon S3 bucket in your own account. Your team decides the region, retention and backups. Salesforce keeps the file metadata and the link to the record.

See what sits where

File access is its own check

Seeing a record doesn’t grant access to its Vault files. File sharing and storage-connection access are set up separately and tested with permitted and restricted users.

Setup is done for you

Everfrost installs Vault, connects the API and your bucket, adds the component to the agreed record pages and tests it with your users.

See the onboarding steps

You can plan your exit

The contents stay in your bucket. Agree the exit steps before rollout, including how file-to-record mappings are exported if you ever remove Vault.

See a file go from upload to preview.

Upload a text file from a Salesforce record, open its actions and preview its contents.

Screen recording of Everfrost Vault in a Salesforce Developer Edition org, with sample data. 18 seconds.
Read the walkthrough
  1. Open Upload files from the Vault component on a Salesforce record.
  2. Select a file to upload to the connected storage. A confirmation appears when the upload completes.
  3. Open the file actions and choose Preview to read the text file within Salesforce.

Download the video or book a personalised demo.

Know the size limit before the demo.

The standard upload path has a per-file limit. Bring your normal file sizes to the demo. Larger files and migration need separate qualification.

See current scope and file limits
Standard upload path
1.5 MBper file
Shown in the component as
1.4 MBapproximately, in binary units

The people who touch record files.

Four steps, in this order.

Nothing is installed and nothing is charged until you’ve agreed a written offer.

  1. See a demo

    Watch files uploaded and accessed from a Salesforce record, and talk through your users, storage and download needs.

  2. Agree a written offer

    Storage, downloads, support, any migration scope and the price are confirmed in writing.

  3. Pay through Stripe

    The payment link follows the agreed offer. The demo request never takes payment.

  4. Everfrost installs and tests

    Installation, API connections, bucket configuration and testing are handled for you. Allow up to one working day once access and the agreed setup are ready.

Short answers first.

The full FAQ covers storage, limits, buying and support.

Where are our files stored?

In your own Amazon S3 bucket, in the region you agree at setup. Salesforce holds the file metadata and the link to the record. See what sits where.

How big can a file be?

The standard upload path takes files up to 1.5 MB (1,500,000 bytes) each. Larger files need separate technical qualification and sit outside the standard assisted scope. Read the current scope.

Does access to a record give access to its files?

No. File sharing and storage-connection access are checked separately from Salesforce record access. They’re configured and tested during onboarding with both permitted and restricted users.

Can we install it ourselves?

Not today. There’s no self-service package installer, AppExchange listing or free trial. Everfrost installs Vault with you after a demo and a written agreement, and handles the API connections, bucket configuration and testing. See how onboarding works.

How long does onboarding take?

Allow up to one working day once access and the agreed setup are ready. Confirm timing with Everfrost before you plan a rollout.

What happens if we stop using Vault?

The file contents stay in your bucket. The file-to-record mappings live in Salesforce, so preserve them and check your team can retrieve the files it needs before removing the integration. Bucket access alone doesn’t rebuild those relationships. Agree the exit steps in your handover.

Book a demo.

See files uploaded and accessed from a Salesforce record. James will contact you to arrange a time.

Watch the administrator demonstration

No account or payment needed. This request does not book a meeting slot.

Work email, company and role are required. Everything else is optional.

An estimate is fine, for example 100 GB.

Include expected file volumes or downloads if you know them.

Everfrost stores these details and sends a notification to its owner through Discord to respond to your enquiry and discuss an offer. Campaign tags in this page’s link may be included. Please avoid confidential files and credentials. Demo request privacy notice.

From demo to onboarding
  1. See your workflowDiscuss your Salesforce records, users and storage needs using non-sensitive examples.
  2. Agree a written offerConfirm storage, downloads, support, any migration scope and price before paying through Stripe.
  3. Configure and testEverfrost handles installation, API connections, bucket configuration and testing. Allow up to one working day once access and the agreed setup are ready; confirm timing before rollout.

Read the onboarding checklist, including test-environment and handover requirements.

Future integrations and structured data storage are not available. Migration interest starts a scope discussion; it does not confirm a migration service.

Prefer email, or following up on a request? Contact hello@galacia.app. No response-time guarantee is made by this form.