SoloSync
All your boards live in one file on your device. The sync tool you already use carries it to your other devices, and Kanban Tasker makes sure nothing gets lost on the way. No account, no cloud of its own.
Set it up in three steps
- Create the data file
Start Kanban Tasker and choose Create data file. Save it in a folder that Nextcloud or another sync client keeps up to date. The suggested name is KanbanTasker.kanban.json.
- Keep it on the device
In your sync client, mark the file or its folder as always available offline, so the app always works on a real local file.
- Open it everywhere else
On each further device, choose Open data file and pick the same file. Settings such as the theme stay with each device.
One device after the other
SoloSync is made for one person working on one device at a time. Before you switch, let the file arrive:
- Your PCWork on your boardsMoves save at once; the status bar says Saved locally.
- Your PCSave and close the appYour sync client starts uploading the file.
- Synced folderLet it syncWait until the upload is done, then the download on the other device.
- Your laptopOpen and carry onKanban Tasker opens the same file, with everything you did.
Editing on two devices at the same time is not supported, and there is no live collaboration; your sync client may report a conflict then. Kanban Tasker notices when its file changes on disk: it checks every few seconds and whenever you come back to its window.
When copies overlap
Sync clients sometimes deliver a file late or leave a conflict copy next to it. Kanban Tasker is built for that:
- Every value carries a small stamp. When two copies differ, the newer change of each field wins, so changes made in different places both survive.
- Conflict copies of the same file in its folder are found and merged. They are never deleted.
- A recovery copy in the app’s own profile keeps the latest merged state, so a saved action is not lost if writing the file fails.
- If the file is missing or broken, the app keeps the last good state and writes nothing until the file is back.
- Deleted stays deleted: a board, column or task removed on one device stays removed after the merge.
Order shelves for the studio
High priority
Due 11/24/2026
Order shelves
High priority
Due 11/27/2026
Order shelves for the studio
High priority
Due 11/27/2026
One readable file
The data file is plain JSON in format 2: groups, boards, columns and tasks, each with its own ID. You can open it and read it.
To change it, use the app. Each value carries its stamp, and a value edited by hand without one does not count as a change. A file can be up to 64 MB, and every device that opens it needs a version of the app that supports format 2.
{
"schemaVersion": 2,
"documentId": "…",
"groups": […],
"boards": […],
"columns": […],
"tasks": [
{
"id": "…",
"boardId": "…",
"created": {…},
"fields": {
"title": {
"stamp": {
"milliseconds": 1789758000000,
"counter": 0,
"deviceId": "77a7bf49-f459-4aad-a43e-ef7d7fa2a37b"
},
"value": "Review the proposal"
},
…
}
}
]
}Backups
The recovery copy is not a backup history. Keep regular copies of the data file, as you would for any important document; the version history of your sync provider can help too.
Opening an older copy is not an undo: the app merges the newer changes it still knows into it.
Private by design
- No account, no advertising, no telemetry.
- No cloud of its own: your boards are never sent to the developer. Your sync provider moves the file under its own privacy policy.
- The file is unencrypted JSON, so choose a sync provider you trust.
- Device settings and the recovery copy stay in the app’s local profile on each device.
GitHub Projects, optional
If you like, Status boards from an organisation’s GitHub Projects appear beside your local boards. Their cards and moves sync online with GitHub through a registered GitHub App, and they are kept apart from your data file.
Later, perhaps: our own server
If there is interest, an optional sync through our own server may follow later. Today SoloSync works with the sync tool you already use.