Serve and test your work seamlessly.
feat: add order filters
- QUEUED3s
- BUILDING28s
- BUILT1s
- DEPLOYING4s
- RUNNINGlive
QUEUED · waiting for a builder. cloning github.com/ada/orders-api@main. BUILDING · runtime node. npm ci — 214 packages. npm run build. BUILT · artifact packaged. DEPLOYING · starting on port 8080. health check passed. RUNNING · orders-api.dpl.app
- QUEUED
- BUILDING
- BUILT
- DEPLOYING
- RUNNING
How it works
Five steps from repository to live.
The same flow for every runtime. Sensible defaults at each step, so most deploys are a few clicks.
- 01
Source
Connect GitHub, pick the repository and the branch to deploy.
- 02
Runtime
Vite, Next.js, Node.js, Python, PHP, Go, Static Sites or Docker. Your stack, your choice.
- 03
Configure
Project name, build command, start command, port and environment variables. Nothing else.
- 04
Deploy
Watch every stage of the build and rollout, with the logs right there.
- 05
Live
Your project is live — with its deployment URL and the actions to manage it.
Configure
Only the settings that matter.
Each runtime exposes the same five settings, with sensible defaults you can override.
01Runtime version
Pick from the supported versions for your runtime.
02Build command
Sensible default per runtime; override when you need to.
03Start command
How your app starts once it's built.
04Port
Where your app listens. We route the deployment URL to it.
05Environment variables
Injected securely into builds and runtimes.
Instance lifecycle
A successful creation is not a running instance.
Instances move through CREATING, BOOTING and RUNNING, with explicit failure states so you always know which stage needs attention.
- 01QUEUEDAccepted and waiting for a builder.
- 02BUILDINGInstalling, compiling, generating artifacts.
- 03BUILTThe artifact is packaged and preserved.
- 04DEPLOYINGStarting your process and wiring the URL.
- 05RUNNINGHealthy and serving traffic.
BUILD_FAILEDafter BUILDING
The build stopped. The logs say exactly where.
DEPLOY_FAILEDafter DEPLOYING
It built, but it didn't start. Not the same thing.
CRASHEDafter RUNNING
It was running, then it wasn't. Health checks noticed.
Build time
Everything that turns a repository into something runnable.
- Dependency installation
- Compilation
- Framework builds
- Artifact generation
Run time
Everything that keeps it alive once it's live.
- The persistent process or container
- CPU and RAM
- Storage
- Network behaviour
Underneath
Complexity stays underneath.
The deploy screen stays simple because the platform does the heavy lifting. Here's what it's responsible for.
- 001.
Runtime detection
Identify — or respect — the runtime you picked and your project structure.
- 002.
Dependency installation
Install packages with the right ecosystem tooling.
- 003.
Build engine
Run default or custom build commands, within limits.
- 004.
Artifact handling
Package and preserve exactly what the deployment needs.
- 005.
Runtime orchestration
Start, monitor, restart and stop deployed workloads.
- 006.
Ports & routing
Expose your app through its nairacloud instance URL.
- 007.
Environment variables
Inject configuration securely into builds and runtimes.
- 008.
Logs
Build and runtime logs, in the same place you deployed from.
- 009.
Health checks
Detect unhealthy or crashed applications.
Get started with nairacloud.
Create an account, fund your wallet and launch your first instance.