Neon LawCall +1 510 800 2090
  • Navigator
  • Notations
  • Legal Aid
  • Sign in

← Operating Neon Law Navigator

Provision the Infrastructure

Chapter 3 of 7 · Section 12 of 54

Sections

1. Intro

  • 1. Deploy your own
  • 2. Agenda

2. Prepare Google Cloud

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

3. Provision the Infrastructure

  • 11. The APIs that light up
  • 12. Network and storage buckets
  • 13. How a matter's pages reach a client
  • 14. A document's bytes and authorization are separate
  • 15. A private image registry
  • 16. The cluster comes up
  • 17. What setup owns — and what follows it

4. Operate Forgejo beside Navigator

  • 18. Deploy the forge before switching repositories
  • 19. Separate people, Git transport, and machine access
  • 20. Require the gate and protected-main policy
  • 21. Bind the workflow to one Project and one commit
  • 22. Notify failures even when the manifest is broken
  • 23. Restore the repository before cutting over

5. Environment Matrix

  • 24. Three operating modes, two deployment profiles
  • 25. The deployment that says its matters are sample
  • 26. Deployment and release switches
  • 27. Workflow host and routing switches
  • 28. Capability and storage switches
  • 29. Configuration precedence: the first source wins
  • 30. Local dev controls: inputs read by `hudson dev`
  • 31. Local runtime: what `.devx/env` generates
  • 32. The store: SurrealDB
  • 33. Where SurrealDB authorization lives
  • 34. Deployed runtime: core web and worker wiring
  • 35. Deployed runtime: identity and access
  • 36. Deployed runtime: email, signatures, and billing
  • 37. Deployed runtime: repositories, content, AI, and scheduled work
  • 38. Provision and ship: variables read by the operator CLI
  • 39. Ancillary operations and opt-in test controls
  • 40. When sample data appears

6. Configure the Trust Boundaries

  • 41. Secrets: the invariants that gate the boot
  • 42. Secret access, encryption, and audit
  • 43. Sign-in: bring an OIDC provider; passwords live there, not here
  • 44. Role rings: who can do what
  • 45. Provider setup and parity across deployment rows
  • 46. The external surface — every third party, in one place
  • 47. The two service deployments
  • 48. Security architecture

7. Ship the Instance

  • 49. Ship and verify
  • 50. Point your domain at the instance (optional)
  • 51. Drive it from the CLI
  • 52. Make it yours — white-label under your own brand
  • 53. First-ship lessons
  • 54. Canonical references

Network and storage buckets

With the APIs on, the CLI provisions the data plane and runtime identity:

  • A custom-mode VPC with one explicitly named regional subnet and private Google access. The deployment's GKE cluster is pinned to both names.
  • Six private Cloud Storage buckets, all uniform bucket-level access: -assets (marketing objects served through the same-origin /assets/* application route), -documents (client documents), -exports (Parquet/Iceberg archives), -logs (the Nearline log-sink destination), -postgres-backups (the PostgreSQL WAL archive and base backups, expired at 30 days), and -applications (still provisioned; the retired Portal's bundles are no longer read or written). A deployment may also name separate archive and telemetry buckets for long-term snapshots and telemetry landing data.
  • A deployment-specific Google service account with the Secret Manager accessor role, object access on only that deployment's core buckets other than PostgreSQL backups and any named archive/telemetry lanes, Workload Identity bindings for the namespace's navigator-web and workflows-service Kubernetes service accounts, and permission to sign its own GCS URLs.
  • A separate Workspace Drive service account with no runtime GCP roles. An operator creates one JSON key, records it in that deployment's secrets.enc.yaml, and grants its OAuth client domain-wide delegation in the selected Workspace.

Presenter notes

No stage generates a credential, so a run prints no secret and there is nothing to record. The six core private buckets are: your-project-id-assets — marketing photography read by web and delivered through /assets/*; your-project-id-documents — client documents, where web writes content-addressed blobs, kept separate from assets; your-project-id-exports — nightly Parquet/Iceberg snapshots written by workflows-service; your-project-id-logs — the Nearline destination for the deployment's Cloud Logging sink; your-project-id-postgres-backups — the PostgreSQL WAL archive and daily base backups, read and written only by the navigator-postgres-backup Kubernetes service account; and your-project-id-applications — still provisioned, though the retired Portal no longer reads or writes it. Setup creates the logs bucket but not the operator-managed sink; complete the per-deployment sink recipe in docs/gke-prod.md. Clients do not get GCS IAM roles or bucket URLs: they see documents through Navigator after it checks their session and Project participation row. Every create call treats an HTTP 409 Conflict as success — that is Google's "already exists" response — which is exactly what makes re-running setup safe rather than destructive.

View all slidesOpen display
← PreviousNext →
Neon Law
  • X opens in a new tab
  • LinkedIn opens in a new tab
  • YouTube opens in a new tab
  • API
  • Blog
  • Contact
  • Design
  • Glossary
  • Navigator
  • Notations
  • Presentations
  • Privacy
  • Team opens in a new tab
  • Terms
  • Testimonials
  • contact@neonlaw.com
  • +1 510 800 2090
  • California
    1515 20th StreetBakersfield, CA 93301
  • Nevada
    5150 Mae Anne AveSte 405-9002Reno, NV 89523
  • New York
    12 E 49th St18th FloorNew York, NY 10017
  • Washington
    1111 Main StSTE 201EVancouver, WA 98660
  • Justice Technology AssociationMission-Aligned Partner opens in a new tab
  • Proud member of Greater Vancouver ChamberGVC opens in a new tab

Attorney advertisement. Nothing here is legal advice without a signed retainer for an active project. Past results do not guarantee future outcomes.

Everyone deserves access to justice.Made with ❤️ in 🗽.

© 2026 Guieb & Shook PC

Powered by neon-law/navigator opens in a new tab26.11.17-rc.1GitHub stars 5