All durable messaging for this product is NATS JetStream, not Zapier queues and not a public TCP API.
Three nats-server -js nodes form the Verae cluster
(routes between them, JetStream replication). Clients (middleware,
poller, aggregator, WORM, tree nodes, and any new process cloned from
verae-nats-process) connect with a cluster URL
list, for example:
nats://127.0.0.1:4222,nats://127.0.0.1:4223,nats://127.0.0.1:4224On a given machine the listener stays on loopback
(or a private interface). Operators reach it with
scripts/nats-tunnel.sh /
ssh -L 14222:127.0.0.1:4222. Do not bind 4222 on
0.0.0.0 without auth.
Today’s NS1 box (NS1.GEORGELAMBERT.ORG,
70.88.205.138) already runs JetStream on
127.0.0.1:4222. The target is three
clustered nodes so losing one server does not lose the stream. Fleet SSH
hosts (ns1, later lan-134) run
workers, not extra public NATS listeners.
| Allowed | Forbidden |
|---|---|
verae-middleware, fleet workers, WORM, tree nodes,
verae-nats-process clones |
Zapier cloud, browsers, zappier-edge |
| Address | Kind | Notes |
|---|---|---|
verae.zapier.jobs.watch |
work queue | poller |
verae.zapier.jobs.events |
events | wait + webhooks |
verae.zapier.webhooks.deliver |
work queue | HTTPS to Zapier REST Hook |
verae.zapier.usage |
optional | metering |
verae.archive.put |
JetStream | splitter / merkle builder |
verae.archive.query |
broadcast (no queue group) | every WORM and tree node |
verae.archive.reply.<correlationId> |
replies | only on bloom hit |
New functions get new
verae.<area>.<resource>.<action>
addresses — see 06-address-routing.md.