The product workspace that runs on your computer.
Prodsy captures what customers and teammates tell you, turns it into requirements, PRDs, tickets and prototypes, and keeps your research, personas and competitors right beside it. It’s free, private by default, and happy to work with Claude.
macOS 13 or later, Windows 10 or 11, Linux. No account needed.
- Claude
- Jira
- Linear
- Notion
- Google Workspace
- Microsoft 365
- Ollama
- LM Studio
One app for the whole job.
Right now that work lives in a notes app, a call recorder, a research doc, PRDs in three places and ticket drafts in a fourth. Prodsy keeps it in one place, and keeps it connected.
Everything you hear, in one Inbox.
- Smart notes with past context beside you
- Call recording and transcript import, transcribed locally
- Email from the browser, .eml and .msg files
- Files, screenshots, sites and your codebase
Find anything by what it means.
- Search by meaning across notes, transcripts and docs
- A knowledge base where every statement shows its sources
- Corrections with a full history
- People and accounts: who said what, and when
From evidence to shippable work.
- Requirements with priority, persona and code checks
- PRDs and docs with versions
- Tickets with acceptance criteria
- HTML prototypes and slide decks
Know the landscape you’re in.
- Research that cites every page it reads
- Personas tied to real evidence
- Competitor profiles that flag when they go stale
Hand off in your team’s tools.
- Push to Jira, Linear or Notion when connected
- Email drafts and files with a sources appendix
- Copy as Markdown, Jira or Linear format
A helpful nudge, never a nag.
Prodsy keeps an eye on your workspace and speaks up when something needs you. Every nudge links to what it’s about, runs on your local model, and goes quiet with one click.
- Thin evidenceR-17 is running on a single quote. Want me to look through your notes for more?
- ContradictionDana said the opposite in the Oct 14 sync. Worth a look before this ships.
- Missing detailT-4 doesn’t say what goes in the error file. I drafted two acceptance criteria for you.
- Going staleApprovr’s profile hasn’t been reviewed in 18 days. Should I refresh it?
- Follow-upYou told Sam you’d look into second approvers “this week.” It’s Thursday.
- DuplicateThis one looks a lot like R-14. Merge them, or keep both?
Every decision keeps its sources.
Each requirement, PRD section and ticket links back to the exact words it came from. When someone asks why a ticket exists, you can show them the customer saying it.
“We download every PDF and type it in. If the PDF just filled the form, my team would save hours a week.”
Plays nicely with Claude.
Connect Claude Desktop or Claude Code and they can read what you choose and write back documents, tickets, personas and prototypes. Writes are versioned or wait for your review, and anything headed to another app gets your OK in Prodsy first.
Private by default.
Prodsy has no servers that hold your data. 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 |
Shape it to how you work.
Templates, workflows, extraction recipes and custom fields are plain files in your workspace. Change them yourself or ask Claude Code to. When you need more, build an extension with the free SDK.
.prodsy/ templates/prd.md templates/customer-call.md workflows/requirements.yaml recipes/support-ticket.md fields.yaml extensions/transcript-import/
Free to download. Yours to keep.
No account, no trial, no card. Install it, point it at a folder, and say hi.