Support
Your project can describe what is wrong with it. Start there, then the troubleshooting page, then write to us — in that order, because the first two answer most of it in the time it takes to send an email.
Try this first
- 1
Run pnpm support in your project
It prints one report of what your project looks like right now: versions, which resources were never created, which secrets are missing, which migrations have not been applied, how far behind the starter you are. It reads no secret values, so the report is safe to show anyone.
- 2
Give the report to your assistant
Paste it back into Claude Code, Cursor or Codex and say: "Read this and fix what it names." Most of what it finds, your assistant can put right without anyone else being involved.
- 3
Look up the error code
Anything that fails on purpose says why, with a code like E_NOT_LOGGED_IN or E_PENDING_MIGRATIONS. The troubleshooting page has a section for each one: what it means, why it happened, what to do.
Where to write
Write to support@chandlery.app from the address you paid with. Include the output of pnpm support, what you were trying to do, and what happened instead. Those three things are usually the difference between one reply and six.
The starter repository
Your purchase adds you to a private repository, and that repository has issues turned on. Opening one there is better than email for anything that might be a bug in the starter: it stays attached to the code, other buyers can find it, and a fix can be linked to it.
One person reads that inbox, and reads all of it. Most replies go out within a working day. Something that takes longer is usually being fixed rather than answered — which is the outcome you wanted anyway. This is a description of the rhythm, not a service-level agreement.
What support covers
- The starter's own code, and anything in it that does not do what the documentation says
- Deploys, updates and scripts that fail while you are following the documented path
- Documentation that is wrong, out of date, or clear only to somebody who already knew
- Working out which of the six stages you are actually stuck on
What it does not
- Code you or your assistant added — the product you are building on top is yours to debug
- Accounts and bills that belong to someone else: Cloudflare, Polar, your domain registrar
- Teaching programming, or reviewing a feature you designed
- Building it for you — there is no done-for-you tier, and this is not one by the back door
Never send a secret. Not an API token, not a password, not the contents of .dev.vars. Nothing in support needs one, and pnpm support is written so that it cannot include one by accident.
Support is included for the lifetime of the product, at no extra cost and with no separate tier to buy.