Neon Law
  • Services
  • Book Consultation opens in a new tab
  • Sign in

← Operating Neon Law Navigator

Wrap Up

Chapter 8 of 8 · Section 51 of 51

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 Project portal reaches 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. Configuration precedence: the first source wins
  • 27. Local dev controls: inputs read by `navigator dev`
  • 28. Local runtime: what `.devx/env` generates
  • 29. The store: SurrealDB
  • 30. Where SurrealDB authorization lives
  • 31. Deployed runtime: core web and worker wiring
  • 32. Deployed runtime: identity and access
  • 33. Deployed runtime: email, signatures, and billing
  • 34. Deployed runtime: repositories, content, AI, and scheduled work
  • 35. Provision and ship: variables read by the operator CLI
  • 36. Ancillary operations and opt-in test controls
  • 37. When sample data appears

6. Configure the Trust Boundaries

  • 38. Secrets: the invariants that gate the boot
  • 39. Sign-in: bring an OIDC provider; passwords live there, not here
  • 40. Role rings: who can do what
  • 41. Provider signup and parity across the deployments
  • 42. The external surface — every third party, in one place
  • 43. The two service deployments
  • 44. Security architecture

7. Ship the Instance

  • 45. Ship and verify
  • 46. Post the verified handoff in `#navigator`
  • 47. Point your domain at the instance (optional)
  • 48. Drive it from the CLI
  • 49. Make it yours — white-label under your own brand
  • 50. This is how we set up our production deployment

8. Wrap Up

  • 51. Canonical references

Canonical references

This workshop is the narrative; these docs are the source of truth and stay current — prefer them when they disagree:

  • docs/oss-install.md — the full end-to-end install (env, Secret, overlay, image, verify). docs/deployment-secrets.md — production secret rendering. docs/third-party-integrations.md — the per-environment vendor-account convention. docs/docusign-esignature.md — e-signature setup and the one-app, two-environment model.

Presenter notes

This is the access-to-justice fight made deployable: the cheaper and more repeatable it is to stand up a grounded legal harness, the more clinics and small firms can run one under Apache-2.0. When your instance is live, tell us at support@neonlaw.org so we can point the next deployer at what you learned. Telling us what you learned is itself a contribution: the Contributing to Neon Law Navigator workshop lays out every way to give back, and once your instance is live, walk your lawyer through Using Neon Law Navigator.

View all slidesOpen display
← PreviousFinish
Neon Law
  • X opens in a new tab
  • LinkedIn opens in a new tab
  • YouTube opens in a new tab
  • API
  • Blog
  • Contact
  • Glossary
  • Navigator
  • Notations
  • Presentations
  • Privacy
  • Team
  • 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
  • Justice Technology AssociationMission-Aligned Partner 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.

© 2026 Shook Law PC

NEON LAW® is a registered trademark of Shook Law PC, U.S. Reg. No. 6,325,650 opens in a new tab

Powered by Neon Law Navigator 26.10.18

neon-law/navigator opens in a new tab

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