Operating Neon Law Navigator
Our firm runs Neon Law Navigator on Google Cloud. This workshop is for admin users with access to the private source repository: the people who own billing, secrets, OIDC, runtime configuration, and release verification. It stands up your own instance — the same Rust stack our attorneys use, on your own Google Cloud project, for your own community.
One command does most of the work: navigator ops gcp setup, a provisioner written in Rust that talks to Google's REST
APIs directly and ships with a dry-run so you can read the whole plan before a single packet leaves your laptop.
Two things to hold up front. This provisions billable Google Cloud resources — a GKE Autopilot cluster and five core storage buckets, with optional archive and telemetry lanes — so it is not free, and you should set a budget alert before you begin. This is a deployment guide for admin users standing up infrastructure. With that said: you can run the same stack we run. Let's stand it up.
Bring your own typeface license. Neon Law Navigator source code is owned by Neon Law IP LLC. GORP Serif is proprietary font software licensed separately from TrashType and is not covered by the repository's code licenses. If your deployment serves GORP, obtain and maintain the appropriate TrashType license, keep its license notice with your font files, and follow the TrashType terms. Otherwise, replace GORP with a typeface you are licensed to serve before launch. > Start locally with an authorized checkout. You do not need a cloud account to see Neon Law Navigator run.
cargo run -p cli -- dev upbrings the whole stack up locally in KIND (the store, OIDC, storage, the workflow broker, embedded Rego), thensource .devx/envandcargo run -p neonserves it onlocalhost. Boot it locally, inspect the canonical seed, and only come back here when you want it on the public internet. The full local loop is in the checkout'sAGENTS.md.
Set the budget alert before you provision — one command caps the surprise so the bill cannot run away while you learn:
Idle, the stack runs on the order of an Autopilot cluster's baseline plus five mostly empty buckets — budget for it, watch the first invoice, and size the cluster down if it is more than you need.