Automation
n8n
Workflow control, delivery routing, and deterministic automation.
Operator Access
This portal layer now includes a post-login dashboard surface for quick navigation across the Modal Nodal stack.
Dashboard
Use the dashboard to jump between the core Modal Nodal surfaces. The `<-- modals` button in the nav always returns you to the main menu.
Reference
Review hostname routing and public/private boundary rules.
Read docSecurity
Review repo-boundary rules and operational exclusions.
Read docIngress Contract
Modal Nodal keeps runtime services private on localhost and exposes only deliberate entrypoints through a reverse proxy. The target hostname map is stable even if the internal runtime moves.
Runtime
LiteLLM, Open WebUI, Flowise, Postgres, Redis, Qdrant, and support workers stay on private local bindings rather than being exposed directly.
Delivery
Output sync, manifests, upload receipts, and optional Drive handoff stay operationally separate from the public portal layer.
Deployment
The public-facing portal can live on Vercel while the infrastructure stack remains local or self-managed behind your own ingress boundary.
Repository
Positioning
Modal Nodal is designed to separate public presentation from private runtime: a clean public surface, a stable ingress contract, and infrastructure that stays under deliberate operational control.