All postsChangelog

Changelog: August 2026

Published rates, a security page that says what we do not have, solution pages per job, and a comparison page that names names.

saved.sh

What shipped this month. Changelog entries live here rather than on their own page, so they are searchable and taggable alongside everything else.

Pricing is public

The four meters now have numbers attached. Computation, storage, archive and transit, with no seats and no tiers, and a calculator that shows what a workload generates.

RUN STARTSRUN ENDSComputationwhile the run executesStorageworking space, in flightTransitbytes in, and out on restoreArchiveevery day it is keptARCHIVE KEEPS RUNNING. IT IS WHAT MOST BILLS ARE MADE OF.
Three meters stop with the run. Archive keeps going, and that is what most bills are made of.

A security page that leads with the bad news

/security is new, and the section people usually bury is near the top: no SOC 2 report, none in progress, and no uptime SLA. The rest of the page is mechanisms rather than adjectives, so a reviewer can evaluate the design instead of taking our word for it.

PushWE HOLD NOTHINGyou connect, we get a fileYour workerWE HOLD NOTHINGpayload stays in your configManagedWE HOLD A CREDENTIALin a secrets managerTHE ONLY PATH WHERE WE HOLD A CREDENTIAL IS THE ONE WHERE YOU ASK US TO CONNECT.
Only one of the three paths ends with us holding a credential, and it is the one where you asked us to connect.

Solutions, organised by the job

Six pages under /solutions, each starting from something someone actually arrives with rather than from a feature:

  • CI/CD backups, one step in a pipeline you already run
  • Database backups, on any of the three paths
  • Files and folders, on hardware you control
  • Fully managed, when hosting nothing is the point
  • Anything you can script, the escape hatch with no reduced guarantees
  • Compliance and custody, when the bucket has to be yours

A comparison page

/compare puts cloud-native backup services, built-in snapshots, a script and a bucket, and us on one table. It compares structural properties only, and it has a section on where you should use something else, which we would rather write ourselves than have you infer.

SNAPSHOTEXTERNAL COPYSurvives a dropped tableSurvives a bad migrationSurvives a deleted cloud accountSurvives stolen production credentialsSurvives ransomware with admin accessReadable without the vendorTHE FIRST TWO ROWS ARE THE ONES PEOPLE PLAN FOR. THE REST ARE THE ONES THAT END COMPANIES.
The first two rows are the ones people plan for.

Smaller things

10

Blog posts, with search and tags

23

Illustrations across the site

53

Pages, all statically rendered

  • Per-post social cards, generated at build time
  • The whole site moved to a new design system: warm ground, green ink, one accent
  • /architecture now shows the artifact lifecycle rather than describing it

Still not done

The client tools are not yet public repositories, so /download links release pages that do not open yet. That is the next thing, and it is the one that makes the encryption claims on /security verifiable rather than asserted.