Bugb Logo
Menu

Seven routes, one for each kind of question

Get help from the right place, first time.

Find what you’re trying to do. Each route goes straight to the people or pages that handle it.

Learn how something works

Installing, configuring and running Bravos, GuardLink and Cert-X-Gen.

Each product’s section opens with a get-started guide, then concepts, guides and reference. Everything is on docs.bugb.io.

Sort out my account, licence or billing

Your licence and its status, deployment keys, team members, billing details and invoices.

Signing in for the first time creates your account. If your Bravos server refuses writes, your licence page and your deployment keys page usually name the cause before you need us. How licensing works.

Report a bug in GuardLink or Cert-X-Gen

Both are open source, so bugs go where the code lives and you can follow the fix.

Include the version, your operating system, the command you ran, what you expected and what happened. For questions rather than bugs, use GuardLink discussions or Cert-X-Gen discussions. If the bug lets someone do something they shouldn’t, it’s a vulnerability: report it privately.

Report a bug in Bravos

Bravos has no public issue tracker, so tell us directly.

Say whether it happened in the CLI, the server or CI, which version you ran, and what the run printed. Remove secrets and customer data from logs before you send them.

Report a security vulnerability

In any Bugb website, service or product, GuardLink and Cert-X-Gen included.

security@bugb.report
Read the vulnerability disclosure policy

Send it privately, by email. Never in a public GitHub issue, a discussion, Discord or the support form, where anyone can read it before it’s fixed. We don’t run a paid bug bounty.

Found a vulnerability in someone else’s software? We can help you disclose it.

Buy Bravos or talk about a plan

Pricing, multi-seat licences, enterprise terms and threat-model previews.

A single seat doesn’t need a conversation: it’s on the pricing page. Multi-seat licences are agreed with a contract.

Ask other users

Questions, ideas and what people are building with Bugb tools.

The Bugb team reads both, but everything there is public. Keep secrets, customer data and security issues out.

Not sure where your question goes? Email info@bugb.report and we’ll pass it on.