How Prodsy works
Where it runs, where your work is kept, and what reaches us. The short version: your work stays on your computer, and nothing from your workspace reaches us.
Desktop or browser
The desktop app is the full Prodsy. The browser version comes after 1.0.
| Feature | Desktop app | In your browser Coming after 1.0 |
|---|---|---|
| Get it | Download for Mac, Windows or Linux | Open app.prodsy.app in Chrome or Edge |
| Your workspace | A folder on your computer | A folder on your computer, or storage inside the browser |
| Local models | Ollama or LM Studio, any size your computer runs | Smaller models that run in the browser on your graphics chip |
| Claude | Claude Code and claude.ai beside your work, on your own Claude plan. Claude Desktop and Claude Code over MCP. Prodsy’s chat with local models or your API key. | In the app with your key. Your own Claude Code can still pick up hand-offs over MCP from a computer with the desktop app. |
| Recording | Calls from any app, and your microphone | Your microphone, or a meeting in another browser tab |
| Jira, Confluence, Linear, Notion | Connected directly | Through the Prodsy extension, or by importing exports |
| Offline | Yes | Yes, once it’s opened |
| Locking | Your computer’s sign-in | A passkey lock, on by default |
Prodsy in your browser
Coming after 1.0- Open app.prodsy.app
In Chrome or Edge. Prodsy saves itself for offline use, so it opens even without a connection.
- Pick where your work lives
Choose a folder on the computer and allow Prodsy to use it, keep it inside the browser, or open a workspace you already sync.
- Models download once
Search and extraction models run in the browser. Nothing you write goes to a model you didn’t choose.
- Lock it with a passkey
Use Touch ID, Windows Hello or a security key. Prodsy locks itself when you step away.
Works best on a computer with 8 GB of memory or more and a recent version of Chrome or Edge. Safari and Firefox can keep a workspace inside the browser only. Add the Prodsy extension to connect Jira, Confluence, Linear and Notion; without it, import their exports and copy tickets out.
Sync and storage
Coming after 1.0Turn on sync and the desktop app, the browser version and the iPad all keep the same workspace. Your iPhone pairs with your Mac instead. Until then, your workspace is a folder of normal files on one computer.
| Using | How it stays matched |
|---|---|
| Desktop app on one computer, browser on another | Both sync. A change on one shows up on the other within seconds while both are online. |
| Desktop app and browser on the same computer | Each keeps its own copy and they sync, like two devices. They can’t share one folder at the same time; Prodsy tells you if you try. |
| iPad, on its own | Syncs like any other device, and works offline. It catches up when it’s back online. |
| iPad or iPhone with your Mac nearby | Paired: a live view of your Mac’s workspace. Nothing is copied. |
| Jira, Confluence, Linear and Notion | One device checks each tool and shares what it finds. If it’s off for 2 hours, another of your devices takes over. |
| Where your synced copy lives | Who can read it | Good for |
|---|---|---|
| Nowhere: just this computer | You | One computer |
| Dropbox, Google Drive, OneDrive or SharePoint | Only your devices. Your provider stores encrypted files. | Work data on company storage, personal work on your own |
| An S3 bucket or a synced folder | Only your devices | Companies that hand out buckets, or block other sign-ins |
| Prodsy Cloud | Only your devices. We store encrypted files. | Nothing to set up |
Encrypted before it leaves. Each change is encrypted on your device. The storage you pick only ever sees scrambled files with random names, and your devices hold the key.
Adding a device. Open Prodsy on the new device and choose your workspace. Approve it from a device you already use by checking that both show the same code. If none of your devices are around, your recovery kit gets you in.
Your recovery kit. When you turn on sync, Prodsy gives you a recovery key to save or print. Without it and your devices, no one can open the synced copy, including us.
When two devices change the same thing. Prodsy merges what it can and asks you about the rest. Nothing is thrown away; the other version stays in the item’s history.
What never syncs. Your API keys and tokens, and the search index, which each device builds for itself. Call audio stays on the device that recorded it unless you turn on audio sync.
What reaches us
Prodsy is a desktop app. Your workspace is a folder on your computer, and ProdXP never receives it. Here’s everything that can leave your computer, and when.
| What | Where it goes | When |
|---|---|---|
| Notes, recordings, email, Slack messages, files, code | Nowhere | Never, unless you send them to a cloud model, show them to Claude or share them |
| Reads from Jira, Confluence, Linear and Notion | Those services, with your own tokens | Only for the projects, spaces and pages you pick |
| Prompts and the context you attach | The AI provider you pick, with your own key | Only when you use a cloud model. Raw notes and quotes stay back unless you include them. |
| What Claude can read over MCP | Your Claude provider (Anthropic, or Amazon Bedrock or Google Vertex if your Claude app is set up that way), through Claude Desktop or Claude Code | Only collections you turn on |
| Research queries and the pages they find | Your search provider and those sites | When you run research, after you see the queries |
| Tickets and docs you push | Jira or Linear, with your own token | When you confirm a push |
| Model downloads | The model's registry | When you download a model |
| App version, operating system and update channel | Prodsy's update server | On the update check |
| Update download | Prodsy's update server | When an update installs |
| Diagnostic report | Whoever you email it to | Only when you send one |
How Prodsy handles data in detailLearn every screen and flow in the Guide
Try it your way.
The desktop app first. The browser version and iPad come after 1.0.