Connect GitHub or upload a ZIP. Devora analyzes the project, builds it, runs it in isolated containers and ships it with HTTPS and your own domain — with database, S3 and monitoring in the same dashboard.
Generate a token in the dashboard and paste it into your AI — ChatGPT, Claude, Cursor or another. It creates the project, the database and S3, and hands you the live site.
You pick the source. The pipeline does the rest and shows every step in the dashboard.
CPU and memory for sites, APIs, workers and services. Replicas behind a load balancer.
GitHub · ZIP · HTMLAccounts, orders, permissions and file references. Credentials and connection in the dashboard.
PostgreSQL · RedisImages, videos and documents outside the database, with an S3-compatible API. From 1 TB to 10 TB.
S3-compatible APICPU, memory and network metrics, deploy history, live logs and terminal. When a build fails, the AI points to the likely cause and suggests a fix for you to review.
sharp is used by next/image but is not in dependencies. Add it and deploy again.npm install sharpWith failover included, your project stays online: if the server goes down, the standby copy in another country takes over on its own. Scalability (autoscaling) and load balancing are optional, billed by the hour.
To scale well, the app must share sessions and files (Redis and S3) and avoid duplicate jobs.
Prices in USD, before tax. CPU and memory are shared between the account’s services and replicas.
We do not sell domains: it stays at your registrar. Just point the DNS.
The map shows, live, where Devora runs servers. When a new region goes live, it shows up here on its own.
Choose per project between Scalability (autoscaling), Load balancing or Failover. With failover included in every plan, your project stays online: if the server goes down, the standby copy in another country takes over on its own. Load balancing and autoscaling are optional and billed by the hour.
A clone that starts with the load
Normal load: one copy is enough
When CPU crosses the limit, the platform starts a clone of the app and the load balancer splits the load with it. When usage drops, the clone is turned off and stops being billed.
Running copies sharing the traffic
Traffic split between US and Germany
Two or more copies run at the same time on different machines. The load balancer splits every request between them; if one fails, the others keep serving while it is recreated.
Protection without burning resources
Primary serves alone; standby is off, no CPU
A standby copy stays off in another country. If the primary goes down, the standby starts on its own and takes the traffic. Every deploy updates it to the new version and it stays off.
Mailboxes on your domain, billed per mailbox. A separate service, no trial.
See price per mailbox →Confirmations, password resets and app notifications via BytSend. Billed separately.
Discover BytSend →No. The trial lasts 7 days and only asks for email confirmation.
No. You keep the domain at your provider and point the DNS to Devora.
CPU and memory belong to the account and are split between services and replicas. Extra CPU, memory or S3 is billed per hour.
You can, but we do not recommend it. Use S3 for images, videos and attachments and keep only the reference in the database.
Portuguese, English, Spanish, French and German, in the docs and support.
7 days free to deploy your first project.
