Fractera Admin

Export data

Download a zip archive with the database and every stored file.

The two parts marked “secret” contain credentials: with them, anyone who opens the archive can act as your bot or reach your services. They are unchecked by default. If you tick them, keep the file off shared drives and out of chats.

The OpenAI key is never exported — you enter it again after restoring. Map data is never exported either: it is over a gigabyte, and the map page re-downloads its region on demand.

≈ 177 KB with the default selection, before compression
What a backup is made of

What goes in. Your rows and the meaning-search over them travel together — they share one SQLite file. Files come with the record of what each one is. The knowledge graph is the most expensive part here: rebuilding it means paying for a model to read every document again.

When to take one. Before anything that rewrites data — a restore, a migration to another machine, a risky experiment. A deploy does not need one: it restores code, and code lives in your repository.

What a backup does not cover. It is code-blind. Restoring an archive does not bring back the version of your application that produced the data, and a build rolled back does not roll back rows. Those are two different histories, kept in two different places on purpose.

GitHub connection required
en

North America

🇺🇸Englishen

Eastern Europe & CIS

🇷🇺Русскийru

Sub-Saharan Africa

🇺🇸Englishen

Asia Pacific

🇺🇸Englishen