API Maker

The backend engine for the AI era

DeployEpisode 47 6:42 12 chapters November 2026

Upgrade API Maker on Every Server from One Page, Safely

A new version of API Maker on every server of the installation, from one page of the panel. See how the page Upgrade/Downgrade Engine installs it from npm or from a bundle, checks its hashes and the program, goes back on its own with a watchdog when the new version does not start, and where Launchpad and the license of each server fit in.

Next: SSR websites Read the docs

In the playlists The complete course Run in production

Chapters

What you will learn

  • The Upgrade/Downgrade Engine page: from npm or from a bundle
  • What each server does, its hash checked
  • The way back: a watchdog
  • A whole cluster, and what stays in place
  • Servers that refuse what they can not do safely
  • Launchpad from your laptop, and the license of each server
In the docsDeploy API Maker
Transcript983 words · click a time to play from there

Intro

You can put a new version of API Maker on every server of the installation, from one page of the panel. In this video, the page Upgrade/Downgrade Engine installs it, checks it, and goes back by itself when the new version does not start.

An upgrade, the usual way

Upgrading a backend is usually risky. You open SSH on each server, one after the other. You copy a build by hand, for the right processor. You restart, and hope that it starts. And when it does not, you go back by hand too, while the APIs are down. With API Maker, one page upgrades every server at once. Each server takes the package of its own machine, and checks its hash.

The new program is checked before it is used. And a watchdog goes back to the old version by itself. In this video: the page, the ways to deploy, what each server does, the way back, a whole cluster, what stays in place, servers that refuse, and the license of each server.

The page

Upgrade Engine, under Operations, opens the page Upgrade/Downgrade Engine. The header shows the version this server runs, under the name of the page. On the left, you can upload a bundle, the file of a version. On the right, you can pick a version published on npm, and deploy it. And below them, a webhook lets your pipeline do the same with one call. It has its own video.

Two ways to deploy

From npm, every server downloads the package of its own machine, x64 or arm64. It checks its SHA 512 before anything is installed. So a cluster with both kinds of machines is upgraded in one go. An upload goes to one server. That server hands it to the others through the Redis of the installation, in pieces of four megabytes, kept for an hour. Each server checks its SHA 256, and a server with another kind of machine refuses it.

What each server does

Each server does the same steps. The package is downloaded, or received. It is unpacked next to the running version, in releases. Its program is checked: it must be built for this machine, and it must start. The current link moves to it, all at once, and the three newest versions are kept. Then systemd starts the new version.

The way back

And if it does not start? A watchdog runs outside of API Maker, as its own systemd unit. It restarts API Maker, then asks its port every two seconds, seventy five times. If it gets an answer, its work is done. If there is no answer within two and a half minutes, current goes back to the version that ran before, and that one is started again.

A whole cluster

The page asks one server. That server asks every other server at once. The page shows a card for each server, with the progress of each step. Each server restarts by itself, once it has answered. The server that took the request restarts last, so the page gets the result of every server. Then the page waits until every server answers on the new version, and reloads.

What stays in place

The env file, the license, the uploads, and the logs live outside of the versions. So nothing has to be put aside. A server that fails keeps the version it runs, and the page says why. A deployment waits up to twenty minutes for its servers. And when the WebSocket of the page is down, the deployment goes on, and the page shows the result when it ends.

Servers that refuse

A server refuses what it cannot do safely. This demo server runs on a Mac. When we ask it for the latest version, it refuses at the first step, before anything is downloaded, written, or restarted. A server run from the source code of API Maker refuses too. It is upgraded by building the code. And versions of the Node.js edition cannot run on version four.

API Maker itself

This page upgrades API Maker itself. Your APIs, schemas, and websites go to every server with a Git pull. And the settings of every server are on Deployment Settings. What about servers without API Maker yet? One command of the installer sets each one up, as video sixty one shows. Or the Cloud mode of API Maker Launchpad installs it from your laptop, over SSH. It uses the same npm packages, checked the same way, and you review every change server by server first.

Then the deployment runs in stages, with the output of every server, from one server to a cluster. Video fifty eight shows it.

The license of each server

Licenses, under Operations, shows the license of every server of the installation, with a card for each. This server has no key yet. It says invalid: no license key is set on this server, and it shows the fix, Set Key. The key is written to the license file of this server only, and every process of it checks the license again at once. Here, it is the key of API Maker Launchpad: local, for this computer and private networks.

A card says one of four things: pending, until the first check, then valid, invalid, or local. The checks never refuse a request. A license that is not valid shows here, and as a warning in the header. Each server asks the license server a minute or two after it starts, every day around noon, India time, and at once after a new key. When it cannot be reached, the last answer stays.

A key is bound to the MAC address of its machine, and Reset MAC moves it.

Recap

To sum up. One page upgrades every server. Each one takes the package of its machine, and checks its hash. The program is checked before it is used. A watchdog goes back by itself. A server refuses what it cannot do safely. And Licenses shows the license of every server. Next: SSR websites, first steps. API Maker. Build faster, spend smarter, deliver better.