Skip to main content

Cloud infrastructure integrations

Send selected Seal records and exports to cloud storage and data platforms through configured transfers set up with Seal’s API and Scripts.

Illustration of a seal beside a laptop showing a data table and an evidence binder linked by a red thread.

What these systems hold.

Cloud storage and data platforms hold copies: exported records, reports and files kept for analysis, sharing or long-term retention.

Retained data has to stay usable for its whole retention period. EU GMP Annex 11 asks that stored data be checked for accessibility, readability and accuracy, that back-ups can be restored, and that archived data be checked for accessibility, readability and integrity (Annex 11, sections 7 and 17). A copy in a bucket meets that only when you can show what it is a copy of.

What Seal reads and writes back.

Every connection here is set up with Seal’s API and Scripts, typically a Script that runs after a Seal event or on a schedule. To AWS, Azure and Snowflake, Seal sends selected records and reports. With Dropbox and Google Cloud Storage, files can move both ways. Which copy is the record, and how changed, duplicate or failed transfers are handled, is agreed before anyone relies on the transfer.

Seal
  1. AWS, AzureSource of truth agreed when scoped

    Sends Selected Seal records and reports

  2. DropboxSource of truth agreed when scoped

    Reads Files in the folders in scope

    Writes back Files, to the folders in scope

  3. SnowflakeSource of truth agreed when scoped

    Sends Selected Seal records

  4. Google Cloud StorageSource of truth agreed when scoped

    Reads Files from the agreed buckets

    Writes back Seal exports, archived to the agreed buckets

5 connections

Blueprints that use these records.

Start with one source.

Tell us what Neil needs to do and where the records live. We’ll scope the connection with your team.

Book a demo