API Maker
The backend engine for the AI era
Per adminEpisode 75 6:16 10 chapters November 2026
Code on the native process needs its language on your servers. Install Node.js, Bun, Python, PHP, .NET, Go, Rust, Java or Kotlin from Sandbox Settings: every server downloads the official build, checks its checksum and runs it once. Each admin runs its own version, and nothing else on the server changes.
In the playlists The complete course Custom APIs & code Run in production
Native languages. Code on the native process needs its language on the servers. Now each admin installs the versions it needs from Sandbox Settings, on every server, from the official builds.
Code on the server machine usually means trouble. You open a session on every server, to install the language by hand. Every team shares one version, so one upgrade breaks the code of another team. Downloads come from wherever a blog pointed, without a checksum. And a new server has none of it. With API Maker, you pick a version in the panel. Every server installs it from its publisher, checked.
Each admin runs the version it chose. And a new server installs it by itself. In this video: where native code finds its language, a version of Node.js installed on every server, native code running on it, a second language, what stays apart for each admin, and a version removed.
Most code runs in sandboxes, and the image of a sandbox has its runtime. Code marked run on native process runs on the server itself, for the lowest delay, or for a program of the server. So it needs its language there. Until now, that was whatever the PATH of the server found, installed by hand. Now each admin installs the versions it needs, in a folder of API Maker, on every server.
Open Sandbox Settings, from the dashboard. Under the version of TypeScript is a new part: Native process. It is only for code marked run on native process. Today, that code runs on the server's own Node.js, the one its PATH finds, shown for each server. The releases come from nodejs.org as it publishes them, with their tags, their sizes, and a star on the recommended one. You see how much it takes, and the checksum that is checked.
Click Install. Every server downloads it, and says ready once its program reports the version that was downloaded. Each server reads the release from its publisher. It downloads the build for its own system and processor. It checks it against the checksum that the publisher gives. It unpacks it into its own folder, in the native languages folder next to API Maker. And it runs it once. Only a program that reports the right version becomes ready.
Nothing else on the server changes: not its PATH, and not the Node.js it had.
Open API Testing. Pick Custom APIs, then Runtime Check. It is a custom API on the native process, which says what runs it. Send. It runs on the server's own Node.js. Open Operations, then Sandbox Settings. Choose the version you installed. Open APIs and Logic, then API Testing, Custom APIs, and Runtime Check. Send again. The same code now runs on the version of the account, installed by Sandbox Settings.
Every admin chooses for its own account. Calm Home runs one version of Node.js, and another admin on the same server keeps the version it chose, or the server's own. Two admins who install the same version share its files on the disk. Removing it from one list never takes it from the other. And the admins who chose the same version share its runner.
Now a second language: Python. Today, its native code runs on the server's own Python. The builds come from python-build-standalone, the ones that uv installs, with pip. Click Install. It is ready, and chosen. The list of languages says what the native code of each one runs on. Every language of API Maker is here: Node.js and Bun, Python, PHP, .NET, Go, Rust, Java, and Kotlin. Each one comes from its publisher, checked with the checksum it gives.
They work on Linux, macOS, and Windows, on Intel and on ARM. Kotlin runs on the Java version you chose. And the packages of Sandbox Settings are installed with the chosen version.
Now a version you no longer need. The native code runs on it. Click Remove. The code goes back to the server's own Node.js, and the versions of the other admins stay. Say yes. The server deletes the build once no admin wants it, and no runner runs on it.
Good to know. A failed install says why, on the server where it failed, and Try again asks every server again. A new server installs what the admins want when it starts. A request that reaches a server while it installs waits for it, within the time of the request. And the choices are saved with the admin user, with a history, and through Git. You get official builds, checked, and the same version on every server.
Your code names no version. The settings of the account do. So code that an AI assistant writes runs on the version you chose.
To sum up. Native code needs its language on the servers. Sandbox Settings installs the versions you need, on every server. Each comes from its publisher, checked, and run once. Your native code runs on the version you choose. And each admin has its own versions, and nothing else changes. Next: deploying a new version of API Maker. API Maker. Build faster, spend smarter, deliver better.
Length 6:42Deploy
Length 6:36Sandboxes
Length 8:36Heavy APIs
Length 8:20Native APIs