API Maker
The backend engine for the AI era
Native APIsEpisode 65 8:20 10 chapters November 2026
Code you mark Run on native process runs on the machine of API Maker, with the language API Maker finds on its PATH. API Maker Launchpad finds what your Mac and your servers have, and installs Node.js, Bun, Python, PHP, Go, Rust, .NET, Java or Kotlin from their publishers, every download checked against its checksum.
In the playlists The complete course Launchpad
Code that you mark Run on native process runs on the machine of API Maker. It uses the program of its language that API Maker finds on its PATH. In this video, API Maker Launchpad finds those languages, and installs the versions you choose, on your computer and on your servers.
Languages for native code usually mean trouble. Runtimes are installed by hand, with brew, nvm, or apt. Your laptop and your servers run different versions. Nobody checks the downloads. And API Maker does not see the PATH when an app starts it. With Launchpad, it first finds what each machine has. The versions come live from their publishers. Every download is checked against its checksum. And one choice runs on your computer, and on every API Maker server.
In this video: the native process, the languages of a new project, the Languages page, Full Docker, the languages of an environment, what a deployment does, and a language for one server.
A sandbox runs code in Docker, with the runtime of its image. Code marked run on native process runs on the machine of API Maker instead. It runs in one runner per language, shared by every account, for the tools that machine has, like a browser. API Maker starts that runner with the program it finds first on its PATH: node, python3, php, go, cargo, dotnet, java, or kotlinc. So that machine needs the language, in a version that API Maker runs.
A new project asks for no language in its setup. Its code runs in the sandboxes until you choose some, on its Languages page. Launchpad first looks at what this Mac has: the PATH, and where Homebrew, nvm, Volta, pyenv, rustup, or SDKMAN put the languages. Each one shows its version, and whether API Maker can run code on it. This Java is a runtime without javac, so it cannot build Java code.
Use them picks every one that works. Nothing is installed for them. Or you can pick a version that Launchpad installs. The versions come live from nodejs.org, the newest line first. Long term support is marked, and the version the sandboxes use is recommended. This one is already installed. For Java, it is the JDK of Eclipse Temurin. The card says what it downloads and how big it is, how much disk it takes, and the checksum its publisher gives.
Below the cards, you see what the choice installs, and where. It is one folder in the home folder, for every project. A version is installed once, and shared by the projects that choose it. Nothing goes into the system, and no shell profile changes. Click Save languages. API Maker reads its PATH when it starts, so it offers a restart. Click Restart. A step of the start, Languages, downloads Java, checks it, and asks the program for its version.
API Maker starts with their folders first on its PATH. Only API Maker and its runners see them. Where do the versions come from? From the publisher of each language, read live, and kept for six hours: nodejs.org, go.dev, static.rust-lang.org, Eclipse Temurin, the releases of .NET, Bun, Kotlin, and the Python builds that uv installs. Only the versions that API Maker runs are offered. Every download must match the SHA-256 or SHA-512 that its publisher gives, or it is refused.
And Go and Rust build code with a C compiler, so the card says when one is missing.
The dashboard of Calm Home API shows its languages: Node.js twenty four, installed by the app, and the Python of Homebrew. On the Languages page, API Maker runs with them. You see what the app installed, the size of each version, and the projects that use it. And you see what this Mac has, usable or not, and why. Now pick Node.js twenty six, for the next APIs. Save it, and restart.
The start installs the new version, and API Maker runs with it.
And in Full Docker, where API Maker runs in a container? The Linux builds of the same languages are mounted into it, read only. PHP, and the C compiler of Go and Rust, come with its image, built again with them. The languages of this Mac do not run there. So switching to Full Docker turns them into versions that the app installs.
Now Cloud mode, and the production environment of Calm Home. Its Languages tab shows the same cards, for the Ubuntu of its servers, on ARM. Every API Maker server of the environment gets these languages, even the ones added later. The Python of Ubuntu is found on app-1, so choosing it installs nothing. Go comes for Linux on ARM, from go.dev. On each API Maker server, they go in /root/languages.
It is saved. Server by server, you see what each one has: Node.js installed, the Python of the server, and Go, for the next deployment. Review the deployment is one click away. And the choice is remembered. A new environment starts with these languages, and its dialog names them.
What does the deployment do? Each server downloads its languages itself, from their publishers, and checks them. Nothing goes through your computer. Each version gets its folder under /root/languages. PHP comes from apt, with FFI. A file, languages.env, puts their folders first on the PATH of API Maker, under systemd, PM2, or in its container. API Maker restarts with them, one server at a time when several are serving. Then the versions it no longer uses are deleted.
The list of servers shows the languages of each one. Open app-1, and its Languages tab. It shows what API Maker runs native code with there, here the languages of production. It shows what Launchpad installed, the room it takes, and what Ubuntu has. Click Install a language. Pick Java, version twenty five, read from Eclipse Temurin for the processor of this server. Choose this server only, or every API Maker server of production.
Click Install. The server downloads it and checks it, and API Maker restarts with it, in seconds. Now Java is on app-1.
To sum up. Launchpad first finds what each machine has. Versions are read live from their publishers, and every download is checked. They go in one folder, and only API Maker sees them. One choice serves every API Maker server, and is remembered for the next environment. And a server can have its own languages. Next: sandboxes, runtimes, and packages. API Maker. Build faster, spend smarter, deliver better.
Length 6:36Sandboxes
Length 9:33Launchpad
Length 6:53Cloud mode
Length 7:42Upgrade from v3