Separate Zapier, web, API, and leaf access planes with NATS authz
Some checks are pending
offline / test (push) Waiting to run

Zapier is one ingress. Direct web, customer API, and S2S leaf nodes are their own services. Every hop to an internal subject must pass verae.access.authz.check (default deny by plane).
This commit is contained in:
George Lambert 2026-09-11 16:05:05 -04:00
parent ac38676645
commit 1b199ca4d4
117 changed files with 2640 additions and 105 deletions

View file

@ -0,0 +1,3 @@
# NATS — verae-access-api
Plane `api`. Statement and jobs.watch after authz. No credits, no archive.

View file

@ -0,0 +1,3 @@
# verae-access-api
Direct customer API (`x-api-key`). Separate from Zapier Platform.

View file

@ -0,0 +1,3 @@
# NATS — verae-access-authz
`verae.access.authz.check` request-reply. Queue `access-authz`. Fail closed.

View file

@ -0,0 +1,3 @@
# verae-access-authz
Default-deny authorization step on the NATS address path. Planes: zapier, web, api, leaf, staff.

View file

@ -0,0 +1,3 @@
# NATS — verae-access-leaf
`verae.access.leaf.in` → authz.check → `verae.archive.*` / jobs.*. Denied: billing.

View file

@ -0,0 +1,3 @@
# verae-access-leaf
Server-to-server NATS leaf ingress. Archive and jobs only. Never billing.

View file

@ -0,0 +1,3 @@
# NATS — verae-access-web
Plane `web`. Authz then `verae.billing.statement.get` / `balance.adjust` kind=reload.

View file

@ -0,0 +1,3 @@
# verae-access-web
Direct customer web plane. Not Zapier. Statement + reload only after authz.

View file

@ -0,0 +1,3 @@
# NATS — verae-access-zapier
Plane `zapier`. Authz then jobs.watch / usage.recorded. Zapier cloud never connects to NATS.

View file

@ -0,0 +1,3 @@
# verae-access-zapier
Zapier Platform HTTPS plane only. No portal, no admin, no leaf.