Talk to the Bracework team.
Bracework is invited-gated for teams running dozens of internal services. The form below reaches the same engineer who drafts the Monday digest — no SDR, no qualification round, no calendar link in the first message.
A short note on the portfolio, your CI, and what would change for your on-call rotation is enough. We’ll come back within one business day.
Prefer email? bracework-2@polsia.appA pilot on the right tier, not on a sales call.
Most engineering orgs land on Team. Fund a pilot there; bump the repo count once the nightly cadence is in steady state and switch tiers in a single click if you cross twenty. If you’re past fifty repos or need custom severity controls, Scale is shaped to the call — one sizing conversation, no qualification round.
- Use the form when
You want a pilot scoped against an actual repo portfolio.
A short note on company, repo count, and the advisory/dependency headaches you’d start with is enough — we’ll come back within one business day.
- Use email when
You have a procurement document ready to share.
The form keeps a name + work email + short message in a single row; longer intake belongs in your inbox rather than crammed into a textarea.
- Response time
Within one business day, from an engineer.
The reply comes from the same engineer who drafted the cut-line — no SDR, no canned sequence, no calendar link in the first message.
Vulnerabilities in Bracework itself, reported directly to the team.
If you’ve found a security issue in the Bracework runtime — the triage engine, the GitHub App install flow, the API endpoints, or the auth surface — we want to hear about it before any vendor advisory does. The disclosure channel below routes straight to the engineering leads and bypasses the contact-form intake table.
Do not submit sensitive details through the contact form on this page.
The contact form above is stored as a plain row in our intake table — the same row any inquiry lands in. For a vulnerability report, send the details to the address below so the engineering team can encrypt the reply with your PGP key before any code-level follow-up. Paste the bare advisory + reproduction steps in the first message; we’ll request extras after acknowledgement.
- Report channel
bracework-2+security@polsia.app
Sub-addressed to our team inbox, so it lands alongside general correspondence but is filterable by routing rule.
- Acknowledgement
Within one business day of receipt.
First message back is human, confirms reproduction status, requests your PGP key if you haven’t included one, and sets a fix timeline.
- Scope
The Bracework App, API, and triage engine.
Out of scope: your own dependency advisories (those belong in
/audit) or third-party libraries Bracework merely inspects.
Before you write the note.
The four questions that show up in nearly every first message — answered up front so the reply can skip the basics and dive into your repo portfolio.
Three plans. Per repo, not per seat.
If the repository count and the expected advisory volume fit a published tier, the fastest path is a Subscribe button on the pricing page — no contact form, no qualification round, the first nightly cadence starts the same week.