Plan a zero-spend network

The current pilot has one possible existing local host, ten Google region candidates, zero confirmed cloud nodes and a $0 cash ceiling. The Google Cloud trial is available to claim. No active billing account, posted grant, regional capacity or checkout has been confirmed for this plan. The AWS Free offer has already been used. Its remaining budget is zero.

Run the plan locally

make build
bin/daedro-mcp-hub network plan --file configs/network-pilot.json --simulate 30

The command reads a local JSON file. It evaluates the plan against today's UTC date, emits JSON and exits. The shipped configuration selects only the local bootstrap scenario on equipment already owned, with existing power and connectivity and no additional committed infrastructure spend. Deselect the local host if that assumption does not hold. Power, ISP or new hardware costs require their own verification. The planner never signs up for an account, contacts a cloud API or creates a VM. Pilot configuration

The candidate slots are Council Bluffs (us-central1), Frankfurt (europe-west3), Tokyo (asia-northeast1), London (europe-west2), Sydney (australia-southeast1), Singapore (asia-southeast1), Paris (europe-west9), Mumbai (asia-south1), Toronto (northamerica-northeast2) and São Paulo (southamerica-east1). These labels describe Google regions, rather than the location of a customer or proof of a specific physical server. Compute Engine regions and zones

What the WAN simulation actually tests

The simulator connects each peer to deterministic neighbors and runs shortest-path message delivery with fixed synthetic link delays. With 30 peers and ten region labels, the healthy overlay reaches 30. Taking one site offline leaves 27 reachable survivors. The simulated partition reaches 15 from its first peer, and reconnecting restores reachability to all 30. These are deterministic software results. Real RTT, throughput, packet loss, cost and VM availability need a deployed probe.

Confirm the first Google slot

1. If the owner elects to enroll, check eligibility in the official Google Cloud console. Record the genuine Free Trial account type, remaining credit and expiry. The advertised welcome offer is $300 for 90 days for eligible new customers. An unupgraded Free Trial account stops its projects when time or credit runs out. Google can request a payment method and a temporary verification hold. Keep the paid upgrade disabled. Google Cloud trial rules
2. Start the plan with one public-edge probe in Council Bluffs. Verify the machine type, regional and global CPU/IP quotas, boot disk, backups, external IPv4, taxes, egress and any address or disk left behind after shutdown. Google lists a monthly e2-micro allowance shared across three eligible US regions, including Iowa. This allowance does not extend to ten international machines. Use the Free Trial's own no-charge boundary for this pilot. Compute allowance · Compute pricing
3. In a private copy of the config, set the Google account's availability to active, enter the actual remaining cents, verified region list, host quota and ISO expiry date. Set the four verification booleans only after checking the corresponding account conditions. Enter the complete regional monthly quote in integer USD cents and select that slot. Each quote requires compute, ipv4, storage, backup, traffic_reserve and tax_and_other. Zero means verified zero. An absent quote or component blocks selection.
4. Set a short run_until date for the first probe. Keep a shutdown margin in exit_days_before_expiry. The report reserves a whole 28-day block even for a seven-day experiment. Only after the owner actually deploys a probe should observed usage and remaining credit be used to update the list. Add a second region and rerun the command before considering ten.
5. Exit by the reported deadline. Remove instances, disks, snapshots and reserved addresses. Confirm resource inventory and billing records on the provider account. The CLI neither performs nor attests to that cleanup. The provider's hard no-charge account mode must protect the owner even if cleanup is late.

Calculate a 90–180 day runway

For each selected trial slot the planner sums its complete monthly quote and multiplies by the number of started 28-day blocks until its exit. It aggregates every selected slot under one provider account and requires the result to be strictly less than the remaining grant. The enforced cash cap after exit is $0. Credits do not authorize a paid subscription, a paid-only service or uncapped overage.

The current Iowa reference quote in the offer comparison puts ten continuously running probes at about $300.93 over 90 days before additional reserves, even using one region's prices for comparison. The pilot's confirmed budget and quotas do not support that fleet today. Provider terms and cost estimate

The $7, $8 and $12 figures above are synthetic inputs for arithmetic and regression tests. Quotes for real machines must come from the actual selected region and SKU. Turning on all ten slots in the shipped sample returns a validation error. Changing the cash cap to a positive value also fails. Do not spread one grant across duplicate account declarations. Planner and tests

Keep the worker boundary intact

A public edge can process only public test data, and its Docker access must be none. Private worker placement requires an explicitly trusted operator host, a permitted provider/region pair in allowed_private_provider_regions and a local Unix Docker socket. Public TCP Docker access is rejected for both roles. The shipped allowlist is empty. Keep tokens, uploaded packages and private documents on their existing trusted deployment until an authorized residency and isolation policy exists. Hub security model