Closed beta
If you're one of the three closed-beta design partners, you have a direct line: email [email protected] for anything broken, confusing, or worth a conversation. Response time during business hours (US Eastern) is typically under an hour. After hours, by morning.
Open beta waitlist
If you're on the open-beta waitlist (or want to join), keep an eye on your inbox — when the open beta opens we'll email you with onboarding instructions. To apply, head back to the home page and submit the form.
Bug reports
Maestro is open-source. The fastest path to a fix is filing an issue at github.com/mcinnisdev/Maestro/issues with:
- What you were trying to do.
- What actually happened (paste any error messages from the run timeline or Cloudflare Pages logs).
- Your install: dev (localhost) or self-host (which version).
For anything sensitive (security, customer data, billing-when-we-have-billing), email [email protected] directly.
What support won't cover (yet)
- SLAs. We're a one-person company in pre-launch. Guaranteed response times come with paid plans, which don't exist yet.
- Custom integrations beyond what's shipped. Skill authoring is documented at the skills overview; if you write a useful skill, we'd love a PR.
- Account-management questions before there are accounts. The closed beta is hand-onboarded; the open beta will have proper account flows.
Status
For real-time service status (when we have one), see status.letmaestro.com. Today everything runs on the design partner's own infrastructure (self-host) so "Maestro status" is "is your lab box up?"