CapsuleCapsule
About Capsule

We built the backup tool we wish had existed.

Capsule exists because backup failures are quiet, restore failures are catastrophic, and the gap between the two is where most teams live — without realising it.

3

Database engines supported

AES-256

Encryption standard

<60s

Median install time

0

Times your credentials leave your server

Origin

How this started.

Not with a roadmap, not with a deck. With a production database that should have had a backup, and didn't.

The incident

A production database went missing during a server migration. There was a cron job. It had been failing silently for six weeks. No alerts. No off-server copy. The backup file was on the same disk as the database.

The wrong lessons

The obvious fix — pg_dump to S3, write a Slack alert — worked until it didn't. The script broke after a dependency update. The alert only fired on exit code 1, not on empty dumps. The off-server copy was never integrity-checked.

The right lesson

Backup isn't a script. It's a system that needs to survive infrastructure changes, be verified end-to-end, store data off the origin server, and tell you immediately when something goes wrong. DIY can't hold that invariant indefinitely.

Capsule

Built to be the thing we wish had existed. Every decision — encryption before upload, SHA-256 integrity checks, failure reporting to the dashboard, one-command restore — comes from a specific way the DIY approach failed.

What we are

An agent that runs on your server. Not one that needs to reach it.

Most backup SaaS products work by connecting to your database from outside — which means opening a port, creating a read-only user, and trusting that a third party can reach your infrastructure safely.

Capsule flips this. A lightweight agent runs on your server, next to your database. It uses the local tools you already have — pg_dump, mysqldump, mongodump — then encrypts the output before it leaves. We receive ciphertext. We never hold the key.

Your firewall rules stay tight. Your credentials stay local. Your data never travels in plaintext.

capsule — your server
$ capsule backup run
→ connecting to postgres://localhost:5432/prod
→ running pg_dump locally...
→ encrypting with AES-256-GCM (local key)...
→ checksum: sha256:a3f9c1...
→ uploading ciphertext to Capsule cloud...
✓ backup complete [2.1 MB · 4.3s]
# credentials never left this server
# plaintext never left this server
How we think

Principles behind the product.

These aren't values on a wall. They're the constraints that drove every architectural decision.

Zero-knowledge by design

Your credentials never leave your server. Your plaintext data never reaches our cloud. We receive only ciphertext — and we don't hold the key. This isn't a policy, it's an architectural constraint.

Built for the restore, not the backup

Anyone can write a cron job that dumps a file somewhere. The hard part — and the part that actually matters — is the moment you need to get your data back. Every design decision starts from that moment.

Transparent and verifiable

We tell you exactly what the agent does on your server. We tell you what traffic it sends. We give you the commands to verify it yourself. Trust should be earned with evidence, not marketing copy.

Simple enough that you'll actually use it

The most dangerous backup system is the one you keep meaning to set up. Capsule installs in under a minute, works with your existing setup, and stays out of your way until you need it.

For engineers, by engineers

We didn't build a SaaS to sell to procurement. We built the tool we wanted to use — one that fits naturally into a terminal-first, code-driven workflow, with no GUIs required to get started.

Honest about what we are

Capsule is a small, focused product. We don't have a 200-person team. We have strong convictions about how database backup should work, and we ship accordingly. Quality over noise.

Direction

Where this is going.

Capsule started as a CLI — because that's where engineers live, and that's where backup actually happens. The agent runs on your server; the command is what you trust.

The dashboard gives you visibility: every backup, every failure, every restore, across every server your team manages. Not as a replacement for the terminal — as the thing you check when something goes wrong at 2am and you need answers fast.

We're building toward a world where "do we have a good backup?" is a question you never have to ask, because the answer is always visible, always verified, and always actionable. No guessing whether the cron ran. No opening the server to check. No surprises.

Backup should be the last thing you worry about. We're making it the first thing that just works.

Works with the databases you already use.

No agents to install per database. One CLI, one dashboard, every engine.

🐘

PostgreSQL

pg_dump
🐬

MySQL

mysqldump
🍃

MongoDB

mongodump
The team behind Capsule

Built by TechFaithful.

Capsule is a product of TechFaithful — a remote-first technology agency that builds custom digital solutions across web, mobile, and cloud. Their conviction is straightforward: technology should faithfully serve business goals, not the other way around.

TechFaithful has spent years building software that solves real problems across industries — from property management systems to AI-powered learning platforms. Capsule is their answer to a problem every engineering team faces: reliable database backup that actually works when you need it.

The tagline is "We build or nothing." Capsule is what that looks like when the problem is your data.

Get in touch

Questions, feedback, or want to talk architecture? We read every email.

support@trycapsule.xyz

Stop hoping. Start knowing.

Your databases deserve better than hoping nothing goes wrong.

Capsule takes 60 seconds to install and runs quietly in the background. Start free — upgrade the day it's guarding data you can't afford to lose.

No credit card to start · Cancel anytime