Keep the doorway resilient
Cloud edge, local Anchor, and federation continuity in one steward surface.
Civweave
HOST NODE SETUP
Your cloud doorway is live. Now make it resilient.
This page belongs to the host steward, not ordinary Civweave visitors. It records this browser as a steward browser and keeps the local Anchor recommendation visible without blocking the campus.
Reading this host's deployment metadata…
CONNECT STEWARD PAYOUTS
Add your Stripe information.
Every Node Steward should connect the Stripe account that will receive this host's share of membership and commerce revenue. This is separate from any card or membership you use as a Civweave member.
Connect from the local Anchor's operator console. Civweave receives only the connected-account identifier and capability status; bank, identity, and tax details are entered in Stripe-hosted onboarding.
Start the local Anchor, open its operator controls, then choose Connect payouts. Steward earnings remain unavailable until Stripe reports transfer capability as active.
PLACE THIS HUB ON THE MESH
Stand where the hub lives.
Take this device to the physical place this hub serves, then sync. Civweave will ask for location only after you tap the button.
Rounded placement is the default: the exact reading stays on this device and only an approximately 100 m site position leaves it. If you explicitly enable the precise public pin above, Civweave sends the fresh coordinate at six decimal places together with the device's measured accuracy. The first successful sync pairs this steward browser for future location updates.
Waiting for the account Worker and starter nodes…
CLOUDFLARE DEPLOYMENT
Worker + three starter nodes
Civweave attempts this layer automatically during host creation and every automated deployment. Pages remains usable if it needs follow-up.
Reading account-edge deployment status…
WHY THE ANCHOR MATTERS
The Cloudflare host remains usable without a local Anchor. A local companion is strongly recommended because it can retain host identity and state for recovery, local-first services, and federation work even when the public edge is unavailable.