ControlQuayby ISAGOLet’s talk SECURITY & COMPLIANCE, IN CONTEXT
Your next security review shouldn’t start with a search through scattered folders.
Give controls, evidence and policy decisions a shared home—with a record your team can explain.
Discuss your team’s needs For small B2B software teams · In development ControlQuay / Acme SoftwareEXAMPLE WORKSPACEEVIDENCE OVERVIEW
| Control | Owner | Evidence status |
|---|---|---|
| Source-code access review | Engineering | Reviewed |
| Incident response policy | Operations | Needs review |
| Backup verification | Engineering | Missing |
New evidence starts a new review. Earlier decisions stay with the record they describe.
Clear ownership
Versioned evidence
Recorded decisions
↓THE REASON WE’RE BUILDING
A customer asks how access is reviewed. You have a policy, a spreadsheet and an approval somewhere in a chat. The hard part is connecting them.
ControlQuay is being built to connect each requirement to its owner, supporting evidence and review history. So “we do this” becomes a record you can follow.
ONE CONNECTED WORKFLOW
Explore a fictional example of the workflows implemented in our development version.
Define the requirement, assign a team member and set a due date. Record why a control applies—or why it doesn’t.
Changes to the control create a new revision and call for fresh supporting evidence.
Keep source details, observation dates and evidence versions together. Preview supported CSV and JSON imports before confirming them.
Expired evidence is marked stale. A new upload needs its own review.
An authorised reviewer records a decision and rationale against the specific evidence version. Export the record with its history and unresolved items.
A review is a team decision—not an independent audit or certification.
Draft, compare and approve versions. Record acknowledgments against the exact policy each member read.
A FOCUSED FIRST RELEASE
We’re building a practical starting point for small software teams preparing for customer security reviews and organising compliance evidence.
Customer deployment and full release validation are still ahead.
These capabilities are planned. They are not available as completed features today.
BEFORE WE TALK
Small B2B software teams that need to organise security requirements, evidence and policy decisions—particularly when customer security reviews expose gaps in ownership or documentation.
ControlQuay is in development. You can discuss your requirements and request a walkthrough. Customer access depends on the supported scope, deployment and validation; we are not offering instant production access.
Not yet. The development version supports manual text evidence and CSV / JSON imports. Live integrations and recurring checks are next in development. We will confirm supported systems before agreeing to an evaluation.
We plan to use AI to assist with policy drafts and evidence-gap suggestions, with source references and human review. AI assistance has not yet been implemented, and it will not be presented as an auditor or automatic compliance approval.
Pricing has not been finalised. We will define the supported scope, hosting needs and price before any paid evaluation. Requesting a conversation creates no purchase commitment.
The link opens an email to our team. Tell us which systems you use and what evidence work is difficult. We will discuss fit, demonstrate the available workflows and identify any gaps before proposing next steps.
LET’S START WITH YOUR TEAM
Tell us where the evidence work gets stuck. We’ll discuss whether ControlQuay’s first release fits your team.
Request a walkthrough [email protected]An initial conversation. No purchase commitment.