Use the support route that protects your information.
BoundaryCI provides reasonable-effort support for the open-source scanner and Cloud subscriptions. Never include credentials, customer data, or proprietary migrations in a public report.
Product help and reproducible bugs
Use GitHub Issues in the public sir-gig/boundaryci repository for installation problems, documentation questions, sanitized reproductions, feature requests, and feedback about an AI-generated finding.
Include the BoundaryCI version, operating system, command, sanitized output, and smallest safe reproduction. The latest tagged release is the supported open-source version.
Billing and subscription help
Use the support contact displayed by Stripe Checkout or on the Stripe receipt for payment-specific questions. Use Manage billing inside BoundaryCI Cloud for invoices, payment methods, plan changes, and cancellation.
A refund and subscription cancellation are separate actions. Include only the organization name and invoice date in an initial request; do not send complete card details, authentication codes, or Stripe credentials.
Security vulnerabilities
Do not open a public issue for a suspected vulnerability. Use GitHub's private vulnerability-reporting feature for the sir-gig/boundaryci repository and follow SECURITY.md.
Include the affected version, reproduction conditions, impact, and a safe contact method. Do not include live credentials or unrelated customer information.
Support scope
Paid plans provide the capacity displayed at Checkout but do not include a guaranteed response time, uptime commitment, incident-response service, or service-level agreement unless a separate Enterprise agreement states otherwise.
Growth and Enterprise requests are prioritized when practical. Fireworks account access, availability, and billing remain the responsibility of Fireworks support.