Operate the terminal product from a Nexus-owned website and control plane.

Nexus Pilot needs customer-facing ownership at the domain and route layer before deeper backend cutover work can be credible.

• The website now carries product, docs, support, security, and distribution messaging.
• The app subdomain is kept operational and focused on runtime control.
• Safe customer-facing links can move immediately without pretending Nexus already owns every backend dependency.

Backend ownership replaces inherited product links in stages rather than through unsafe string replacement.

• Sessions and run history move behind Nexus-owned routes and storage abstractions.
• Environment onboarding, scheduled runs, connectors, and GitHub integration cut over only when the backing flows exist.
• Hostinger automation keeps deployment and DNS changes under one repeatable Nexus workflow.