Design partners
We're working with a small group of AWS and Linear teams to validate LoopProof before general availability. Design partners shape the product and get direct access to the founding team.
The record starts when you connect.
Audit evidence cannot be backfilled
The record of how a finding was handled starts when you connect. LoopProof imports your open findings, but it cannot reconstruct what was done to them before.
Your audit date decides what ships first
Design partners tell us when their next audit is. Features that give you evidence sooner ship before features that do not. That is how the roadmap is ordered.
The downside is small and reversible
No agent to install in your account. No code change to your application. The connector is one Terraform module. If LoopProof does not solve the problem, remove the module and stop.
All shipped capabilities
Findings in, tickets out, resolution written back, the record and the web app: everything that is live today.
What's available today, what's on the 2027 roadmap
Every capability carries its status tag wherever it appears on this site. The source of truth is the roadmap.
| Capability | Description | Status |
|---|---|---|
| Findings in | GuardDuty and Inspector findings at High and above, from every account and Region you connect. | Shipped |
| Tickets out | One Linear ticket per remediation, not per finding, routed to the owning team, filed as the app. | Shipped |
| Resolution written back | LoopProof updates the finding in Security Hub as the work moves, so the two do not drift apart. | Shipped |
| The record | Every finding, ticket, resolution and accepted risk, with the raw event in S3, past the 90 days. | Shipped |
| The web app | Onboarding, people, settings, the audit trail and reports, in the browser. | Shipped |
| More finding sources | Security Hub CSPM and Exposure findings alongside GuardDuty and Inspector. | 2027 |
| The evidence export | The record packaged for an auditor to read, rather than read in the app. | 2027 |
| More trackers | Jira alongside Linear, if design partners need it. | 2027 |
| Notifications | A daily digest and hold alerts in Slack. | 2027 |
SaaS on AWS, engineering in Linear
The design-partner programme is a good fit if:
- Your engineering team uses Linear
- Security Hub is, or will be, enabled in your AWS accounts
- You manage infrastructure with Terraform
- You have a recurring obligation to show that specific findings were reviewed and handled
In the meantime: hello@loopproof.ai
What happens after you apply
Apply
Fill in the form above. We'll reach out if there's a fit.
Onboarding call
A call with the founding team. We walk through the connector Terraform module, your account structure and Linear setup.
Install the connector
Apply one Terraform module in your AWS account. LoopProof provisions your schema and begins forwarding findings.
First finding in Linear
High and Critical findings from GuardDuty and Inspector appear as Linear tickets.