How Deployments Work
A Deployment in Karada represents a specific build and runtime state of your project.Automatic Builds
When you click Deploy on the dashboard (or when continuous integration triggers a new build), Karada spins up an isolated builder container.- It downloads your source code (or the generated Auto-MCP server).
- It detects the language and runtime (e.g., Node.js).
- It installs dependencies securely and compiles your project.
Global Edge CDN and Regions
Once built, your application is pushed to Karada’s distributed container registry. When the server starts:- It runs securely using firecracker microVMs.
- Statically generated files and assets are cached across our global Edge CDN for lightning-fast loads.
- Your dynamic endpoints are exposed via a secure HTTPS proxy.
Managing Deployments
From the Deployments tab in your Project Dashboard, you can monitor the lifecycle of every build.Deployment Logs
Every deployment generates detailed build logs. If a build fails (e.g., due to a syntax error or a missing dependency), you can immediately inspect the logs directly in the Karada UI to diagnose the problem. There is no need to SSH into servers.Instant Rollbacks
Mistakes happen. If a new deployment introduces a bug, Karada makes it incredibly simple to revert. Just click the three dots (...) next to any previous successful deployment and select Rollback. Karada will instantly route traffic back to the stable version with zero downtime.
Custom Domains
By default, Karada assigns a unique.karada.ai subdomain to every project automatically. You can also map your own custom domains by configuring a CNAME record in the Settings tab. Karada provisions and automatically renews free SSL certificates for all custom domains.