Stable Cross-Region Preview

International Transfers

Secure, compliant, and high-throughput cross-region data migration and deployment synchronization for global engineering teams.

Overview

The International Transfers module enables seamless propagation of code artifacts, configuration states, and infrastructure manifests across .git's global edge regions. Designed for multi-jurisdictional teams, it enforces strict data sovereignty boundaries while maintaining sub-second sync latency.

⚠️ Note: Cross-border transfers are subject to your organization's data residency policies. Regions can be explicitly locked using the --region-lock flag or via the git.yaml policy file.

Technical Specifications

Parameter Value / Behavior
Encryption in Transit TLS 1.3 with AEAD ciphers
Encryption at Rest AES-256-GCM (region-keyed)
Max Payload Size 50 GB per transfer batch
Supported Regions us-east, eu-west, ap-southeast, me-central
Compliance GDPR, CCPA, SOC 2 Type II, ISO 27001
Transfer Protocol Chunked HTTP/2 + Delta-sync (Rsync-compatible)

Usage & Configuration

CLI Interface

Initiate a cross-region transfer using the git transfer command. The CLI automatically negotiates optimal routing and validates compliance policies before execution.

# Initiate transfer to EU-West region git transfer --source us-east --target eu-west \\ --project production-cluster \\ --include "./src,./config,./.git/hooks" \\ --exclude "node_modules,*.log" \\ --region-lock eu ✓ Policy validated. GDPR boundaries enforced. ✓ Initiating delta sync... 84.2 MB/s ✓ Transfer complete. Manifest updated in 1.8s

YAML Configuration

For CI/CD integration, define transfer rules directly in your .git/config.yaml:

# .git/config.yaml transfers: enabled: true routing: optimal-path compliance: enforce_data_residency: true allowed_corridors: - us-east → eu-west - eu-west → ap-southeast block_corridors: - eu-west → us-east # GDPR restriction retry_policy: max_attempts: 3 backoff: exponential

Architecture & Routing

International transfers bypass public internet routing by utilizing .git's private backbone mesh. Each transfer is segmented into encrypted chunks, routed through regional peering points, and reassembled using forward error correction. Delta synchronization ensures only modified blocks are transmitted, reducing bandwidth consumption by up to 94%.

Transfer state is tracked via idempotent job IDs. Interruptions are automatically recovered from the last verified checkpoint without data duplication.

Data Sovereignty & Auditing

All cross-border movements generate immutable audit entries. You can query transfer history via the API or CLI:

git transfer logs --project production-cluster --since 7d [2025-05-12 14:22:01] JOB-8F3A | us-east → eu-west | 142 MB | STATUS: SUCCESS [2025-05-11 09:15:44] JOB-7B2C | eu-west → ap-southeast | 31 MB | STATUS: SUCCESS [2025-05-10 18:42:19] JOB-6A1D | me-central → us-east | BLOCKED (Policy Violation)

Enterprise plans include automated DPA generation, data flow mapping exports, and integration with SIEM platforms for real-time compliance monitoring.

FAQ

Can I restrict transfers to specific regions?

Yes. Use the --region-lock CLI flag or define allowed_corridors in your YAML config. Transfers outside permitted boundaries are hard-blocked at the routing layer.

What happens if a transfer fails midway?

Transfers are checkpointed every 2MB. On failure, the system resumes from the last verified block. Idempotency guarantees prevent partial or duplicated state.

Is there a rate limit?

Standard plans allow up to 50 concurrent transfer jobs. Pro and Enterprise plans support unlimited concurrency with dedicated throughput allocation.