Neon Law
  • Fractional CTO
  • Litigation
  • Fractional GC
  • Legal Services
  • Sign in

Operating Neon Law Navigator

Our firm runs Neon Law Navigator on Google Cloud. The Foundation gives the recipe away. This workshop is for admin users of the application: 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 storage buckets — so it is not free, and you should set a budget alert before you begin. And 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 Shook Law PLLC. 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. > Want a free win first? You do not need a cloud account — or a credit card — to see Neon Law Navigator run. cargo run -p cli -- dev up brings the whole stack up locally in KIND (the store, OIDC, storage, the workflow broker, embedded Rego), then source .devx/env and cargo run -p neon serves it on localhost. 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 AGENTS.md.

Set the budget alert before you provision — one command caps the surprise so the bill cannot run away while you learn:


gcloud billing budgets create --billing-account "$BILLING_ACCOUNT_ID" \
  --display-name "Neon Law Navigator" --budget-amount 200USD \
  --threshold-rule percent=0.5 --threshold-rule percent=0.9

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.

Start →View all slidesView as Markdown
1

Chapter 1

Intro

  1. 1Deploy your own
  2. 2Agenda
2

Chapter 2

Prepare Google Cloud

  1. 3Bring your own project
  2. 4Dry-run first
  3. 5Private assets and domain restricted sharing
  4. 6The one project that is public on purpose
  5. 7The Navigator deployment matrix
  6. 8The `/app` mount and HTTP route ownership
  7. 9`neon` — the whole brand seam
  8. 10Live rollout checkpoint
  9. 11Set one site to one version
3

Chapter 3

Provision the Infrastructure

  1. 12The APIs that light up
  2. 13Network and five buckets
  3. 14How a Project portal reaches a client
  4. 15One matter's document never backs another matter's
  5. 16A private image registry
  6. 17The cluster comes up
4

Chapter 4

Environment Matrix

  1. 18Three operating modes, two deployment profiles
  2. 19Configuration precedence: the first source wins
  3. 20Local dev controls: inputs read by `navigator dev`
  4. 21Local runtime: what `.devx/env` generates
  5. 22The store: SurrealDB
  6. 23Where SurrealDB authorization lives
  7. 24Deployed runtime: core web and worker wiring
  8. 25Deployed runtime: identity and access
  9. 26Deployed runtime: email, signatures, and billing
  10. 27Deployed runtime: repositories, content, AI, and scheduled work
  11. 28Provision and ship: variables read by the operator CLI
  12. 29Ancillary operations and opt-in test controls
  13. 30When simulated data appears
5

Chapter 5

Configure the Trust Boundaries

  1. 31Secrets: the invariants that gate the boot
  2. 32Sign-in: bring an OIDC provider; passwords live there, not here
  3. 33Role rings: who can do what
  4. 34Provider signup and parity across the deployments
  5. 35The external surface — every third party, in one place
  6. 36The two service deployments
  7. 37Security architecture
6

Chapter 6

Ship the Instance

  1. 38Ship and verify
  2. 39Post the verified handoff in `#navigator`
  3. 40Point your domain at the instance (optional)
  4. 41Drive it from the CLI
  5. 42Make it yours — white-label under your own brand
  6. 43This is how we set up Neon Law Foundation
7

Chapter 7

Wrap Up

  1. 44Canonical references
Neon Law
BlogContactFoundationNavigatorPresentationsWorkshops
Contact us — contact@neonlaw.com+1 510 800 2080
  • Nevada
    5150 Mae Anne AveSte 405-9002Reno, NV 89523
  • New York
    12 E 49th St18th FloorNew York, NY 10017
  • Washington
    720 Seneca StSte 107-715Seattle, WA 98101

© 2026 Shook Law PLLC and Neon Law Foundation

This is attorney advertisement. Nothing on this site is legal advice. Neon Law is the trade name of Shook Law PLLC, and an attorney-client relationship begins only with a signed retainer between you and Shook Law PLLC. Published flat fees cover the scope each one names and do not include third-party filing fees. Every legal matter is different, and past results do not guarantee a similar result.

Shook Law PLLC is a proud supporter of the Neon Law Foundation , a 501(c)(3) nonprofit.

Neon Law Foundation is a Nevada nonprofit corporation and a 501(c)(3) tax-exempt organization. It does not practice law and cannot represent you.

Nothing on this site is legal advice, and nothing here creates an attorney-client relationship.

5150 Mae Anne Ave Ste 405-9999, Reno, NV 89523
support@neonlaw.orgTransparency & public disclosures

Powered by Neon Law Navigator #26.8.20-hotfix.4

Open source — neon-law-foundation/navigator GitHub stars 2