Enterprises keep using the hosted dashboard but deploy an execution gateway inside their own network, attached to their org. Their runners execute there, under strict DLP and exfiltration controls, so task data, repositories and secrets never leave the customer network; only the control metadata the dashboard needs crosses back.
Open questions for the maintainer: attachment scope (org vs instance, leaning org), which data may cross back (status, logs, diffs?), and how egress policy is expressed (Cedar policy vs gateway config).
Done when: a design states the trust boundary, the outbound-only connection model, and the data classes that cross it.
Imported from beads archie-core-1gm08 · GitHub #1803 · type feature · priority P2 · created 2026-10-18
Enterprises keep using the hosted dashboard but deploy an execution gateway inside their own network, attached to their org. Their runners execute there, under strict DLP and exfiltration controls, so task data, repositories and secrets never leave the customer network; only the control metadata the dashboard needs crosses back.
Open questions for the maintainer: attachment scope (org vs instance, leaning org), which data may cross back (status, logs, diffs?), and how egress policy is expressed (Cedar policy vs gateway config).
Done when: a design states the trust boundary, the outbound-only connection model, and the data classes that cross it.
---
_Imported from beads `archie-core-1gm08` · GitHub #1803 · type feature · priority P2 · created 2026-10-18_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Enterprises keep using the hosted dashboard but deploy an execution gateway inside their own network, attached to their org. Their runners execute there, under strict DLP and exfiltration controls, so task data, repositories and secrets never leave the customer network; only the control metadata the dashboard needs crosses back.
Open questions for the maintainer: attachment scope (org vs instance, leaning org), which data may cross back (status, logs, diffs?), and how egress policy is expressed (Cedar policy vs gateway config).
Done when: a design states the trust boundary, the outbound-only connection model, and the data classes that cross it.
Imported from beads
archie-core-1gm08· GitHub #1803 · type feature · priority P2 · created 2026-10-18