API Maker
The backend engine for the AI era
LaunchpadEpisode 56 7:57 10 chapters November 2026
Databases on your computer with API Maker Launchpad: eight engines in a few clicks, any version Docker Hub has, their instance in API Maker in one click, another version without losing the data, and one file to export and import everything a server holds.
In the playlists The complete course Launchpad
API Maker Launchpad runs databases on your computer. You get eight engines in a few clicks, any version that Docker Hub has, and their instance in API Maker in one click. You can move to another version without losing data. And one file moves everything a server holds.
Databases on a laptop usually mean work. You install a server for each engine, and for each version. You type connection strings by hand. An upgrade leaves the data behind. And every engine has a different dump tool. With Launchpad, each database is a container of the project, with its data in the folder. Its connection strings are written for you, and so is its instance in API Maker. You can move to another version, with the data moved too.
And one export file works for all eight engines. In this video: the databases of a project, a database added, its instance in API Maker, another version, data moved to a new major version, export, import, and good to know.
Open Databases, in the sidebar of Calm Home API. The project has three. crm runs on PostgreSQL, and catalog on MongoDB, and both are running. warehouse runs on SQL Server, and starts when needed. Each one runs in its own container, with its data in the folder of the project. Above them is every engine you can add, as many of each as you need. There are eight engines. MongoDB, as a single node replica set, so transactions work.
PostgreSQL. MySQL, MariaDB, and Percona Server. TiDB. SQL Server, its Developer edition. And Oracle Database Free. The versions follow the images of Docker Hub and of the Microsoft registry. A new release is offered once its image is published.
The sales of Calm Home need MySQL. Pick MySQL. A free port is already picked, and a strong password is made. Its name is sales, which is also the name of its instance in API Maker. Its version is the long term release of MySQL, the recommended one. It makes the database sales, and the connection string follows while you type. Its data stays outside the container, in the folder.
It can start with API Maker, start now, and be added to API Maker. Click Add MySQL. Its task shows each step. Docker is checked, and its configuration is written. Its image is downloaded, then the database is started. Once it answers, its instance is made in API Maker, and the toast says so. Its card shows it running on its port, with its instance sales, of the admin.
catalog runs, but it is not in API Maker yet. Click Create instance in API Maker, and now it is. How does it work? Launchpad starts API Maker with its own token. It calls the local run API of API Maker with that token, from this computer only. The credentials go into a managed block of the default secret of the admin. And the instance points at those keys, like any instance you make in the panel.
Open the card of crm. It has the connection string for API Maker, a connection URI, and JDBC, each ready to copy, plus the user and the password. It shows its database, its image, its container, and the folder of its data. Start with API Maker, Version, Logs, Data, and Remove are here too.
Version leads to Project Settings, with every version that the project runs. Pick a newer MongoDB for catalog. It keeps its data, in place. The dialog says what that means: MongoDB upgrades its data when it starts, and it cannot go back afterwards. Not now. Now the next major version of PostgreSQL, for crm. A new major version cannot open the data files of the version before it. So the dialog asks what happens to the data.
It can be moved to the new version, or the new version can start with no data. Pick Move. Click Change version. The data is exported from the old version into the backups of the project. The new version starts in its own folder, and the export is imported into it. Now crm is on the new PostgreSQL, with its data. Here are the rules. A newer version keeps the data, in place.
An older version, or another major version of PostgreSQL, cannot open it. So you move the data, or start empty. SQL Server and Oracle do not import what a newer version exported. So going back to an older version of them only starts empty. And nothing is deleted. The data of the version before stays in its folder. If anything fails, the version before is put back on its data.
Export, on the card of crm, writes everything its server holds into one file. It goes database by database, with the accounts made on it, while it keeps serving. Stop ends it, and leaves no file. You get one file, with the name of the database, its engine, and the time. The file is a zip. It has a manifest with the engine and its version, the databases, the accounts, and the size and SHA two five six of every part.
Then come the dumps. The tools of each engine do the work, inside the container of the server: pg dump all and pg dump, mysqldump or mariadb dump, mongodump with the oplog of the replica set, backup database, and Data Pump for Oracle. Import reads such a file. Here, it is the export of the production orders, made in Cloud mode. Before anything changes, you see the plan. It lists the database it replaces, the ones it makes, the accounts, and everything that stays as it is.
Replacing needs a yes. Click Import. Every part of the file is checked before the server is touched, then imported. At the end, the task says what is worth knowing.
Good to know. A file from MySQL, MariaDB, Percona Server, or TiDB can go into any of the four, with a warning for anything only one of them understands. The administrator that Launchpad manages is never exported or changed. So after an import, the connection of the folder and the instance in API Maker still work. On a Mac and on Windows, database ports listen on this computer only, unless you choose every network.
And the Logs page has the log of every database.
To sum up. Eight engines, with any version from Docker Hub. Connection strings are written for you, and the instance takes one click. A newer version keeps its data in place, and a new major version moves its data. And one export file works for every engine, with an import that shows its plan first. Next: many projects, their settings, and your editor. API Maker. Build faster, spend smarter, deliver better.
Length 6:50Launchpad
Length 6:53Cloud mode
Length 8:08Clusters
Length 8:09Day two