Security

Philosophy of resilience

When someone asks how you’d keep working if the network or a vendor is down

You can open this Help article and walk through how N78-Ops is designed to keep working when the network or hosted services are slow, spotty, or unavailable.

Treat the network as a variable, not a requirement

Connectivity improves the experience—email handoffs, optional cloud backup, and similar features—but the architecture assumes the network is unreliable. Day-to-day work is anchored on this device first.

Works even when the internet does not

Core workflows are built so your ability to build quote and invoice PDFs on your phone, manage clients and quotes, and record payment does not depend on any one online service staying up. In plain terms: you can still finish client-ready documents and mark jobs paid when a website or backend is slow or offline. When that happens, the copy of your data on this device stays what you work from.

Built for real workdays

The app is not a shell that only works while someone else’s server answers every tap. N78-Ops keeps doing the job above on your device even when the wider internet or a vendor’s systems are having a bad day.

What this does not claim

Email delivery, third-party inboxes, and optional cloud sync still depend on their networks and policies. Your job if you care about recovery is unchanged: keep verified full backups current (.n78bk, or legacy .json / .zip), use Data & files → Import then Restore when you move devices (see Data files & backups), verify on a test device when you can, and treat portable backup files like cash in an envelope. Spreadsheet CSVs cannot restore the app — they are not a substitute for a full backup.

← All N78-Ops help topics