For developers
Ship software instead of maintaining servers
If it runs in a container, it runs here: HTTPS address, logs, metrics, secrets and a database — without touching a server.
- api · SmallContainer image from GitHub Container Registry
- db · PostgreSQL · General 1 GBIts URI in a DATABASE_URL secret
- cleanup · cron jobEvery night
- Addressapi-5b6a1f.ap-mum.drasken.cloud
The whole flow
From Dockerfile to a live address
No server to configure. If it runs in a container, it runs here.
1 · Build and push
FROM node:22-alpine WORKDIR /app COPY . . RUN npm ci && npm run build CMD ["node","dist/server.js"] $ docker push ghcr.io/you/api:1.0
2 · Create app
- Image
- ghcr.io/you/api:1.0
- Port
- 3000 · public HTTP
- Size
- Small · 0.5 vCPU · 1 GB
- Secrets
- DATABASE_URL · env group
3 · LiveRunning · 1 instance
https://api-5b6a1f.ap-mum.drasken.cloud
Logs, metrics and health on the app’s page. Every deploy is a release you can go back to.
Coming soon: a container registry hosted by Drasken Cloud, and deploying automatically when you push a new image.
Coming soonSound familiar?
What developers would rather not do
Your problem
“I just want to deploy, not configure nginx.”
On Drasken Cloud
Choose an image and a port; HTTPS is already set up.
Your problem
“Where do I keep secrets?”
On Drasken Cloud
Secrets live in the app or an environment group, never in your repository.
Your problem
“My weekend project costs too much.”
On Drasken Cloud
Small sizes billed by the hour; stop it and pay only for its storage.
Why it fits
Developer‑friendly by default
- Any public or private container registry
- Ready-made connection strings: URI, JDBC, command line
- Logs and metrics per instance
- Jobs and cron from the same image, billed per minute of each run
Push an image. Get an address.
Create an account and deploy your first container today.