What is Docket?
A support centre you run yourself: bug reports, feature requests, a public roadmap, a changelog, an FAQ and testimonials, on your own domain. Underneath it is a folder of Markdown files in your git repository and a static site built from them. No database, and no account with us.
Does it work for my kind of product?
Whatever you build. Docket is a website, so anything that can hold a link reaches it: a Mac or Windows Help menu, an iOS or Android Settings screen, an App Store page, a README. Web products can also carry the widget.
How long does setup really take?
About ten minutes of your attention. You give your agent one line, answer a handful of questions, and it does the rest while you get on with something else.
Where does it run?
Wherever you already deploy. It is a static site and two small endpoints, so Vercel, Netlify, Cloudflare and the rest all take it without changes.
Can I put it on my own domain?
Yes, and that is the normal way to run it. It sits on a subdomain of yours, under your brand, with nothing of ours on the page.
Do my customers need an account?
No. There is nothing to sign up for and no password to forget. An email address is optional, and it is only ever used to tell somebody their thing shipped.
What stops it filling up with spam?
A hidden field bots fill in, an origin check that turns away scripts that never loaded your page, and a rate limit. The AI replies are capped per day as well, so a bad night costs you nothing.
How do people hear back?
Your agent writes the first acknowledgment within the hour. After that they see the status change on the board, and anyone who voted is told the day it ships.
Are email addresses visible to anyone?
Never. They are encrypted before they are written, so an address cannot be read out of your repository or its history, and none of them appear on a page.
Can I embed it in my own product?
Pro and Studio include a widget that drops into your own pages, so someone can file a report without leaving what they were doing. The board itself stays a normal website, so a link works from anywhere.
Can I keep a board private?
Boards are public today, and there is no privacy setting to turn on. You hold the code though, so putting a board behind your own gate is a change you can make and keep, which is not an option on a hosted tool at any price.
Can I review posts before they go public?
Not today. A post is a commit, so it appears as soon as it is made. You can delete or edit anything at any time, and because it is your repository that is an ordinary change rather than a support request to us. Testimonials are the exception: those are held until you approve them.
Can people attach screenshots?
Not today. Reports are text. If you want file uploads, that is a feature you can build on top rather than one you have to wait for us to ship.
What if I need something it does not do?
You change it. It is your repository and your code, so a missing feature is work you can schedule rather than a request in someone else's queue.
What support do I get?
Docket has its own support centre, where we answer within the hour. Email reaches us at support@theodorehq.com and we answer within one working day.
Do I need a coding agent to use Docket?
Not for the free edition, which installs by hand and runs every board. The paid editions hand the running of it to whichever agent you already use.
Which agents does it work with?
Claude Code, Codex, Cursor and anything else that can read a repository and follow a set of instructions inside it.
Is there an MCP server?
No, and there will not be. The data already sits in the repository your agent has open, so there is nothing for a server to serve.
Is there an API?
Two endpoints, one to submit and one to vote, both same-origin so they serve your own pages rather than other people's sites. There is no read API and nothing to authenticate against, because reading your data means opening a Markdown file in the repository your agent already has open.
What does it cost me in tokens?
Very little. It reads a handful of small files and writes a few more, and it only runs when you ask it to or when you ship a release.
What happens if I stop paying?
Nothing happens. It is one payment, the code is already in your repository, and it does not call home or check a licence, so it keeps running whatever becomes of us.
Whose brand is on it?
Yours. Your domain, your colour and your typography, with no vendor badge on a page your customers think belongs to you. The free edition carries a small Docket badge in the footer; the paid editions carry nothing of ours.
Can I change how it works or looks?
Yes. You own the code, so the colours, the boards, the statuses and what happens when something arrives are all yours to move.
Can I bring my existing feedback across?
There is no importer for Canny, UserJot or Featurebase. Your data in Docket is plain Markdown in a git repository, so the practical route is to ask your coding agent to move it across for you, which is the kind of job it is good at.
What happens if Docket stops being maintained?
Nothing stops working. The site is yours, the code is yours and it builds from your own repository, so it keeps running whether or not we do. The update check simply finds nothing and carries on.
Does it cost more as more people use it?
No. There are no seats, no tracked users and no per-board pricing, so the price is the same whether ten people or ten thousand use your board, and the same as your team grows.
What is actually in the free edition?
Every board, your own domain and the whole design system. What the paid editions add is the work being done for you rather than by you.
How many products does one licence cover?
All of them. Every edition is unlimited on products, because charging per board is charging you for shipping more.
Do I have to pay for updates?
No. Updates as a pull request against your repository, and you take them when you want them.
Can I get a refund?
Before you accept the invitation to the repository, yes, straightforwardly: email support@theodorehq.com and we refund you in full. After you accept it you are holding the source code, so we do not refund. Your statutory rights under the Consumer Rights Act 2015 are unaffected either way, and refunds are issued by Polar, who is the seller.
