Local-first, explained: where your work lives in Plexii
What local-first means in Plexii: local work, account sync, connected features, encryption boundaries and practical offline checks.
On this page 10 sections
Local-first describes software that keeps a working copy of your material on your device rather than requiring a server round trip for every ordinary action. It is not the same as cloud-free, account-free or end-to-end encrypted. To understand a particular product, ask what stays local, what connected features send elsewhere and what still works when the connection is unavailable.
Plexii uses a local-first workspace model on Mac and Windows. Download Plexii free if you want to try the working arrangement with sample material. Read the data boundaries below before deciding whether to bring confidential work into it.
What lives on your computer
Plexii's privacy page says folders, tasks, desk objects, notes and SpeedDeck configurations are stored in a local SQLite database on your machine. Its product tour describes the workspace as living on the device first and working offline.
That gives ordinary work a local home. It does not mean the local database is the only copy in every configuration. The same documentation explains account-backed synchronisation and server features.
On a task desk, the distinction is practical. Your saved note is workspace material. A live web page shown beside it is still supplied by that website. The two can share a canvas without sharing an offline or privacy boundary.
The report workspace example shows the working surface: a return note, sections and feedback together. This article explains where that arrangement's data may go, not which app you should choose.
An account and local-first storage can coexist
Plexii's product page says you create an account when first opening the app and confirm your email. It describes the account as providing sync across devices, sharing and a cloud inbox that can receive shares while the app is closed.
While signed in, the workspace syncs to the account. The current privacy page also says you can keep a particular computer's workspace from syncing while remaining signed in. Check the relevant settings and help documentation for your configuration.
Do not read “local-first” as “no sign-in required”. Initial setup and later offline work are separate stages. If a workflow depends on a disconnected first launch or a particular account policy, verify that exact requirement before committing to it.
Nor should you assume signing out erases local work or server records. Account lifecycle, local files and deletion have their own controls and consequences, described in the policy.
What leaves through connected features
The privacy page lists features whose data needs servers: sync, sharing, the cloud inbox, live collaboration, chat and meetings. Using those features changes the data flow compared with editing a saved local note.
Sharing is a good example. A local document can be part of your private working set until you deliberately share it. The act of sharing creates a new audience and may involve a server-held representation.
Before sharing, check the contents, recipient or audience and access controls. A desk can contain private context beside a perfectly shareable report. The convenience of one working home does not make everything in it suitable for external access.
For a more detailed tour of these categories, read What leaves your computer. Use the live privacy policy as the primary statement if an older article or a remembered setting differs.
Encryption is several separate questions
Plexii states that sync and connected server features use encryption in transit, and that sync is not end-to-end encrypted. The privacy policy explains that the server can read server-held data needed to provide those functions.
The master-password vault is a separate feature. The policy says Plexii cannot recover its contents if the master password is lost. Do not extend that statement to all documents, all sync traffic or every server record.
Your computer's own security is another boundary. A local working copy remains subject to device access, operating-system protections and your organisation's policies. Local storage alone does not establish that an unattended or compromised computer is safe.
If a contract or policy requires a specific encryption model, evaluate that requirement directly. A general phrase such as “private workspace” is not precise enough to decide compliance.
AI has its own route
A local document does not tell you where an AI request runs. Plexii's privacy policy describes managed requests that pass through its server and a route using your own Anthropic key that goes directly from the machine to Anthropic. Plexii can also run AI on the machine itself with Local on this device (how it works).
Both routes involve sending information beyond the computer when those cloud services are used. The direct route avoids Plexii's server for those requests; it is not a claim that no external provider receives the prompt.
Check the chosen AI source, the feature and the material involved before making a request. Ask whether the relevant text, file context or question is permitted to leave the device under your work rules.
You can assess the desk arrangement without using AI. Keeping the source document and working note together is a different function from asking a model to summarise them. Evaluate the two decisions separately rather than treating AI as a mandatory part of local-first work.
Offline is a feature-by-feature test
The workspace can be local while a live website, meeting or cloud response remains unavailable without a connection. A useful offline test therefore names the operation, not just the app.
Prepare harmless sample material while connected. Close and reopen the app, then test opening a saved document, making a change and confirming that it persists. Check whether any attachments you need are actually present on the device.
Then try the connected actions you depend on and record which are unavailable. Do not interpret a failed website load as proof the saved note beside it was not local. Equally, do not interpret an app launching offline as proof every function is available.
The companion working offline guide covers preparing for a disconnected session. Do this preparation before travel or a planned loss of connectivity, not after the only usable connection is gone.
Sync is not the whole recovery plan
Synchronisation helps bring a working state to another device. It can also bring an unwanted change or deletion to that device. Backup and restoration require their own questions.
Find out what history is retained, what an export includes and how you would recover an earlier version. Read the current plan and help documentation rather than assuming a local copy gives you unlimited rollback.
Try restoring or opening an exported sample before trusting the route for important work. An unread export file proves that something was written, not that you can reconstruct the work you need.
For the broader topic, see backing up your work. Follow your organisation's retention and device policies, especially where client data or regulated records are involved.
A simple data-flow inventory
For one representative task, write a short inventory in ordinary language. This can be more useful than collecting a list of privacy labels.
- Saved report: where is the working copy, and is it syncing?
- Reference website: which external service supplies it?
- Shared update: who can access it and how can access be changed?
- Assistant question: which source is selected and what context is sent?
- Export or backup: where is it stored and has restoration been tested?
Use a fictional report until the answers are clear. If you cannot answer a question from current documentation, treat it as unresolved rather than filling the gap with an assumption.
This inventory is a decision aid, not a security audit. For sensitive use, involve the people responsible for information security or compliance before moving material into a new arrangement.
What local-first changes about the working day
The useful everyday benefit is that local work has a place on the machine you are using. You can arrange a task around its saved materials and understand which parts depend on a service.
The limitation is equally important: local-first does not abolish accounts, networks or the responsibilities of sharing information. Good product documentation makes those boundaries legible rather than asking you to infer them from a slogan.
If you are choosing software rather than learning the definition, read local-first desktop workspace apps compared. That article separates notes tools from a full task canvas and cites each product's own documentation.
For Plexii's costs and trial, pricing states a free-forever personal tier, Pro at US$12 a month or US$120 a year, and a 14-day Team trial. Select the arrangement for its fit with your work and data requirements, not only because a trial is available.
Common questions
Does local-first mean nothing leaves my computer? No. It describes the local working model. Sync, sharing, communication and cloud AI can create separate data flows, which the product should document.
Can Plexii be local-first and still require an account? Yes. Its product page describes account creation on first opening and local workspace storage. Initial setup and subsequent offline operations are different questions.
Is Plexii's sync end-to-end encrypted? No. Its current privacy page explicitly says sync is encrypted in transit and not end-to-end encrypted. The vault's master-password protection is a separate feature.
Does an embedded browser page become an offline copy? Not merely because it appears on a desk. A live website depends on that site's connection and behaviour; check or save authorised material separately when needed offline.
Does using my own AI key keep inference on-device? Not for the cloud route described in the privacy policy. It sends requests directly to the external provider rather than through Plexii's server. Check the selected source and permissions.
What should I verify before using confidential work? Storage, sync, sharing audiences, AI routes, device rules and recovery. Resolve any policy requirement with the responsible person before using real sensitive material.