Architecture
Infrastructure & Hosting
Production hosting, local emulation, and network routing.
Infrastructure & Hosting
Wordloop deploys entirely to managed Google Cloud serverless infrastructure in production. For information about local development and emulation, see the Local Infrastructure page.
Production Hosting
| Service | GCP Resource | Description |
|---|---|---|
| wordloop-docs | Firebase Hosting | Next.js/Fumadocs static site deployment. |
| wordloop-app | Cloud Run | Next.js server utilizing SSR and Route Handlers. |
| wordloop-core | Cloud Run | Go REST API. |
| wordloop-ml | Cloud Run (x2) | Deployed as two separate services: an HTTP web server and a Pub/Sub background worker. |
| Database | Cloud SQL | Managed Postgres 15 database instance. |
| Messaging | Cloud Pub/Sub | Managed topics and subscriptions. |
API Routing (Production)
To ensure the frontend is environment-agnostic, the Next.js wordloop-app implements a Server-Side API Proxy.
- All frontend fetches are directed to
/api/.... - A Next.js Route Handler proxies these requests to the underlying
wordloop-coreURL (defined via theCORE_API_URLenvironment variable at runtime). - This prevents hardcoding backend URLs during the Next.js build step.
Environment Configuration
Configuration relies exclusively on environment variables injected at runtime. There are NO configuration files deployed with the containers. See individual service handbooks for specifics.