This page shows how the GROWTH_ARCHITECT app runs: the frontend launch surface, the proxy backend that handles AI requests, and the runtime status used in local and deployed environments.
The user enters a URL in the GROWTH_ARCHITECT interface and starts an audit.
The app sends the request to the proxy endpoint rather than calling Google APIs directly from the browser.
The Node backend authenticates with Google ADC, builds the Vertex AI request, and forwards the payload.
The result comes back to the interface, where the app renders the score, recommendations, and follow-up actions.
The frame below points at the production-style build so you can show the app and the operational shell in one place.
The proxy server lives in the Growth Architect backend service and now exposes a health endpoint for the ops page.
Use it as the portfolio-friendly operations view: it shows the running app, the proxy route, and whether the backend responds to health checks.
Once deployed, the portfolio card opens the app and this page explains the backend path, so the whole product story is visible in one browsing flow.