Aproow
Sign up

Security

Your source code
stays on your machines.

ZERO CODE is the default. Aproow Cloud works from submitted QA evidence, while repository access and agent credentials stay in your Customer Trust Zone. Local analysis may use the API provider you choose.

Start freeExplore the security model

Free plan · Works with Claude Code and Codex and others

The default promise

The ZERO CODE boundary.

No repository source upload

No private source index in Cloud

No local Git credentials collected

No agent sign-ins or local API keys in Cloud

Architecture

Two places, and one narrow path between them.

Aproow Cloud

Understands the report.

Normalizes evidence, transcribes voice, structures observed vs. expected and suggests root cause — without customer source access by default.

  • Submitted evidence
  • Investigation
  • Plan metadata
  • Work events

Customer Trust Zone

Touches the code.

Your laptop, workstation, VM, VPC or CI runner. The customer coding agent reads the repository, history, tests and instructions under local permissions — and does the actual work.

  • Repository source
  • Git history
  • Tests and local instructions
  • Agent credentials
CloudYour Runtime
Task Packagebounded JSON · no source · no credentials

Connected only by the Task Package — a bounded JSON contract carrying the Investigation reference, observed / expected, reproduction, acceptance criteria and privacy policy.

Data boundary

What stays local under ZERO CODE.

Stays in your Trust Zone

  • Repository source, diffs and patches
  • Git history, private architecture and symbols
  • Coding-AI credentials and repository secrets
  • Raw test logs and absolute local paths
  • Private indexes, embeddings and retrieval traces

Never reaches Cloud under ZERO CODE

  • Your repository, in whole or in part
  • Unapproved snippets, diffs or raw private code metadata
  • Git or coding-AI credentials
  • Direct message content (excluded from AI & MCP)
  • Executable registry source from the UI Library

Privacy modes

Your code stays local.
You choose the exceptions.

ZERO CODE is the current default. Broader modes describe the policy scope; their detailed controls remain under specification.

ZERO CODEDefault
Submitted evidence and explicitly permitted derived reports. No raw repository source.
No source transit
METADATA
Repository structure, without file content.
No source transit
CONTROLLED SNIPPETS
Only the code excerpts explicitly allowed by your policy.
Scoped source transit
FULL
Broader repository context, only with explicit opt-in.
Explicit source transit

Aproow never silently switches from Protected to Managed planning. It does not permanently clone or index a repository by convenience, or reuse managed planning context as Cloud memory without a separate policy decision.

ZERO CODE protects repository source. Submitted screenshots, browser-session replay and narration are QA evidence sent to Cloud. DOM replay does not automatically mask sensitive page content; mark exclusions or text masking before recording.

Your keys

Bring your own provider.
Keep your privacy policy.

Enter coding and Project Intelligence API keys only in Runtime. They remain in your OS credential store; Web syncs worker and model names. Local analysis can send bounded repository context to your selected provider. Choosing a provider does not grant Aproow Cloud repository access.

Your planning model

Protected planning.
Managed is a separate path.

Protected / BYO plans through your paired Runtime. Managed / Easy is a separately authorised opt-in design; its broader rollout and source-transit controls remain outside the current MVP. Both use the versioned ImplementationPlan contract.

Stop losing context.
Start shipping.

Join small teams, founders and builders who use Aproow to keep their product moving.

Start free