Read-Only Scoped • Native Git Bundles

Sovereign repository backups, verifiable to the last commit.

Connect your GitHub organizations with strict read-only permissions. Our automated engine archives complete commit graphs into deterministic, point-in-time Git bundles streamed to encrypted S3 storage—restorable anywhere with standard Git tooling and zero vendor lock-in.

Start Backing Up Inspect Restoration Guide

Zero Write ScopesGitHub App is strictly read-only

True .bundle FormatIncludes branches, tags & HEADs

AES-256 KMSEncrypted private S3 storage

restoration-inspector — git bundle

git bundle verify backups/core-api-2026-09-22T040000Z.bundle

The bundle contains these 3 refs:
7a4f912c4e1a5f6e8b2d1c3a7e5f9a1b3c5d7e9f refs/heads/main
b89e2110c73d4e6a8f1b2c5d7e9f0a2b4c6d8e1a refs/heads/release/v2.4
f4118a9902b53c7e9a1b2d4e6f8a0c2e4b6d8f0a refs/tags/v2.4.1
 
The bundle records a complete commit graph.
Ref and commit integrity verification: OK

Validates packfile cryptographic signatures, branch refs, and commit ancestry without extracting.

Architecture Pillars

Engineered for Sovereignty, Scoped for Zero Trust

Four structural guarantees protecting your organization's source code, commit lineage, and business continuity.

Zero Write Access

Strict Read-Only Scoping

Our GitHub App requests exclusively contents:read and metadata:read permissions on explicitly selected repositories. The platform possesses zero write capability, cannot modify code, alter workflows, or touch environment secrets.

Fine-grained GitHub App repository selection

Short-lived cryptographic installation tokens

Zero pull request or branch write access

Native Git Archive

True Git Bundles (.bundle)

Unlike flat tarballs or zip archives that discard branch references and tag histories, our engine generates canonical Git bundle files. Every commit, branch ref, annotated tag, and detached head is cryptographically preserved.

Complete object database and packfile packaging

Full commit graph and merge topology intact

Cryptographically verifiable via git bundle verify

Rolling Snapshots

Automated Retention Windows

Define predictable rolling retention windows per repository. As scheduled daily or weekly backup jobs complete, older bundles beyond the configured threshold are safely pruned, controlling storage growth without manual intervention.

Configurable rolling bundle capacity per repository

Automated post-backup pruning in Amazon S3

Zero orphaned database records or dangling S3 keys

Zero Platform Lock-In

One-Command Native Restoration

When disaster strikes or compliance audits occur, restore complete repository history with git clone <bundle-file>. No proprietary unpacking agents, no platform APIs, and no vendor lock-in are ever required.

Works out of the box with standard native Git

Instant offline restoration on any developer workstation

Includes all remote branches and tagged releases

Operational Lifecycle

Three Steps from Installation to Disaster Recovery

A transparent pipeline connecting your GitHub organizations to encrypted S3 storage, retaining verified bundles ready for immediate restoration.

Connect Scoped GitHub App

Install our GitHub App into your organization or personal account. Select the precise repositories you wish to protect with strict read-only permissions for contents and metadata.

Architecture Seam:Uses state-signed OAuth callbacks and fine-grained installation IDs isolated per account.

Automated Bundle Streaming

Our headless worker executes scheduled or on-demand backup jobs. It authenticates with short-lived tokens, generates a complete Git bundle packfile, and streams it directly to your encrypted S3 bucket.

Architecture Seam:Packfiles are verified for ref completeness and encrypted with AWS KMS/SSE-S3 at rest.

Independent Point-in-Time Restore

In the event of an outage, accidental deletion, or ransomware attack, generate secure presigned download URLs. Restore full commit history and branch trees with a single native git clone command.

Architecture Seam:100% offline recovery capable. Zero reliance on our platform API during emergency restoration.

Restoration Guide

One Standard Git Command. No Proprietary Tooling.

True disaster recovery means sovereign independence. If our servers disappear, your backup bundles remain fully restorable using nothing more than standard Git on any Linux, macOS, or Windows machine.

Cryptographic Ref Integrity

Every commit SHA-1/SHA-256, merge parent, branch HEAD, and annotated tag is preserved inside the bundle's packfile format. Verification confirms complete ancestry before restoration.

Zero Lock-In Guarantee

We don't use proprietary databases or obfuscated zip dumps. A Git bundle is an official, standard Git transport format supported natively by every version of Git released since 2007.

Restoration Guide — Step-by-Step

Offline Capable

1Download timestamped bundle via presigned URL:

curl -o repository-2026-09-22T040000Z.bundle \
  "https://s3.amazonaws.com/repo-backups-vault/...?AWSAccessKeyId=..."

2Verify packfile and branch ref integrity:

$ git bundle verify repository-2026-09-22T040000Z.bundle
The bundle records a complete commit graph. OK.

3Clone complete repository locally into new directory:

$ git clone repository-2026-09-22T040000Z.bundle restored-repository
# Rebuilds master/main, all feature branches, and annotated release tags

Data Governance & Lifecycle

Clear Boundaries: Disconnection vs. Archive Purge

You maintain full sovereignty over your code. We decouple backup cessation from data destruction so compliance requirements and retention obligations are never violated accidentally.

Administrative Control

Disconnection

Severing an Installation revokes GitHub App authorization and transitions the account to a Disconnected Installation. Scheduled backup jobs and webhook synchronization halt immediately.

Preserves Historical Bundles: Existing Backup Bundles in S3 remain safely archived and available for download.

Stops Future Backups: No automated jobs or tokens are ever invoked again.

Reconnection Ready: If desired, the organization can be reconnected without losing previous backup history.

Permanent Destruction

Archive Purge

An explicit, user-initiated action designed for compliance with GDPR "Right to be Forgotten" mandates and data decommissioning policies. Requires deliberate user confirmation.

Physical S3 Deletion: All Backup Bundles and associated S3 objects are permanently deleted from object storage.

Database Purge: All metadata records, commit SHA references, and job logs are purged from the database.

Zero Residual Data: Cryptographic and physical removal leaves zero recoverable traces behind.

Answers & Technical Detail

Frequently Asked Questions

Everything you need to know about permissions, storage security, and Git bundle restoration.

Our GitHub App requests strictly read-only access to repository contents and repository metadata on explicitly selected repositories. The application has zero write access to your code, cannot merge pull requests, cannot alter workflows, and cannot access organization billing or environment secrets.

Protect your organization's Git repositories today.

Automate cryptographically verified Git bundle backups scoped strictly to read-only permissions. Complete sovereignty over every commit, branch, and tag.

Start Backing Up