In brief
For a first production Node.js app, most of the time goes not into the code but into the server: system updates, a reverse proxy, HTTPS, process management, recovery. With Montavio Node.js hosting you deploy your code from GitHub, GitLab or Bitbucket and we run the environment. This article shows seven concrete things you get and honestly says when a VPS is still the better choice.
The hidden tax on your first production Node.js app: the server
Building a Node.js app feels good: `npm start` and it works. Production is another game. You need a machine with the right Node.js version, a process manager that restarts the app, a reverse proxy, a valid certificate, logging, backups and someone to apply the system updates.
A VPS makes all of that possible, but you have to do all of it. If your application is an API, a bot, a Next.js site or an internal tool, managing the server is often more work than the app itself.
A 7 dolog, amit megkapsz
With Montavio Node.js hosting you focus on your code and we run the environment. These are the real elements of the service:
- Deployment from a repository. You publish your code from the customer portal using GitHub, GitLab or Bitbucket; build and start take a few minutes depending on size.
- Private repositories, safely. Each app gets its own deploy key, which you add to the repository as a read-only key; the private key never leaves the service environment.
- A Node.js version of your choice. Pick from the supported 26 (LTS), 24 and 22 lines per application and switch later.
- Automatic HTTPS and your own domain. Every app gets an address, and depending on the plan you can attach 2, 5 or 10 of your own domains; the system issues and renews the certificate.
- A MariaDB database. Plans include 1, 2 or 5 databases, created in the customer portal, with phpMyAdmin one click away.
- Environment variables and logs. Secrets stay out of your code, and you read logs in the customer portal without SSH.
- Rollback to the previous release. If you ship a faulty version, go back in the customer portal; we keep the last few versions, so rolling back does not need a new build from your repository.
Which plan fits what?
The plan resources build on each other. You will always find exact prices and current limits on the plan page.
| Plan | Memory and CPU | Storage | Domains and databases | What is it for? |
|---|---|---|---|---|
| Node.js Start | 512 MB, 1 vCPU | 2 GB | 2 domains, 1 database | Small API, bot, first site project |
| Node.js Pro | 1 GB, 2 vCPU | 4 GB | 5 domains, 2 databases | Production web app, Next.js, API |
| Node.js Plus | 2 GB, 4 vCPU | 8 GB | 10 domains, 5 databases | Busier app, several services |
When a VPS or web hosting is still better
Node.js hosting is not for everything, and it is better to know that up front.
- PHP, WordPress, WooCommerce: web hosting is simpler for these.
- Full server access, custom packages, Docker or arbitrary services: a VPS is the right choice then.
- A Node.js application where you want to focus on code: Node.js hosting sits between the two: you handle the code, we handle operations.
How to start: four steps
To order you only choose the plan, the term and the application name; the system asks for your code address after payment, in the customer portal.
- Choose the plan and term (1, 3, 6 or 12 months).
- Pay by card; the application is created in the customer portal within seconds.
- Enter your repository address and, for a private one, add the read-only key you receive.
- Set your environment variables, publish the code, then attach your own domain.
Node.js hosting with Montavio
Three plans, GitHub-based deployment, automatic HTTPS, your own domain, MariaDB and rollback. You provide the code after payment.
See Node.js plans
