Reference · Connector modes

Five modes, so you always know what it can touch

Every Verigence connector runs in exactly one mode. The mode tells you what it can read, what it can write, and what happens when it can't. State is always shown with an icon, a label, and a color.

Demo

Fully simulated. The connector contacts no external system; reads and writes hit mock data. Use it for walkthroughs, sales demos, and operator training with zero risk.

reads: mockwrites: mockprod data: never

Sandbox

Connected to a non-production environment that mirrors the real system's shape. You validate reads, mappings, errors, and gated write behavior without touching production data.

reads: testwrites: testprod data: never

Live

Connected to production. Reads run as needed to inform the call; healthcare PHI and writes also require BAA, product eligibility, tenant approval, and operator gates before they commit. This is the only mode that can touch production data.

reads: livewrites: gated by approvalprod data: yes

Degraded

Partially available — for example outbound-only, rate-limited, or read-only because of an upstream issue. The specific limitation is shown explicitly so operators know what they can and can't rely on.

capability: partiallimit: shown

Unavailable

Not reachable — expired auth, an outage, or a revoked credential. Dependent actions are blocked and surfaced, never retried silently. The call can still proceed and escalate to a human.

reachable: noactions: blocked + surfaced

Promoting a connector safely

You don't jump to live. Connectors graduate, and healthcare PHI/writeback can stay blocked at any step.

01
Start in sandbox
Prove the workflow against a non-production environment.
02
Pilot with approvals
Promote only after BAA/product/tenant gates pass; every write remains operator-gated.
03
Scale with confidence
Expand volume; keep the gate, watch the evidence trail.

See modes in the demo

The connector panel in the demo shows live, sandbox, and degraded side by side.

Open the demo

See modes in the demo

Live · sandbox · degraded

Demo

Reference · Connector modes

Five modes, so you always know what it can touch

Every Verigence connector runs in exactly one mode. The mode tells you what it can read, what it can write, and what happens when it can't. State is always shown with an icon, a label, and a color.

Demo

Fully simulated. The connector contacts no external system; reads and writes hit mock data. Use it for walkthroughs, sales demos, and operator training with zero risk.

reads: mockwrites: mockprod data: never

Sandbox

Connected to a non-production environment that mirrors the real system's shape. You validate reads, mappings, errors, and gated write behavior without touching production data.

reads: testwrites: testprod data: never

Live

reads: livewrites: gated by approvalprod data: yes

Degraded

capability: partiallimit: shown

Unavailable

Not reachable — expired auth, an outage, or a revoked credential. Dependent actions are blocked and surfaced, never retried silently. The call can still proceed and escalate to a human.

reachable: noactions: blocked + surfaced

Promoting a connector safely

You don't jump to live. Connectors graduate, and healthcare PHI/writeback can stay blocked at any step.

01
Start in sandbox
Prove the workflow against a non-production environment.
02
Pilot with approvals
Promote only after BAA/product/tenant gates pass; every write remains operator-gated.
03
Scale with confidence
Expand volume; keep the gate, watch the evidence trail.

See modes in the demo

The connector panel in the demo shows live, sandbox, and degraded side by side.

Open the demo

See modes in the demo

Live · sandbox · degraded

Demo