Daily planner · macOS · local-first · waitlist only, not yet buyable
The design lead's morning list, including the Figma comment addressed to someone else on your team.
Your morning is two Jira instances, Figma comments and a calendar. Docket is the one screen where the answering gets done, and it writes your answer back to the account the work came from.
Today: your plan, your real meetings and the focus blocks Docket wrote, on one screen. Demo data throughout; real client names never appear on this page.
What it does
Your whole morning, one list
Nine systems produce the noise. Docket reads them all, works out what needs you, and lets you answer without opening a single tab.
Several Jiras, one list
Hosted and self-hosted Jira, several accounts at once, and every write goes back to the account that owns the issue.
Figma comments find their owner
Mentions meant for your teammates land where the lead can see them. The comments you find days late are usually the ones addressed to somebody else.
A notetaker that stays home
Docket records the meeting from your Mac's own audio and transcribes it on the device.
Follow-ups that don't evaporate
After the meeting, each action item becomes a ticket, a line on today's plan, or a calendar block. Your choice, and nothing lands without your approval.
A day plan with honest capacity
Plan against the hours your meetings actually leave you. Drag a task onto the day canvas and it becomes a real calendar block; remove it and the block goes too.
It tells quiet from broken
An empty list can mean peace or a dead token. Docket names the source that is down and marks every view that depends on it as incomplete.
The loop
Gather, plan, record, route
The morning
Open one screen: everything that moved overnight, across every account, ranked by what needs an answer from you. Answer it there. Every comment, transition, estimate and reply is written back and logged.
The day
Work from the hours your meetings leave, block focus time on your real calendar, run a timer against the estimate. Say "block an hour Thursday at half nine" in a meeting and Thursday 09:30 is prefilled.
The close
The day closes with what moved and what carries over. An on-device AI drafts the standup from what you did.
No server, no account, and nowhere
for your clients' work to end up.
There is no Docket cloud: your tokens, your tickets, your transcripts and your recordings live in plain files on your own Mac. The AI that drafts your standup runs on the device, and so does the transcription of every meeting you record. Every connection the app can make, enumerated.
- Your data in plain, readable files; export everything, any time
- Email and Slack are read-only connections: the app cannot post, mark or send
- Everything already synced stays readable even if you stop paying
- If the project ever ends, the source opens (the Obsidian pledge)
Why one app
My morning used to be four tools that didn't talk to each other: tasks in Jira, comments in Figma, a notetaker for the meetings, a planner for the day. My work sat on all of their servers. Docket is that stack folded into one app.
Docket turns what was said in the meeting into a Jira ticket and a block on your calendar, and transcribes it on the Mac. The table shows six of the ten meeting tools checked, taken from their own pages.
| Feature | Docket | GGranola | MMotion | SSunsama | AAkiflow | FFellow | NNotion |
|---|---|---|---|---|---|---|---|
| Meeting capture | ✓ no bot | ✓ no bot | bot joins | no recorder | bot joins | ✓ botless mode | ✓ no bot |
| Transcription | ✓ on your Mac | cloud | cloud | — | cloud | cloud | cloud |
| Actions → tasks | ✓ day plan | ✓ Zapier, paid | ✓ own board | — | ✓ one click | ✓ | ✓ |
| → Jira | ✓ | Zapier, paid | — | — | — | ✓ 2-way, paid | sync only |
| → Calendar blocks | ✓ | — | ✓ auto | — | manual | — | — |
| The catch | macOS only | Jira via Zapier, paid | bot in the call, own board | no meeting capture | tasks land undated | no calendar blocking | can't file a Jira issue, no blocking |
Checked August 2026 against Granola, Motion, Sunsama, Akiflow, Morgen, Fellow, Otter, tl;dv, Notion and Fathom, each time on the vendor's own pages. Granola, Fellow and Notion were re-read on 24 August, and several cells above changed as a result: the vendor pages behind them are now linked in the full comparison, with the sources and the rows where they beat us. The Motion, Sunsama and Akiflow cells here are from the earlier August reading and carry no link yet. Morgen, Otter, tl;dv and Fathom are in that page's meeting-notes section.
Pricing
Simple, upfront pricing
No free tier and no trial: the connectors cost real maintenance every time Jira, Figma or Google move something, and that is what the rate pays for.
- Every connector, every feature
- Or €180 a year, two months free
- Your data stays readable forever
- Everything in One person
- €12 locked for as long as you stay, €72 a year less
- A setup call: we connect your Jiras, Figma and Slack with you
- A direct line to us, and your requests jump the queue
- From three seats, €15 each
- Everyone keeps their own connections
- Their own identity in every Jira
Two guarantees, not one. Fourteen days to change your mind, refunded without a conversation. And your work is never hostage: everything already synced stays readable even if you stop paying, export always works, and if the project ever ends the source opens. Built by one person, paid so it stays maintained. Nothing is buyable yet; the waitlist hears first.
FAQ
Questions
Where does my data live?
On your Mac, in plain readable files. There is no Docket server and no account. Your source tokens are stored in an owner-only config file on your machine, and the security page states exactly how, including the parts that are still on the roadmap.
Where does the recorded audio go?
Nowhere. Recording and transcription happen on the device, and the action-item extraction works on the transcript, never the audio. With the default on-device engine, not even the transcript leaves the Mac. Configure a cloud AI engine yourself and the transcript goes to that vendor with your key.
Does it write to my tools, or just read them?
Jira gets comments, transitions, estimates and new tickets. Figma gets your replies, and your calendar gets the blocks you approve. Every write is something you chose, and it lands in an in-app audit log. Email and Slack are read-only: the app opens the mailbox in read-only mode and can never post, mark or send.
Why is there no free trial?
One person maintains this, and connectors break every time a vendor moves something. A paid app with a fourteen-day no-questions refund keeps it maintained.
What happens if I stop paying, or you stop building?
Your data is never hostage: everything already synced stays readable, and export always works. And if the project is ever discontinued, the source opens, the same pledge Obsidian made.
Windows? Linux? Mobile?
macOS, deliberately: the recorder, the calendar integration and the on-device AI all lean on the platform. A phone companion that reads your Mac is being explored; Windows and Linux are not planned.
Your morning, from one screen.
Join the waitlist and get an email when it opens, plus the occasional build update. The first twenty-five lock €12 a month for as long as they stay. After that the rate is €18.