Token-based backup service

Curl it.
Forget it.

Dead-simple backups for lazy developers. One POST request — we handle rotation, retention, and yell at you if a backup goes missing.

Backups: 93
Stored: 219.8 MB
# your entire backup pipeline:
curl -s -X POST \
  -F "file=@backup.sql.gz" \
  -H "Authorization: Bearer $TOKEN" \
  https://savemyvibe.com/api/v1/upload
Script constructor

Your backup script, written for you

1
Category
2
Type
3
Configure
4
Schedule
5
Review

What do you want to back up?

AI Script Constructor

For any scenario — describe it in plain text

Log in / Sign up to try

Which type?

Didn't see what you need?

Try AI Constructor

Configure

Schedule

We randomize generated schedules to spread uploads across time and avoid midnight traffic spikes. You can still edit the cron expression manually after deployment on your server.

Daily randomized schedule

Cron schedule runs in the server's local time zone.

Review & activate

Sign up or login to activate this script with a real upload token. Your progress is saved.

Log In Sign Up

🏁 Step 6: Deploy

Your secure backup script is ready to run. Choose your preferred installation method below.

Recommended for security. Run this single copy-paste block to safely write the backup script and register it to your crontab. No external network downloads required.

# command will appear here
  • Security baked in: Your secure upload-only token is compiled straight into the commands above.
  • Single-Use Installer: Option B link is short-lived (1 hour) and can only be downloaded once for safety.
  • File Location: Writes to /usr/local/bin/smv-backup-[slug].sh.
  • Crontab Automated: Deduplicates existing entries and registers the cron schedule safely under root.
/usr/local/bin/smv-backup-<scenario>-<archive>-<id>.sh
#!/usr/bin/env bash
/usr/local/bin/smv-backup-<scenario>-<archive>-<id>.sh
#!/usr/bin/env bash
# ← Select a backup type to get started

Success! The backup script is now fully operational. Your secure, upload-only token has been baked directly into the script above. Please note that for security reasons, you will not be able to retrieve or view this token's plaintext again.

How it works

Three steps.
Then never think about it again.

01

Create an archive

Name your backup target, pick a retention policy, and get a unique bearer token.

02

Upload via curl

Send gzip, JSON, SQL dumps, or any file with a single POST. No SDK needed. Not sure how to generate the dump? The script builder writes the whole pipeline for you.

03

We handle the rest

Automatic rotation, retention enforcement, and alerts if a backup goes missing.

Free tier: 30-day retention, up to 3 archives

Retention & alerts

Set it. Forget it. We won't.

Minimum survival rule

Even after your retention window expires, your last copies are always kept — up to 3 per archive on Free, up to 10 on Pro.

  • Free: up to 30 days retention
  • Pro: up to 1 year retention

Smart alerting

Define your expected upload frequency. If a backup is late, we let you know before you find out the hard way.

  • Free: email alerts
  • Pro: email + webhooks
Pricing

Pricing that vibes.

Just $9.99 to keep the good vibes rolling.

Free No card required
$0/mo
  • 3 archives
  • 5 GB total storage
  • 30-day max retention
  • Email alerts
  • Up to 3 surviving copies per archive
  • 500 MB max per upload
Get started
Compare

How we stack up

Dead-simple backups vs. the alternatives. No spin, no omissions.

Why developers trust SaveMyVibe

1-click

curl uploads. No SDKs, no config files.

Token-based

Simple auth. One token per archive.

Auto-rotate

Retention handled for you.

Start backing up — it's free Try the script builder