Can an agent push to production?

No. Agents open draft pull requests. A person approves every merge.

Where are credentials kept?

In your own secret store. None are kept in the repository.

Does Realized.dev hold certifications?

No. SOC 2, ISO 27001 and ISO 42001 inform our practices. Mapped · not certified or audited.

Is there a kill switch?

No. Control comes from human-approved merges and reverting a merge.

Does our data leave our environment?

The work runs in your repositories and toolchain; we host no runtime or model.

Reference · Security & deployment

Security & Deployment Reference

Where the controls sit, where the work runs, what the audit trail is, and the limits of what we claim.

Last updated 12 October 2026

Threat model, in brief

The main risks with coding agents are unreviewed changes, excessive permissions, leaked credentials and goals hijacked by untrusted input. Our answer is structural: agents work inside your toolchain, through typed tools, and only open draft pull requests. The full control map is on the Security page.

Control boundaries

Policy checks outside the model: Checks run in the harness, not inside a prompt.
Typed tool calls: Actions against systems of record go through typed, permissioned tools, designed to avoid free-form writes.
No credentials in the repository: Secrets stay in your own secret store.
Human-approved merges: Agents open draft pull requests. A person approves every merge.
Rollback: Revert the merge.

Deployment

The work runs in your own repositories and toolchain, using Cursor and the models you bring. Realized.dev hosts no runtime and no model, so your code and data stay where they already are.

Audit trail

Your Git history and pull request reviews: who proposed each change, which tests ran, and who approved the merge.

Framework mapping

Mapped · not certified or audited. A control map, not an assessment.

Framework	How it relates
OWASP Agentic Top 10 (2026)	Risks mapped to controls.
EU AI Act Art. 12 + 14	Record-keeping via Git history; human oversight via human-approved merges.
SOC 2, ISO 27001, ISO 42001	Inform our practices.

See the full compliance map

What we don't claim

SOC 2, ISO 27001 and ISO 42001: Mapped · not certified or audited.
There is no Stop Button, kill switch or cryptographically signed audit log.
We do not host your runtime, models or data.
The control map is not a legal or regulatory assessment.

Questions

Can an agent push to production?: No. Agents open draft pull requests. A person approves every merge.
Where are credentials kept?: In your own secret store. None are kept in the repository.
Does Realized.dev hold certifications?: No. SOC 2, ISO 27001 and ISO 42001 inform our practices. Mapped · not certified or audited.
What is the audit trail?: Your Git history and pull request reviews.
Is there a kill switch?: No. Control comes from human-approved merges and reverting a merge.
Does our data leave our environment?: The work runs in your repositories and toolchain; we host no runtime or model.

Want to walk through the controls for your environment?

Book the 90-minute workshop Architecture Guide