Secure & Encrypted

Backup Management Built for Your Clients

DigiPack Server automatically receives, encrypts, and uploads your clients' database and storage backups to Google Drive — all from one dashboard.

Go to Dashboard

12 Clients

98 Uploaded

2 Failed

client-db-backup_2026-06-08.sql.gzip Uploaded

client-storage-backup_2026-06-08.zip Uploaded

client-db-backup_2026-06-07.sql.gzip Received

client-db-backup_2026-06-06.sql.gzip Failed

Features

Everything you need to manage backups

A complete backup management solution — from client configuration to secure cloud storage.

Auto Upload to Google Drive

Backups are automatically queued and uploaded to a structured folder hierarchy in Google Drive as soon as they arrive.

AES-256-GCM Encryption

Every backup file is encrypted before leaving the server using AES-256-GCM with a unique IV per file. Files on Drive are completely opaque without your key.

Multi-Client Management

Manage multiple clients from a single dashboard. Each client has isolated folders, API credentials, and configurable retention policies.

Database & Storage Backups

Supports both database dumps (.sql.gzip) and full storage archives (.zip), each tracked and stored in their own Drive subfolders.

Retry Failed Backups

Failed uploads are kept locally for manual retry. One click re-queues the job — no need to resend from the client machine.

Secure Download

Download any backup directly through the dashboard. Encrypted files are decrypted on-the-fly and streamed to your browser.

How It Works

Three simple steps

From client machine to encrypted cloud storage in minutes.

Client Sends Backup

The client machine runs a scheduled backup script that sends the compressed file to your DigiPack Server API with a secret key.

Server Receives & Encrypts

The server validates the request, stores the file, and queues an upload job. The file is encrypted with AES-256-GCM before upload.

Uploaded to Google Drive

The encrypted file is uploaded to the client's dedicated folder on Google Drive. The local copy is deleted after a confirmed successful upload.

Security

Your backups are protected end-to-end

DigiPack Server was built with security as a first principle. Files are encrypted before they leave your server — Google Drive only ever sees ciphertext.

AES-256-GCM authenticated encryption per file
Unique random IV generated for every backup
Encryption key stored only in your server's environment
Existing unencrypted backups still download correctly
Per-client API secret keys with regeneration support
All dashboard routes protected by authentication

BACKUP_ENCRYPTION_KEY 32-byte AES key stored in .env — never leaves your server

AES-256-GCM Industry-standard authenticated encryption with 16-byte auth tag

Unique IV Per File Random 12-byte nonce ensures no two files share a keystream

Google Drive OAuth 2.0 Scoped access token — only your designated Drive folder is accessible

FAQ

Frequently asked questions

DigiPack Server supports two types: Database backups (.sql.gzip compressed SQL dumps) and Storage backups (.zip compressed file archives). Each type is stored in its own subfolder on Google Drive.

Yes, when BACKUP_ENCRYPTION_KEY is set in your server environment, all new backups are encrypted with AES-256-GCM before upload. Google Drive stores only the ciphertext — the decryption key never leaves your server. Older backups uploaded before encryption was enabled are still downloadable as-is.

The job is retried up to 3 times automatically. If all attempts fail, the backup is marked as Failed and the local file is preserved. You can retry it with a single click from the dashboard — no need to resend from the client machine.

Each client has a configurable keep_files setting. After each successful upload, backups beyond that count are automatically deleted from both Google Drive and the database, starting with the oldest.

Navigate to Settings → Google Drive in the dashboard. Enter your Google OAuth client credentials and click Connect. The server handles token refresh automatically — you only need to connect once.