Infrastructure Requirements

Compute Resources

• Build Environment: A build server or CI/CD runner capable of executing Node.js build processes. The build process requires sufficient CPU and memory to compile the Nuxt-based frontend application.
• Runtime Environment: A server or container platform to host the built frontend application. This can be:
  • A Node.js runtime environment for server-side rendering (SSR)
  • Edge computing platforms for optimal global distribution
• Scaling Capability: Infrastructure that can scale horizontally to handle traffic spikes and ensure high availability.

Storage

• Build Artifacts: Storage for build outputs, which can range from a few hundred megabytes to several gigabytes depending on your frontend size, dependencies and asset optimization.
• Static Assets: CDN or object storage for serving static assets (images, fonts, compiled CSS/JS). Optional but recommended.
• Deployment History: Optional storage for maintaining deployment artifacts for rollback capabilities.

Networking

• Public Internet Access: Your infrastructure must be accessible from the public internet to receive webhook calls from the Laioutr Cockpit.
• HTTPS Support: SSL/TLS certificates for secure communication and proper content delivery.
• DNS Configuration: Ability to configure DNS records for your frontend domain(s).
• Firewall Rules: Properly configured firewall rules to allow webhook traffic from Laioutr Cockpit IP ranges.

Health Checks

Point your platform's liveness probe at GET /api/frontend/health. It answers {"status":"ok"} with cache-control: no-store.

The endpoint is deliberately shallow. It resolves no market, page, cache or upstream, so it reports that the server can run a handler and nothing more.

That shallowness is the point, because probing a content path instead does not work reliably:

• A platform healthcheck arrives with the host's own Host header, which matches no configured market.
• A project with nothing published answers 404 on every content path.

Either case fails a container that is running perfectly well. Railway has taken healthy containers out of rotation this way.

Geographic Distribution

For optimal performance, consider deploying to multiple regions or using edge computing platforms to reduce latency for global audiences.