NinjaWeb AI Backup Explorer starts from the backup question most people ask too late. It starts after a drive fails, after a folder is overwritten, after a laptop refuses to boot, or after someone realises that the important work was not all safely sitting in a cloud account.

The practical question is simpler: if your working PC failed today, which exact folders would you need back first?

NinjaWeb AI Backup Explorer v0.1.0 was built around that question. It is a portable Windows app for encrypted backups, incremental snapshots, full recovery archives and controlled restores. It is for local work that has real value: code repositories, client folders, AI/Codex workspaces, SSH and Git files, WordPress tools, project exports, scripts, prompts, notes and business files that would be painful to rebuild from memory.

Cloud sync is useful, but it is not the same as a backup workflow you understand. A random ZIP file on an external drive may help, but only if it is current, complete and restorable. AI Backup Explorer is designed to give a local operator a clearer system: choose the sources, choose the storage target, encrypt the backup, keep recent snapshots and restore the item you need when something goes wrong.

Local Work Is Often the Real System

A lot of business infrastructure does not look like infrastructure. It looks like normal folders on a working machine.

A developer may have repos, deployment notes, test exports, build folders and configuration files spread across a few local paths. A WordPress operator may have plugin packages, staging notes, server snippets, SSH access files and recovery commands. An agency may have client assets, handover files, working exports and project notes. AI and Codex users may have rules, prompts, local context, reference folders and custom workflows that are hard to recreate because they were built through use.

When that machine breaks, the loss is not only data. It is time, context and operating rhythm. That is why the backup question is not abstract. It is about whether the person responsible for delivery can recover the working system quickly enough to keep moving.

What the App Actually Does

NinjaWeb AI Backup Explorer runs as a portable Windows app. You extract the ZIP, run the launcher, and use the local browser interface to configure and operate backups. The release package is designed to include the runtime pieces it needs, including Node.js and WinSCP/SFTP tooling, so the normal user does not have to install Node, npm or WinSCP manually.

The app gives you four practical areas: Dashboard, Incrementals, Full Backups and Settings. The Dashboard shows state and health. Incrementals are for regular encrypted snapshots. Full Backups are for separate full archive points. Settings is where the server, auth, source folders, restore target and retention live.

• Incremental snapshots protect selected sources without treating every run like a full backup.
• Full backup archives provide separate encrypted recovery points.
• Resume support helps interrupted uploads continue from a saved checkpoint.
• Server scan helps list backup data already present on the remote side.
• Restore control lets you bring back a selected file or folder into a safe restore location.

That makes it more like a practical backup control panel than a blind copy command. The point is not just to send data somewhere. The point is to make backup and restore work visible enough that the owner can reason about it.

What You Need Before It Makes Sense

AI Backup Explorer is not magic storage. You still need somewhere to send the encrypted backups. In the current release model, that means an SFTP-capable server or storage target that you control or trust.

Before using the app seriously, you should know these details:

• Windows PC: v0.1.0 is a Windows release.
• SFTP target: a server, VPS, storage box or account that accepts SFTP connections.
• Server details: host, port, username and remote root path.
• Authentication: password or SSH private key.
• Encryption password: the password used to unlock backup and restore actions.
• Backup sources: the folders and files you want protected.
• Restore target: a safe local folder where restored files should land.
• Retention choice: how many recent full backups and incremental snapshots you want to keep.

A typical remote root might be something like:

<user>@<server>:/root/AI-Backups

Under that root, the app separates incremental backup data and full archive data. The exact server is your decision. The important point is that the remote side should receive encrypted backup content, not readable copies of your local files.

Why Incremental and Full Backups Both Matter

One backup type rarely answers every recovery problem.

Incremental snapshots are useful for regular protection. If you work in active folders every day, you do not want the backup process to feel so heavy that you avoid running it. Changed work should be protected without turning every backup into a complete archive ceremony.

Full backups serve a different purpose. They give you a stronger recovery point that is easier to think about as a complete archive. They are heavier, but that is why they are separate from the regular incremental rhythm.

For a local workstation, that split is practical. You may want regular snapshots for code, client work and AI workspace changes, and occasional full archives for stronger recovery confidence. AI Backup Explorer keeps those ideas visible instead of hiding everything behind one vague backup button.

Restore Is the Real Test

A backup that cannot be restored cleanly is only backup theatre.

The restore side of NinjaWeb AI Backup Explorer is built around selected recovery. Sometimes you do not need the whole machine back. You need one overwritten config file, one missing folder, one project asset, one export, one SSH-related file, or one working directory from before a mistake happened.

The safer default is to restore into a dedicated restore target, inspect the recovered item, and then decide what should replace current work. Restoring directly over original files is dangerous when the situation is already under pressure.

By default, temporary work and restore output belong under the current user’s temp area:

%TEMP%\NinjaWeb\AI Backup Explorer

Runtime app data belongs under the current user’s app data area:

%APPDATA%\NinjaWeb\AI Backup Explorer

Those details matter because a backup tool should keep its own runtime state separate from the files it is protecting.

Where This Fits in a Serious Setup

NinjaWeb AI Backup Explorer is not trying to replace every backup layer a business might need. A serious setup may still include cloud sync, server-side backups, offsite storage, device replacement planning, access control and documented recovery steps.

This app sits in a specific place: the local Windows workstation where real work happens before it becomes a clean cloud asset, a released package, a client handover or a finished deployment.

That is why it fits the same thinking behind our business systems work and AI automation work. A system is only useful when the owner understands what it does, what it depends on, and how to recover when something breaks.

Download NinjaWeb AI Backup Explorer v0.1.0

If your local PC holds work that would be expensive or painful to rebuild, start by listing the folders that matter. Then decide where encrypted backups should live, how you want to authenticate, what password protects the backup set, and where restores should land.

That is the level where NinjaWeb AI Backup Explorer makes sense: local sources, encrypted backup storage, SFTP upload, incremental snapshots, full archives and controlled restores.

You can download the first portable Windows release here: NinjaWeb AI Backup Explorer v0.1.0.