Connect a server in one line. Run scheduled file and database backups. Restore a single table or an entire database — and verify every run by its checksum.
| database.sql.enc | 184.2 MB | a1b7…04fe |
| files.tar.enc | 2.13 GB | 9f02…17dd |
Point a job at an S3-compatible bucket or a local disk. Artifacts stream straight from the agent to the destination you chose — never through a storage provider you did not pick.
| Target | Kind | Used | Last write | Health |
|---|---|---|---|---|
| s3://acme-backups/eu-north-1 | S3 | 412 GB | 2m ago | OK |
| /mnt/backup/vol1 | Disk | 1.94 TB | 4m ago | OK |
| b2://acme-vault | B2 | 88.4 GB | 2h ago | Stale |
Data is sealed with a fresh key per run. That key is wrapped to the public key for the job, so neither the transport nor the destination can read plaintext.
Run one line on the server. The agent registers with your enrollment token.
systemctl status pcbackup-agent
active (running)
Define a job once. It runs on the clock you set, unattended.
0 3 * * *
daily · 03:00
Pull a single table or a whole database back, from any sealed run.
pcbackup restore --table users
restored · 12.4 MB
Paste the command, and the agent installs itself, enrolls, and starts on schedule. Run it on amd64 or arm64.
$ curl -fsSL https://backup.pinecone.no/install.sh | bash -s -- --token=<enrollment-token>
Requires root · installs a systemd unit · amd64 and arm64
Every mechanism above is a named, verifiable detail. Here is the whole stack in one place.
PC Backup is in an invite-only closed beta while we harden every path. You connect the servers, keep every artifact in storage you control, and we run the panel for you.
The full control panel, hosted and maintained for you. Access is granted by invitation.
One line on the server. Your first sealed, verifiable backup before the next scheduled window.
Closed beta. Invite only.