Deploy Next.js, NestJS and Node.js
Ship long-running applications from the CLI or a connected GitHub repository, with logs, domains and configuration in one place.
- Next.js, NestJS, custom Node
- Rootless containers
- Automatic rollback on a failed probe
From repository to running app
Deploy with the CLI or connect a GitHub repository. Next.js standalone output, NestJS and custom Node.js entrypoints are all supported.
Isolated by construction
Each application runs in a rootless Podman container with a read-only root filesystem, all capabilities dropped, no new privileges and a hard memory limit.
Deployments that can go back
The old container is stopped and renamed, the new one started and probed over HTTP. Only a passing probe retires the previous version; a failure returns to it.
A hard memory limit is a limit
Exceeding the configured memory kills the container through the kernel. It is not a soft warning threshold, and the restart policy retries a bounded number of times.
Configuration next to the app
Environment variables, domains and logs belong to the application resource, so there is no second console to keep in sync.
Logs where the app is
Live log streams come over a realtime channel rather than a polling loop, so tailing an application feels like tailing a local process.
Bring your own build
Next.js needs output: 'standalone'. NestJS uses dist/main.js. A custom application needs a runnable server entrypoint that binds the PORT it is given. Beyond that, Veltic does not ask you to restructure your project.
A redeploy is not a rolling reload
There is a brief interruption while containers are swapped. If your workload cannot tolerate that, put a queue in front of it rather than assuming zero downtime you were never promised.
veltic apps deploy PROJECT_ID storefront ./ --framework nextjs
veltic apps logs PROJECT_ID storefront --followBuild the whole backend in one project
One plan, one dashboard, one command line interface. PostgreSQL, applications, functions, storage and realtime.