Contact
Talk to us
One inbox, one GitHub org, one docs site. There is no support tier to buy, no ticket queue to be triaged into, and no contact form that quietly routes you into a sales sequence. Email reaches the people who build Quonfig.
Channels
Four ways to reach us
Email us
hello@quonfig.com
Product questions, evaluations, migrations, and billing and account changes. If you are not sure where something belongs, it belongs here. Security reports go to security@quonfig.com.
Open an issue on GitHub
github.com/quonfig
The SDKs, the OpenFeature providers, and the qfg CLI live here. Bug reports and feature requests are genuinely welcome as issues on the repo they affect.
Read the docs
docs.quonfig.com
SDK guides for every supported language, the qfg CLI reference, and the configuration concepts. Most “how do I…” questions are answered here faster than we can answer them.
Check service status
status.quonfig.com
Live uptime for the app, config delivery, and telemetry, plus incident updates while we work on them. Check here first if something looks down, and subscribe for notifications.
What to expect
Engineers read the inbox
Everything sent to hello@quonfig.com is read by people who work on the product, so the person who answers you is usually the person who can fix the thing you are writing about. That cuts out the layer where a support agent relays your question to engineering and relays a guess back.
You can help us skip a round trip. Tell us what you were doing, what you expected, and what actually happened. If it is an SDK question, include the language and the version you are on. If it is about a specific flag or config value, include your workspace slug and the key — never paste an API key, a secret value, or an encryption key into an email.
Mail is read by the founders, and the reply comes from a person, not an autoresponder.
Where do I…
Pointers for the common cases
- Report a bug
- Open an issue on the repo it affects at github.com/quonfig — the SDK, the provider, or the CLI. Include the version, a minimal reproduction if you have one, and what you expected instead. If the bug is in the app or in delivery rather than in a package, email us.
- Ask how something works
- Start at docs.quonfig.com. If the docs do not answer it, email hello@quonfig.com and tell us which page you were on when you gave up — that is a docs bug on our side, and we would like to fix it.
- Request a feature or an SDK
- A GitHub issue is the best home for it, because other people can find it and add their case. Email works too, especially if you would rather not describe your use case in public.
- Report a security issue
- Email security@quonfig.com, and please do not open a public issue for a suspected vulnerability. We will confirm that we received it and keep you updated while we work on a fix. Our machine-readable contact is at quonfig.com/.well-known/security.txt. We do not currently run a bug bounty program.
- Sort out billing or your account
- Email hello@quonfig.com from the address on the account, and include your workspace slug. Plan changes, invoices, seat counts, and cancellations all go to the same place.
- Ask about data, privacy, or terms
- The Privacy Policy covers what we collect and how it is used, and the Terms of Service covers the rest. To access, export, or delete your data, follow the Data Deletion and Access Requests section of the Privacy Policy — we complete verified requests within 30 days. Anything else — data processing agreements, subprocessors, or where your config is stored — goes to hello@quonfig.com.
Quonfig is operated by MHW Works LLC. See the Privacy Policy and Terms of Service, or read more about who we are and why we build this.
Or just try it
Most questions answer themselves once your config is a git repo you can read. Start in under 5 minutes.