Feedback, questions, and support
Email works best right now. If you include a little context, we can usually respond much faster.
[email protected]Quick actions
Prefer to email manually? Send to [email protected] .
What to include
Bugs
Steps to reproduce, what you expected, what happened, and a screenshot if possible.
Feature requests
The outcome you want, why it matters, and how you'd measure success.
Questions
Where you got stuck, links to docs, and any relevant error messages.
Security
High-level summary first. If it's sensitive, keep details minimal until we confirm a safe channel.
Common questions
A couple of quick answers for the things people usually ask first.
Do you have a public issue tracker?
Not yet. For now we're keeping support simple: email works best and helps us iterate quickly. If you'd like a public tracker, tell us. It's a common request.
How fast do you reply?
We try to respond quickly, but the best way to get a fast answer is to include steps, context, and a screenshot. If it's urgent, say so in the subject line.
Can you build something custom for us?
Often, yes, within reason. If it aligns with the product direction, we'll usually fold it into the core roadmap so you're not maintaining a one-off forever. Send details and we'll tell you quickly if it's a good fit.
Tip
If you're reporting a bug, include your browser + OS, and whether it happened in dev or prod environment. That alone can save a bunch of back-and-forth.