API Maker
The backend engine for the AI era
LaunchpadEpisode 57 6:50 9 chapters November 2026
Several API Maker projects on one computer, each in its tab and on its own ports. Every setting of a project on one page, a project deleted with everything it made, and your editor kept in sync with API Maker, both ways, with the local client.
In the playlists The complete course Launchpad
You can run several API Maker projects on one computer, each in its own tab and on its own ports. In this video, you see their settings, a project deleted with everything it made, and your editor kept in sync with API Maker, both ways.
Working on several backends usually means trouble. Only one runs at a time, and the others are stopped to free their ports. Settings are spread over env files and scripts. Containers and volumes of old projects are left behind. And code is edited in a browser tab, far from your editor. With Launchpad, projects run side by side, each on its own ports. Every setting of a project is on one page.
A project is deleted with everything it made. And a folder on your computer stays in sync with API Maker. In this video: the projects on this computer, a tab for each, Project Settings, deleting a project, the Local Client, and how it syncs.
Here is the Projects card of the welcome screen. Under Running, we see Calm Home for Business, in Full Docker, with the processor and memory of its containers. Under Recent, we see every project opened on this computer. Each one shows its stack, the version of API Maker, its MongoDB, Redis, and every database, with their logos. Calm Home API is pinned. A folder on a USB drive that is gone says so.
The search looks at names, folders, versions, and databases. postgres seventeen finds the projects with a PostgreSQL seventeen. The play button starts a project in the background. try-oracle, a project for trying Oracle, starts on its own ports, and says when it runs. Now Running lists both, each with Admin panel, Open, and Stop. Click Open, and the business project opens in its tab, with its dashboard on the screen.
The other projects keep running.
Each project opens in its own tab, and each tab remembers its page. The plus opens a list of the running and recent projects, and Open a folder. Typing finds a project, and Enter opens it. Right click on a tab. You can close it, while the project keeps running. You can close the others, stop the project, or show its folder. You can drag tabs to reorder them, and close them with a middle click.
The project picker of the sidebar lists the running and recent projects too. And on the keyboard, Command and a number go to a tab, Command T opens the plus, and Command W closes a tab.
Open Project Settings, for the project on the screen. First, the architecture: Native or Full Docker, switched while the project is stopped. Then the version of API Maker. You see the one installed, one native program, and every version on npm, to install another. Then the versions of what it runs with: its MongoDB, its Redis, and every database, as video fifty six showed. Then its name, and its license key: the key for local runs, or your own.
Next are its ports, and where the database ports can be reached from. Then extra environment variables for API Maker. Here, it is the time zone of its schedulers. They go into the env file that the app writes. And last, the danger zone, to delete the project.
The Oracle trial is over. The bin icon of a recent project deletes it for good. The confirmation lists what goes: its containers, volumes, and networks, and the folder, with its size. Files in the folder that Launchpad did not make are pointed out first. Type its name, and it is gone, from the disk and from the list.
The Local Client page keeps a folder on this computer in sync with API Maker, both ways. You edit custom APIs, schemas, schedulers, hooks, and every other item in your editor. And what you save in the admin panel lands on the disk. Its card shows what was sent, received, and deleted, the full syncs, and the Git branch with its changed and unpushed files. Open in lists every editor found on this computer, the terminal, and the file manager.
The console shows the local client as it works, with each item next to the icon of its category. You can filter for what was received, or what went wrong. Here, it is a utility class that API Maker could not save, fixed a minute later. Or you can show everything. If a sync stops by itself, the card turns red, with the reason. Now set up another folder. Where is the code kept?
It can be GitHub, GitLab, or another Git host, with a token that API Maker keeps encrypted. Or it can be a Git repository on this computer, which is recommended. It has versions, and nothing leaves this computer. Pick the folder, then click set up and start. The repository is made, attached to API Maker, and checked out. A sync token is made, and the files of the local client are written.
Then it starts, and brings every item into the folder. Nothing is committed until you say so. It is ready for code.
Here is how it works. The local client is the one that ships with API Maker, a small Node.js program. Launchpad downloads Node.js for it once, and keeps it for every folder. It talks to API Maker over its WebSocket. A repository made on this computer is a bare Git repository, served on one two seven point zero point zero point one, with a secret in its address. API Maker pushes and fetches there.
And when the app is gone, a watchdog stops the local client.
To sum up. Projects run side by side, each in its tab, on its own ports. Every setting of a project is on one page. A project is deleted with everything it made. And your editor stays in sync with API Maker, both ways. Next: Launchpad, and API Maker on your own servers. API Maker. Build faster, spend smarter, deliver better.
Length 6:53Cloud mode
Length 8:08Clusters
Length 8:09Day two
Length 8:20Native APIs