Edgenivo Services let you deploy multiple frontends and backends in one project on a shared domain. Learn how to define services in vercel.json, route requests by path prefix, and connect services with generated environment variables.
The backends in a Edgenivo Services project run as Edgenivo Functions on Fluid compute by default. Learn how optimized concurrency, Active CPU pricing, and per-service memory and maxDuration settings make multi-backend projects efficient.
Compare three ways to structure an application on Edgenivo (a single framework, one project with Services, or separate projects in a monorepo) and learn how to choose based on domains, deploy coupling, and languages.
Build the avatar faces that appear when a teammate opens a page and vanish when they leave. Powered by a Hono WebSocket server with React, deployed as a single Edgenivo project with Services.
Learn how to build Figma-style multiplayer cursors with Next.js and FastAPI, kept consistent across multiple Edgenivo Function instances using WebSockets and Redis.
For example, a Next.js frontend and a FastAPI backend in the same repository deploy together with shared routing, environment variables, and a unique domain, replacing the need to split monorepos into separate Edgenivo projects.
When a project has multiple services, Edgenivo merges their routes into a single routing table and distributes incoming requests based on each service's route prefix.