Backups, and what happens when something goes wrong

Your work is saved continuously

Every time Mia builds or changes something in your app, she takes a snapshot of how everything looked at that moment. That covers more than your text or settings: it includes the underlying code and your data too.

Think of it as a timeline: every step Mia takes is recorded. If something goes wrong later, that timeline is what lets you go back to a moment when everything was still right.

You don't need to set anything up for this. There's no button to press and no schedule to create. It's simply taken care of.

What happens when a change goes wrong

Say you ask Mia to add a new feature to your app. Mia builds it, but after the change another part suddenly stops working. What then?

Mia checks her own work before a change goes live. If something isn't right, such as a logic error or a part that no longer responds, Mia spots it herself and tries to fix it before you notice anything.

If she can't fix it automatically, the change is held back. Your app keeps running as it was, and you get a notification that something needs extra attention. You lose no work, and your users notice nothing.

You can read more about how Mia checks her own work in the article hoe-mia-zichzelf-controleert.

Rolling back: restoring an earlier version

Sometimes you don't want to wait for Mia to solve a problem herself. You just want to go back to how things were yesterday. You can.

In Mia OS you can ask to restore an earlier version of your app. You don't need any technical knowledge for this. You describe what you want in plain language, "put my app back to how it was last week", and Mia finds the most sensible restore point.

What gets rolled back:
- Your app's settings and structure
- The parts or features that were changed
- The layout and text you had entered

Data your users entered in the meantime (such as orders or form submissions) is in most cases stored separately and isn't lost when you restore.

What happens to your data during an outage

Outages are rare, but they happen. A server can be temporarily unreachable, an update can cause unexpected behaviour, or something can go wrong at an external service your app relies on.

Mia OS runs on infrastructure designed for high availability. That means your app doesn't run in a single place: several systems can take over from each other if one fails.

Your data isn't stored in one place either. There are multiple copies, in multiple locations. So there is always a recent, intact version available, even if something goes wrong at one location.

You can read more about where your data is stored and who can access it in the article waar-staat-mijn-data.

What you can do yourself (and what you can skip)

Most users never need to do anything about backups. The system handles it. But a few things are worth knowing:

• Make a note of important changes. Not required, but useful. If you know you made a big change yesterday, you can ask Mia more precisely to go back to before that change.
• Report problems straight away. If you see something that isn't right, tell Mia right away. The sooner a problem is flagged, the better the chance that the recovery goes smoothly.
• Rely on the system. You don't need to download backups, copy files or keep screenshots. None of that is necessary, which is exactly how it should be.

Mia OS is meant for people who want to focus on their work, not on managing technical systems. Backups belong to those technical systems, and we're glad to take them off your hands.