OpenzaPersonal Cloud,
in your own account.
Take your Openza tasks to the Web while keeping a local-first desktop. Each user connects their own Cloudflare account, which holds their Web app and task database.
The Cloudflare OAuth client is public, allowing users to authorize setup in their own accounts. These steps explain the intended flow and support existing preview installations; this page is not a sign-up or a production-release announcement.
What lives where?
On your desktop: your local task database and connected-provider credentials. It continues to work offline.
In your Cloudflare account: a Worker serves your Web app, and a D1 database stores the synchronized task copy. Task APIs require owner sign-in or a paired desktop.
In your browser: you sign in using a passkey and work with your tasks. The public website at openza.org does not receive or host your tasks.
The setup flow
- Start in Desktop Settings. Choose Personal Cloud setup. Review what will be uploaded and the Cloudflare permissions before continuing.
- Authorize your own Cloudflare account. Openza requests Account Settings: Read, D1: Write, and Workers Scripts: Write to set up the resources. Setup authorization is temporary and discarded afterward.
- Let Desktop prepare your cloud. It creates the database, deploys the Web app, prepares the schema, verifies the connection, and pairs this desktop.
- Finish security in your browser. Create the owner passkey and save the recovery code privately. Use the generated Personal Cloud address to open your tasks—not openza.org.
Already have a Personal Cloud?
Open its Web Settings and choose Pair a desktop. Then, in Desktop setup, choose Pair existing cloud and enter that cloud’s address and its newly generated one-time code. Codes belong to the cloud that generated them; localhost and a deployed cloud are separate.
Everyday use
Desktop sync makes adopted Openza tasks across Spaces available to your cloud. Add, edit, organize, and complete tasks on the Web, then synchronize changes back to Desktop. Provider-related operations may require an online, provider-capable desktop; the cloud does not hold provider credentials or contact providers directly.
A few important boundaries
Does my data go to an Openza server?
No Openza-operated task-hosting service sits in the sync path. Your task copy is in your Cloudflare account. Cloudflare processes and stores that content; this is not end-to-end encryption.
Are Cloudflare charges possible?
Your resources count toward your own Cloudflare account’s limits. Usage beyond your plan’s allowances may incur charges. Review Workers pricing and D1 pricing before setup.
What if I disconnect or remove my cloud?
Disconnecting a desktop preserves its local tasks and does not delete the cloud. Removing Personal Cloud is different: it deletes its deployment and database. Download and verify a private SQL backup first. An update or restore should be deliberate; schema changes are not automatically undone by rolling back the Worker.
Can I use a shared browser?
Avoid shared browser profiles for private tasks. The Web app caches its last confirmed task copy locally; sign-out revokes the session but does not erase that cache. Clear the site’s data before leaving a shared device.