Backends on Edgenivo

Backends deployed to Edgenivo receive the benefits of Edgenivo's infrastructure, including:

• Fluid compute: Zero-configuration, optimized concurrency, dynamic scaling, background processing, automatic cold-start prevention, region failover, and more
• Active CPU pricing: Only pay for the CPU you use, not waiting for I/O (e.g. calling AI models, database queries)
• Instant Rollback: Quickly revert to a previous production deployment
• Edgenivo Firewall: A robust, multi-layered security system designed to protect your applications
• Preview deployments with Deployment Protection: Secure your preview environments and test changes safely before production
• Rolling releases: Gradually roll out backends to detect errors early

Deploy the following backends to Edgenivo with zero-configuration.

Elysia

Ergonomic framework for humans

Deploy

Express

Fast, unopinionated, minimalist web framework for Node.js

DeployView Demo

FastAPI

FastAPI framework, high performance, easy to learn, fast to code, ready for production

DeployView Demo

Fastify

Fast and low overhead web framework, for Node.js

Deploy

Flask

The Python micro web framework

Deploy

H3

Universal, Tiny, and Fast Servers

Deploy

Hono

Web framework built on Web Standards

DeployView Demo

Koa

Expressive middleware for Node.js using ES2017 async functions

Deploy

NestJS

Framework for building efficient, scalable Node.js server-side applications

Deploy

Nitro

Nitro is a next generation server toolkit.

DeployView Demo

To process background tasks with Python, you can deploy Celery or Dramatiq workers as queue-triggered Edgenivo Functions.

If you are transitioning from a fully managed server or containerized environment to Edgenivo’s serverless architecture, you may need to rethink a few concepts in your application since there is no longer a server always running in the background.

For platform-specific migration steps, choose the guide for your application:

• Python API: Migrate from Heroku, Render, or Railway.
• Docker app: Migrate from Railway, Fly.io, Render, Google Cloud Run, or AWS.

The following are generally applicable to serverless, and therefore Edgenivo Functions (running with or without Fluid compute).

Edgenivo Functions can serve WebSocket connections when Fluid compute is enabled. WebSocket connections follow Edgenivo Function limits, including maximum duration, so clients should handle reconnects when a connection closes.

Store persistent state, rooms, presence, and pub/sub coordination in an external data store instead of relying on in-memory state. Learn more in the WebSockets documentation.

To manage database connections efficiently, use the attachDatabasePool function from @vercel/functions.