How we talk to users.
We do not have a Discord with 10,000 inflated members. We have email, GitHub Discussions, office hours, and direct access to engineering on Pro+ tiers. When we have enough active members for a Discord that stays warm, we’ll launch one.
Where to reach us today
3 live channels. Each one has a response-time commitment.
GitHub Discussions
LivePublic, searchable, indexable. Best for technical questions, feature requests, and "is anyone else seeing this?" threads. We answer in the open so the next person searching finds the answer.
Email ([email protected])
LiveBest for account-specific questions, billing, anything you don't want public. We answer within 1 business day on best-effort. Pro / Team / Enterprise tiers are planned (no billing system yet), and once those ship they'll have committed response times.
Office hours
LiveWeekly 30-minute slots. Talk to a founder. Bring a hard problem, a prompt that didn't work, or just an evaluation question. No pitch, no slides, no recording.
Not yet — and we’ll tell you why
Honest about what we’re skipping for now.
Design partner Slack
PlannedPlanned. A private Slack with the founders, opened when the first design partner signs. /factory/customers shows zero signed partners today, so this channel is reserved, not active.
Discord
PlannedNot yet. Most early-stage product Discords are graveyards with fake member counts. We'll launch one when we have enough active design partners that it stays warm without engineering doing all the talking.
X / Twitter
PlannedNot yet. We'll announce launches via the changelog feed first, and link to social only when we have a tweet that's worth amplifying. Following the changelog Atom feed is more reliable than checking X.
How we behave
- ✓We answer in the open when we can. Public answers in GitHub Discussions help the next person searching.
- ✓We acknowledge fast, even if the fix is slow.A real human replies within our SLA. No “we’ll get back to you” auto-templates.
- ✓We say “no” when something is out of scope.We’d rather say no honestly than fake a roadmap commitment we won’t honor.
- ✓We credit reporters. Security reports get a line on the hall of thanks; community contributors get acknowledged in the changelog.
Just write to us
Pick the channel above that fits the kind of conversation you want. If in doubt, email [email protected].