Plan-to-Cloud... backed up before Sunday

Local-first means your content is on your machine. It also means backup is your job. This is the opt-in that does it for you.

By Abelitie · September 25, 2026
Plan-to-Cloud... backed up before Sunday

What is available

Plan-to-Cloud backs up plans, media and themes to your own Google Drive before Sunday.

Available on PRO, MAX and ALPHA.

Why this exists

Your content stays on your machine. Lyrics, plans, media and recordings live on your disk, and the cloud holds only your account and plan status. That is a deliberate choice, and I have written about why: a connection outage should cost you your remote viewers, not your service, and years of accumulated work should be yours rather than held for you.

It has exactly one real cost, and I would rather name it than let people discover it: backup becomes your job.

Nothing happens automatically. A dead drive takes your song library, your themes and your plans with it, unless you did something.

Plan-to-Cloud is that something, done for you.

What it does

Before Sunday, your plans, media and themes are copied to your own Google Drive.

The distinction matters: not my storage, yours. This is not me quietly becoming the cloud-first product I chose not to build. The backup lands in an account you control, in a folder you can open, containing files you can read without me.

If you stop paying, the backup is still in your Drive. If you move to something else, it goes with you.

Who benefits

Anyone who has never set up a backup. Which, honestly, is most venues. Backup is the task that stays on the list.

Teams where one machine holds everything. A single production laptop containing years of song arrangements is a single point of failure with a real failure rate.

Venues preparing on one machine and running on another. The backup doubles as a way to move work between them.

Anyone who has already lost something. They do not need convincing.

What it does not do

It is not automatic sync. This is a backup, not a live mirror. Two machines will not stay in step by themselves.

It does not back up recordings. Those are large and they are yours to manage. A service recording belongs on a drive you chose, not pushed to a cloud account by default.

It is not a substitute for a second copy. A backup in one cloud account is better than none and it is still one place. For anything irreplaceable, have another copy somewhere else.

What a good backup habit looks like

Three things, and none of them take long.

Plans, media and themes... this feature, running before Sunday, into your own Drive.

Recordings... copied off the production machine deliberately, every week, to somewhere that is not the laptop. These are the files you cannot re-create, and they are the ones this feature deliberately does not touch.

One check, occasionally. Open the backup folder and confirm the files are the files. Not every week... once a month is plenty, and it is the difference between having a backup and believing you have one.

One more thing worth doing once: make sure somebody else knows where it is. If the person who set it up leaves, someone needs to know which account holds it. That is the most common way a backup becomes unavailable... not failure, just nobody knowing where.

A venue doing those three has removed the most common way years of work disappears.

The honest position

Local-first is a decision about where risk sits. It moves backup responsibility to you, and in exchange your content is genuinely yours and your service runs without an internet connection.

I think that is the right trade for software running live events in buildings. Plan-to-Cloud is me taking back the part of that trade that most reliably goes wrong... while keeping the backup in an account you own rather than one you rent.

Available now on PRO and above.

Asked often.

How do you back up service plans and media from live production software?

With local-first storage the files are on your disk, so backup is yours to arrange... an optional cloud sync copies plans, media and themes to your own Drive.

What happens to a song library if the production computer fails?

Without a backup, it is gone with the drive... which is the one real cost of keeping content local rather than in a vendor's cloud.

I have never set up a backup for anything. Is this complicated?

No. You connect your own Google Drive once and it runs before Sunday from then on. The only ongoing task is opening the folder occasionally to confirm the files are there.

Does this mean my plans are now on someone else's computer?

On your own Google Drive, in an account you control, in a folder you can open. Not my storage, and readable without me.

If backup matters this much, why not just store everything in your cloud like other products?

Because that trades one failure for another: your service would then depend on a connection, and years of work would sit somewhere you rent rather than own. This is me covering the part of local-first that most reliably goes wrong.

Why does it not back up recordings too?

They are large, and pushing service recordings into a cloud account by default is not a decision I should make for you. They are also the files you cannot re-create, so they deserve a deliberate copy rather than an automatic one.

What happens if a backup fails or the Drive connection lapses?

The next run tries again rather than giving up, and the folder shows you what actually landed. A backup nobody has verified is a belief rather than a backup, so check it once after the first week.

Try it on your Sunday.

Free tier, no credit card. A laptop and the phones in the room.

Start Free →
Plan-to-Cloud... backed up before Sunday | Broadcasteer