90-second safety demo

Let agents work with real databases — without blind production access.

Watch an agent request a money-related change. Synapsor scopes the read, blocks the direct write, and stages a reviewable proposal with evidence.

Run safety demo View docs

Demo uses safe mock Postgres/MySQL-style data. No real credentials required.

Agent request

Waive the $55 late fee for Acme Robotics.

Money-related update · $55 request · approval required above $50

ReadyRisk: Not assessedProduction unchanged

Outcome paths

Start with the human-review path.

The default shows the full safety loop: governed read, direct write blocked, proposal staged, approval required, replay saved.

Step 1 of 9 — Customer request received

The agent asks to waive a $55 late fee.

Live run graph

Branch graph: main unchanged, Synapsor review branch staged

The graph separates the unchanged production lane from the Synapsor review branch lane so the branching behavior is visible as the run advances.

Trigger

The workflow uses AUTO BRANCH ON PROPOSAL, so a requested write forks into Synapsor review state.

Main lane

Production/main stays unchanged during review.

Review branch

Synapsor auto-creates a review branch for the proposed diff, evidence, approval state, and replay.

Decision

Green-lane updates can become worker-ready; $55 and riskier changes stay held for review.

Plain English

The branch is Synapsor-owned change-control state: proposed row diff, evidence, approval status, writeback handoff, and replay. The model never gets direct write authority.

1. Main/source stays unchanged2. Synapsor forks a review branch3. Approval/policy decides handoff

Source/main laneSynapsor review branch lane

Loading safe-write run graph...

The static path below mirrors the interactive graph while the canvas initializes.

Request
Agent asks
The agent asks to answer or change money-related support data.
Session
Trusted scope
Tenant, principal, and ticket ID are backend-bound.
Evidence
Approved rows
Synapsor returns only governed rows and policy facts.
Policy
Decision gate
Deterministic rules decide read-only, proposal, review, or block.
Source
Main stays unchanged
The production table is not updated while the review branch exists.
Auto branch
Synapsor review branch
AUTO BRANCH ON PROPOSAL forks a Synapsor branch that holds the diff, evidence, approval state, and replay record.
Review
Human approval required
A reviewer approves or rejects the branch before worker handoff.
Writeback
Trusted worker boundary
Approved changes are applied later by your backend worker, not the read-only connector.
Replay
Run record
Synapsor links source state, branch diff, approval state, writeback status, and replay.

Request

Agent asks

The agent asks to answer or change money-related support data.

Session

Trusted scope

Tenant, principal, and ticket ID are backend-bound.

Evidence

Approved rows

Synapsor returns only governed rows and policy facts.

Policy

Decision gate

Deterministic rules decide read-only, proposal, review, or block.

Source

Main stays unchanged

The production table is not updated while the review branch exists.

Auto branch

Synapsor review branch

AUTO BRANCH ON PROPOSAL forks a Synapsor branch that holds the diff, evidence, approval state, and replay record.

Review

Human approval required

A reviewer approves or rejects the branch before worker handoff.

Writeback

Trusted worker boundary

Approved changes are applied later by your backend worker, not the read-only connector.

Replay

Run record

Synapsor links source state, branch diff, approval state, writeback status, and replay.

Synapsor workflow map

What Synapsor coordinates

Same database, different agent outcomes. Synapsor owns the safety state around the read, policy decision, proposal, approval, replay, and worker handoff.

1. Agent requestWaive a money-related fee
The agent asks to change customer data, but it does not get database access.
Synapsor safety boundary
1. 2. Bind trusted session
  tenant, principal, ticket ID
2. 3. Read governed evidence
  approved rows and fields
3. 4. Apply policy
  $50 threshold and risk rules
Selected outcome
Read-only answer
Auto-settled proposal
Human-review proposal
Selected
1. 1Direct write blocked
2. 2Proposal staged
3. 3Human review required
Blocked request

Always enforced: No raw SQL to model · No DB credentials to model · Tenant scope server-bound · Fields filtered · Write policy applied

What Synapsor did

Current proof

Allowed

Customer: Acme Robotics
Ticket: T-1042
Request: Waive $55 late fee
Source: Seeded support record

Outcome

Policy active

Synapsor is enforcing the database boundary before the agent can see context or propose changes.

Tenant: demo_tenant
Read limit: applied
Suggested review fields: withheld

View full run trace · 9 events

Demo takeaway

Agents get useful context. Operators keep control.

Request Builder Trial See existing DB setup

Synapsor

Public demoGet access

Public demo

Preparing safe database demo...

Loading the agent timeline, policy checks, and approval workflow.

Synapsor

Public demoGet access

90-second safety demo

Let agents work with real databases — without blind production access.

Watch an agent request a money-related change. Synapsor scopes the read, blocks the direct write, and stages a reviewable proposal with evidence.

Run safety demo View docs

Demo uses safe mock Postgres/MySQL-style data. No real credentials required.

Agent request

Waive the $55 late fee for Acme Robotics.

Money-related update · $55 request · approval required above $50

ReadyRisk: Not assessedProduction unchanged

Outcome paths

Start with the human-review path.

The default shows the full safety loop: governed read, direct write blocked, proposal staged, approval required, replay saved.

Step 1 of 9 — Customer request received

The agent asks to waive a $55 late fee.

Live run graph

Branch graph: main unchanged, Synapsor review branch staged

The graph separates the unchanged production lane from the Synapsor review branch lane so the branching behavior is visible as the run advances.

Trigger

The workflow uses AUTO BRANCH ON PROPOSAL, so a requested write forks into Synapsor review state.

Main lane

Production/main stays unchanged during review.

Review branch

Synapsor auto-creates a review branch for the proposed diff, evidence, approval state, and replay.

Decision

Green-lane updates can become worker-ready; $55 and riskier changes stay held for review.

Plain English

The branch is Synapsor-owned change-control state: proposed row diff, evidence, approval status, writeback handoff, and replay. The model never gets direct write authority.

1. Main/source stays unchanged2. Synapsor forks a review branch3. Approval/policy decides handoff

Source/main laneSynapsor review branch lane

Loading safe-write run graph...

The static path below mirrors the interactive graph while the canvas initializes.

Request
Agent asks
The agent asks to answer or change money-related support data.
Session
Trusted scope
Tenant, principal, and ticket ID are backend-bound.
Evidence
Approved rows
Synapsor returns only governed rows and policy facts.
Policy
Decision gate
Deterministic rules decide read-only, proposal, review, or block.
Source
Main stays unchanged
The production table is not updated while the review branch exists.
Auto branch
Synapsor review branch
AUTO BRANCH ON PROPOSAL forks a Synapsor branch that holds the diff, evidence, approval state, and replay record.
Review
Human approval required
A reviewer approves or rejects the branch before worker handoff.
Writeback
Trusted worker boundary
Approved changes are applied later by your backend worker, not the read-only connector.
Replay
Run record
Synapsor links source state, branch diff, approval state, writeback status, and replay.

Request

Agent asks

The agent asks to answer or change money-related support data.

Session

Trusted scope

Tenant, principal, and ticket ID are backend-bound.

Evidence

Approved rows

Synapsor returns only governed rows and policy facts.

Policy

Decision gate

Deterministic rules decide read-only, proposal, review, or block.

Source

Main stays unchanged

The production table is not updated while the review branch exists.

Auto branch

Synapsor review branch

AUTO BRANCH ON PROPOSAL forks a Synapsor branch that holds the diff, evidence, approval state, and replay record.

Review

Human approval required

A reviewer approves or rejects the branch before worker handoff.

Writeback

Trusted worker boundary

Approved changes are applied later by your backend worker, not the read-only connector.

Replay

Run record

Synapsor links source state, branch diff, approval state, writeback status, and replay.

Synapsor workflow map

What Synapsor coordinates

Same database, different agent outcomes. Synapsor owns the safety state around the read, policy decision, proposal, approval, replay, and worker handoff.

1. Agent requestWaive a money-related fee
The agent asks to change customer data, but it does not get database access.
Synapsor safety boundary
1. 2. Bind trusted session
  tenant, principal, ticket ID
2. 3. Read governed evidence
  approved rows and fields
3. 4. Apply policy
  $50 threshold and risk rules
Selected outcome
Read-only answer
Auto-settled proposal
Human-review proposal
Selected
1. 1Direct write blocked
2. 2Proposal staged
3. 3Human review required
Blocked request

Always enforced: No raw SQL to model · No DB credentials to model · Tenant scope server-bound · Fields filtered · Write policy applied

What Synapsor did

Current proof

Allowed

Customer: Acme Robotics
Ticket: T-1042
Request: Waive $55 late fee
Source: Seeded support record

Outcome

Policy active

Synapsor is enforcing the database boundary before the agent can see context or propose changes.

Tenant: demo_tenant
Read limit: applied
Suggested review fields: withheld

View full run trace · 9 events

Demo takeaway

Agents get useful context. Operators keep control.

Request Builder Trial See existing DB setup

Let agents work with real databases — without blind production access.

Waive the $55 late fee for Acme Robotics.

Start with the human-review path.

Branch graph: main unchanged, Synapsor review branch staged

What Synapsor coordinates

Read-only answer

Auto-settled proposal

Human-review proposal

Blocked request

Current proof

Policy active

Agents get useful context. Operators keep control.

Preparing safe database demo...

Let agents work with real databases — without blind production access.

Waive the $55 late fee for Acme Robotics.

Start with the human-review path.

Branch graph: main unchanged, Synapsor review branch staged

What Synapsor coordinates

Read-only answer

Auto-settled proposal

Human-review proposal

Blocked request

Current proof

Policy active

Agents get useful context. Operators keep control.