[EPIC] Hosted service: resilient, multi-instance, multi-tenant deployment #1821
Notifications
Due Date
No due date set.
Depends on
#1825 NATS: clustered deployment
sam/archie
Reference: sam/archie#1821
Reference in new issue
Block a user
Archie is to be offered as a hosted service behind one public GitHub App, with a resilient load balancer and many instances. This epic holds the design discussion and the work it produces.
Open questions (maintainer):
Constraints found in the code:
Already in place: orgs as the tenant boundary (Cedar policies, org-scoped credentials, task grants), NATS work queue, Postgres as the system of record.
Sequencing: items that also harden self-hosted installs (owner failover, scheduler split, NATS cluster) can land before 1 December; hosted-only items (tenant isolation, installation routing #1820) after, unless launch moves earlier.
Done when the open questions are decided and every item below is closed or deliberately deferred.
Items: #1822 decision (launch scale, platform), #1823 State Store and Gateway instances, #1824 archied coordination split, #1825 NATS cluster, #1826 webhook intake behind the LB, #1827 tenant isolation, #1820 GitHub App installation routing.
sam referenced this issue2026-11-12 04:53:47 +00:00