API Maker
The backend engine for the AI era
InstallEpisode 61 8:37 10 chapters November 2026
One command on a fresh Ubuntu server installs API Maker version four, its MongoDB and Redis, systemd to keep it running, and Caddy in front. A new server of Calm Home goes from nothing to its admin panel in under two minutes, then upgrades with the same command, keeps every version, and grows to more servers.
In the playlists Start here The complete course Run in production Upgrade from v3
One command on a fresh Ubuntu server installs API Maker version four, its MongoDB and Redis, systemd to keep it running, and Caddy in front. In this video, a new server of Calm Home goes from nothing to its admin panel, in under two minutes.
A backend server usually takes a lot of setup. You set up a runtime, a process manager, and a web server by hand. You run databases in containers, with their passwords and their volumes. And you spend a day writing notes that nobody else can repeat. With API Maker, one command does it all. One program serves the APIs, the WebSockets, and the admin panel. And the same command upgrades it later.
In this video: the command, its four questions, what the installer does, the new server in a browser, systemd and a restart, an upgrade, more servers, and the move from version three.
On the new server, as root, download the installer, and run it. --default takes the default answer of every question that has one. --version picks the version. And --ip gives the public address. If you leave it out, it is found by itself, and you are asked to confirm it. First, the server is checked: root, Ubuntu, the processor, glibc, systemd, and the disk. Whatever the installer needs, it installs.
Four questions remain, each with its default in brackets. Is this a primary server, the first of an installation? Yes. Caddy in front? Yes. SSL? Not now. With yes, you get Let's Encrypt certificates for your domains, renewed by Caddy. And this is not a QA, UAT, or production environment of a project. The installer sums it up: one port for the APIs and the WebSockets, one for the admin panel, and new containers for MongoDB and Redis.
Then it works. It installs Docker, MongoDB, as a replica set of one member, for transactions, Redis, and the Oracle client, for Oracle instances. Then API Maker itself: the package for this processor, read from npm, checked against the sha512 that npm publishes, and run once before anything changes. Its settings are written, systemd starts it, and the installer waits until it answers. Caddy comes last, with its Caddyfile. Under two minutes later, here is the summary.
Both services are active, and enabled at boot. It says where everything is, and lists the secrets it made, hidden here. Here are the addresses: the admin panel on port eighty, the APIs on eighty eighty, and the WebSockets on eighty eighty one. Here are the two default users. You change their passwords at the first sign in. And here are the commands to start, stop, watch, and upgrade API Maker.
On the server, there is one program: api_maker_be. It answers the APIs and the WebSockets on one port, thirty eight, two four six, and serves the admin panel on forty six twenty six. Caddy passes the public ports to them. MongoDB and Redis run in Docker next to it, and the code of your accounts runs in Docker sandboxes. Nothing from Node.js is installed on the server. In a browser, the address of the APIs answers with its own page: API Maker, primary, running.
It shows its version, its threads, and under a hundred megabytes of memory. /ping answers pong. That is what a load balancer asks. Port eighty is the admin panel, version four. Sign in as admin, change both default passwords, as in video forty three, and add your databases, as in video two.
systemd runs API Maker as the service api_maker_be. Now a restart. It answers again a moment later. The process was told to stop, its connections were closed, and the new one started. And if it ever dies, systemd starts it again a second later. Here, it answered right after. It also starts with the server at every boot. A stop is graceful. Calls in flight get thirty seconds to finish.
WebSocket clients are closed cleanly, with code one thousand and one: server is going away. The schedulers move to the other servers. So a restart or a new version drops no request.
To upgrade, run the same command again, with the version. The settings of the earlier install are the defaults. MongoDB stays, with its data, and so does Redis. The ports and the secrets stay. The settings and the Caddyfile are backed up before they are written. And a new version takes the place of the old one only once it answers. One that does not start is rolled back by itself.
All of it takes under a minute. Each version keeps its own folder in releases, for the last three, and current points to the one that runs. Going back by hand is one link and a restart. Everything lives in the home folder of root. The program is in projects, the settings are in config, with their backups, the logs are in logs, rotated past fifty megabytes, and the data of MongoDB and Redis is in docker-data.
The .env file holds every setting, with what it is for. Change a line, restart, and you are done.
More traffic? Run the same command on a second server, and answer secondary. It installs only API Maker, using the MongoDB and Redis of the primary. It prints the line to add to the Caddyfile of the primary, so one address spreads the calls over both. There are no sticky sessions, because the state is in MongoDB and Redis. And every server shows on the Servers page. Do you have a server of version three, the Node.js edition?
Run the installer there, and keep MongoDB and Redis. Version four takes the place of the service api_maker_be, with the same data and secrets. PM2 lets it go. api_maker_fe disappears, because the server serves its own panel. And the WebSockets move to the port of the APIs. Behind Caddy, the address of your clients does not change. On a real server, the installer also sizes what Linux allows. It sets as much swap as memory, from two to eight gigabytes.
It sizes the table of connections and the open files to its memory. A server with sixteen gigabytes took over a million WebSocket clients. At every start, API Maker says how many it can take, and warns when the system allows fewer. Here, in a container, the kernel is shared, and the log says so.
There are other ways to run it. API Maker Launchpad, on your own computer, in video fifty five. Launchpad, which installs and deploys whole clusters over SSH, in video fifty eight. And the page Upgrade/Downgrade Engine, for the next versions, from the admin panel, in video forty seven.
There is one installer for every server, with the same folders, the same service, and the same logs. Every question is also a flag, so a cloud-init script or a CI job can install a server with nobody at the keyboard. And nothing is changed unless it was backed up first.
To sum up. One command on a fresh Ubuntu server. Four questions, each with a default. Docker, MongoDB, Redis, API Maker, and Caddy, checked and started in under two minutes. systemd keeps it running, and the same command upgrades it. Next: API Maker on your own computer, with Launchpad. API Maker. Build faster, spend smarter, deliver better.
Length 9:33Launchpad
Length 6:42Deploy
Length 7:03Scale out
Length 6:18Upgrade from v3