Transfer General
Request a PoC

Your cross-cloud data transfer pipeline — live in minutes, not months.

Serverless transfer pipelines, deployed entirely inside your own cloud accounts. One deployment runs as many as you need, across any pair of clouds — recurring cross-cloud transfer, not a one-time migration.

Your cloud providers' tools work inside their own cloud. Nobody covers the boundary between them.

Run the numbers Watch the walkthrough
Verified & listed
Google Cloud Ready — Regulated & Sovereignty Solution
Google Cloud Partner
Carahsoft
FIPS 140-2Level 2 validated
Build vs. buy

What does building this yourself actually cost?

Most teams underestimate cross-cloud transfer because the hard parts are invisible until you're in them: a separate integration per cloud pair, object-layer encryption, KMS integration, FIPS validation, and the on-call tax every time a cloud API changes. Put in your own numbers — change any assumption you disagree with.

2 clouds = 1 integration pair · 3 clouds = 3 pairs
Adds an engineering block — you set the effort
Fully burdened — salary + benefits + overhead.
Before business logic. 1 engineer-month ≈ 160 hrs (≈4 weeks) — adjust to your own estimate.
CSP API changes, security patches, on-call.
Building it yourself
$—
Your build cost (Year 1, incl. first-year maintenance)
$—
Ongoing, every year after
And it still doesn't produce a cross-cloud attestation — only two disconnected cloud logs.
  • Deploy in 30 minutes, not months.
  • CSP-compatibility maintenance is ours, not your on-call rotation.
  • One signed record per object, across the boundary. See the attestation ↓
Contact sales for a private offer

These are your numbers — adjust any input. We don't pre-fill a savings figure; the comparison is whatever your own assumptions produce.

Why teams move

Four reasons teams make the move.

01Speed

Minutes, not months.

A cross-cloud pipeline is normally a multi-month engineering build. With Transfer General it's a same-day deployment.

02Cost

Nothing to build or maintain.

You buy the pipeline — not the per-cloud integration work, the FIPS validation, and the maintenance that never ends as cloud APIs change.

03Control

Your accounts, your keys.

It runs entirely inside your own cloud accounts. Keys stay in your KMS, and your data never touches Server General.

04Proof↓

Signed proof, every object.

When someone asks you to prove a transfer arrived intact, the answer already exists — produced automatically, never assembled after the fact.

Setup

Stand it up once. Run it for everything.

Setup is a deployment, not a project. Stand Transfer General up inside your own cloud accounts in about 30 minutes — then point it at as many source-to-destination routes as you need, across any pair of clouds, in any direction.

01
Deploy the control plane
A one-time deployer role lets the config UI stand TG up inside your account — UI, immutable log, and serverless workers. It hands back a scoped runtime role and the deployer access is revoked. About 30 minutes, your perimeter, your IAM.
SpeedControl
02
Define your pipelines
Point each pipeline at a source and destination bucket — any cloud pair, either direction. One deployment carries as many as you need, so the next route is minutes, not another project. Nothing new to build, nothing new to maintain.
SpeedCost
03
Run — on every trigger
Serverless workers move data the moment an object lands, encrypted with keys from your KMS, scaling to zero when idle. Every event is written to the immutable log — the record that becomes a signed attestation once the transfer completes. Nothing routes through Server General.
ControlProof ↓
Live · your account6 running
AWS → GCPrunning
GCP → Azurerunning
Azure → AWSrunning
AWS → Azurerunning
GCP → AWSrunning
Azure → GCPrunning
Every cloud pair, both directions.
Six pipelines — one deployment.

Every object that moves leaves behind one signed record of the whole cross-cloud journey — independently verifiable, no call back to us. See what your auditor receives ↓

Where it's used

Three places cross-cloud transfer is a standing need.

Not a one-time migration — an operating condition. One deployment covers all three.

AI / ML Primary

Use the best tool on each cloud.

Train on one cloud, prep or serve on another, without rebuilding a pipeline each time you mix providers. TG moves the data on a standing route — and produces a data-provenance / integrity report, so what went into a model is provable.

AI edition
Healthcare

Move PHI across clouds without hand-building it.

Stop staffing a HIPAA-grade cross-cloud pipeline and the evidence trail that has to come with it. TG deploys in your own accounts, encrypts at the object layer, and produces the integrity record on its own.

HIPAA / HITECH · Standard or AI edition
Federal

Cover the boundary your authorization doesn't.

FedRAMP authorization stops at each cloud's boundary; a transfer between clouds exits both. TG provides compensating controls for that gap — object-layer FIPS encryption and an independently verifiable record of the crossing.

FedRAMP / FISMA · Federal edition
Editions

One pipeline. Three compliance realities.

Same architecture across all three — your own accounts, keys from your KMS, signed proof for every object. You're priced by your cloud configuration, not by how much data you move; the edition sets your compliance mapping.

Standard
SOC 2 · GLBA · HIPAA

For teams that need clean, provable cross-cloud transfer under commercial compliance.

  • Own-account deployment, customer-held keys
  • Reports map to HIPAA / SOC 2 / GLBA — chosen at setup
  • Per-object signed attestation · FIPS 140-2 Level 2
Contact sales
AI
Data provenance · HIPAA

For teams moving training and inference data across clouds, where what went into a model has to be traceable.

  • Everything in Standard
  • Reports map to a data-provenance / integrity record — prove a dataset arrived intact, no compliance regime required
  • Built for recurring, multi-cloud movement
Contact sales
Federal
FedRAMP · FISMA

For federal systems where a transfer between clouds exits your authorization boundary.

  • Everything in AI
  • Reports map to FedRAMP control mapping + ATO evidence
  • You sign attestations with your own key, in your own KMS — sovereign-cloud (GovCloud / Assured Workloads / Azure Gov)
Contact sales

All deals are arranged 1:1 through a private offer on Google Cloud Marketplace.

Proof

When the auditor asks, hand them one signed record.

Each cloud can prove what happened inside its own walls. Neither proves the crossing between them. Transfer General signs one record that covers the whole journey — and your auditor can verify it without ever contacting us.

Transfer Attestation Verified
Objecttg_object_id a7f3c9…2b91c4
Sources3://prod-phi/patient_0412.dcm
SHA-256  9f86d0…f4c2e7
Destinationgs://analytics-phi/patient_0412.dcm
SHA-256  9f86d0…f4c2e7
Integrityhash_match = true ✓
SignatureECDSA P-384 / SHA-384
Signed byServer General ASK · KMS
CryptoFIPS 140-2 Level 2
Completed2026-06-20T14:22:09Z
Verify offline against our public key  ·  or authoritatively via the cloud provider's KMS
— Sample record —

One record, the whole journey

Source hash and destination hash, linked and signed in a single record. No stitching two clouds' logs together by hand.

Verify it without us

Check the signature offline against our published public key, or authoritatively against the cloud provider's own KMS. No dependency on Server General.

Always ahead of the ask

Produced automatically the moment a transfer completes — the evidence exists before anyone requests it. You're never caught assembling it later.

See a full sample attestation →
Interactive demo

See the full walkthrough.

A short guided walkthrough — the audit problem, the cross-cloud evidence gap, and how Transfer General closes it. No login required.

Procurement

It may not even be new budget.

Transfer General transacts on Google Cloud Marketplace. If your organization has committed Google Cloud spend, eligible Marketplace purchases draw down against that commitment — so adopting TG is often a reallocation of budget you've already set aside, not a new line item to justify.

Google Cloud Marketplace All sectors · all editions

Transact on Google's paper via Private Offer. Eligible purchases draw down your committed Google Cloud spend (MACC) — turning adoption into a reallocation, not a fresh approval cycle. Commercial, federal, and state buyers can all transact here.

Google Cloud Ready — Regulated & Sovereignty Solution
Carahsoft Federal · SLED

For government buyers, Transfer General is also available through Carahsoft — the procurement vehicle your contracting office already works with, on the contract vehicles your agency already trusts.

Carahsoft Blue Vector Logo - Web Pantone 286 U Official Carahsoft partner

Prefer to go direct? Every deal can be a Private Offer shaped to your volume and commitment — it starts with a conversation.

Proof of concept

See it run on your own data.

A proof of concept stands up in about 30 minutes, entirely inside your own cloud accounts. TG moves real data on a real pipeline — your keys, nothing through Server General — and hands you a signed attestation at the end. See exactly what it does before you commit to anything.

~30-minute setup Your own accounts Your keys, nothing through SG A real signed attestation
Request a PoC → Book a 20-minute walkthrough