Node.js hosting · Vallic Cloud
Node.js hosting · Vallic Cloud
Node.js and Next.js hosting, deployed from Git.
Next.js, Express or anything that listens on a port, on machines no other customer shares. Node or Bun, with the database and Valkey beside it, and a deploy that rolls back if the new release never answers.
On Vallic Cloud
What runs your Node.js site
You choose
Runtime
You can add
Database
Cache
Reverse proxy
Search
Time series
Background work
The default, unless vallic.yaml names another version.
Done for you
Kept between releases
private, so a deploy never loses what the site wrote.
Why here
An application that serves itself.
The runtime is the web server
Your application serves its own HTTP. In front of it the platform terminates TLS, routes the hostname and compresses responses.
Node, or Bun in its place
One line in vallic.yaml runs the same project on Bun, with the same port and the same node_modules. Going back is the same line the other way round.
Configuration it already reads
PORT, DATABASE_URL and REDIS_HOST arrive as environment variables. There is no bootstrap file to add.
Deploys that check themselves
With a health path set, a deploy waits for it to answer, and on_failure: rollback puts the previous release back if it never does.
Workers and cron when you declare them
Background processes run as supervised workers with no port. Cron runs on one machine only, however many web servers there are.
Support from people who build applications
Our team builds and runs web applications for a living, and a ticket reaches them.
Moving a Node.js application here.
Add a vallic.yaml, make the application listen on PORT on every address, import the database with vallic db import, and deploy.
Building a front end for a Drupal or WordPress site? Run it as a project of its own beside the CMS, in the same team and console.
Questions
Can I run a Next.js front end beside Drupal or WordPress?
Yes. It is a project of its own, next to the CMS project, with its own environments and deploys. On the shared plan it can join the machine the first project already runs on.
Where do uploads go?
The release is read-only. What the application writes and expects to keep goes under VALLIC_PRIVATE_DIR, which outlives every release, or a directory declared as a mount.
Do you charge per request or per visit?
No. Machines are billed by the month, and traffic past what a machine includes by the terabyte.
Where can it run?
In any of the platform’s datacentres. The configurator shows each one’s machines and prices before you sign up.
