support

where to ask

• community discord— open to everyone. fastest path for "how do i…" questions; expect informal answers from the team + community within an hour or two on Flanders business hours. invite link lands at public-beta open on 2026-05-21; until then ping the team via email below.
• github issues code.konnos.org/flndrn/briven — bug reports + reproducible defects. include the build sha from the dashboard footer and the relevant audit-log entries (sanitised — see below).
• email support@flndrn.com — for paid customers; include your project id and the rough time of the issue. response targets per tier are on the SLA card in your billing dashboard.
• status page docs.briven.tech/status — check here first if invocations are failing platform-wide.

what to include in a bug report

1. build sha— bottom-right of the dashboard footer. pins which release you're on so we can correlate with deploy_history.
2. project id (p_…) and approximate time of the failure (UTC).
3. what you did — exact steps. for invocations, the function name and a sanitised version of the args.
4. what you expected vs what you saw — paste any error text verbatim. error codes (the code field) are stable; the message text drifts.

don't paste

• api keys (brk_…). if you suspect one leaked, revoke it in the dashboard immediately; we'll never ask for a plaintext key over support.
• polar customer ids / payment-method ids — share the project id instead.
• real personal data from your own customers when you can avoid it. for repro, fabricate a single row that triggers the issue.

security disclosures

report security issues to security@flndrn.com — encrypted reports welcome (PGP key on /trust). target acknowledgement is within one business day; we will not pursue legal action against good-faith research that follows the standard disclosure flow.

response targets by tier

free

community-only; best-effort within ~48h via discord / github

pro

email support, 48h target

team

priority email + 99.5% SLA, 24h target on outages