API Maker
The backend engine for the AI era
LaunchpadEpisode 56 7:10 10 chapters October 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
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 move everything a server holds.
Databases on a laptop usually mean a server installed for each engine, and for each version, connection strings typed by hand, an upgrade that leaves the data behind, and a different dump tool for every engine. With Launchpad, each database is a container of the project, its data in the folder, its connection strings written for you, and its instance in API Maker, another version with its data moved, and one export file for all eight engines.
In this video : the databases of a project, a database added, its instance in API Maker, another version, its data moved to a new major version, export, import, and good to know.
Databases, in the sidebar of Calm Home API. The project has three : crm on PostgreSQL, catalog on MongoDB, both running, and warehouse on SQL Server, started on demand. Each runs in a container of its own, its data in the folder of the project. Above them, every engine you can add, as many of each as you need. 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. MySQL : a free port is already picked, and a strong password generated. Its name, sales : also the name of its instance in API Maker. Its version : the long term release of MySQL, recommended. The database it makes, sales, and the connection string follows as 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.
Add MySQL. Its task shows each step : Docker checked, its configuration written, its image downloaded, then the database started. Once it answers, its instance is made in API Maker : the toast says so. Its card : running on its port, and its instance, sales, of the admin.
catalog runs, but is not in API Maker yet : Create instance in API Maker, and it is. How? Launchpad starts API Maker with a token of its own, and calls the local run API of API Maker with it, 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.
The card of crm opens : the connection string for API Maker, a connection URI and JDBC, each to copy, the user and the password. 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 : every version of what the project runs with. 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 can not go back afterwards. Not now. The next major version of PostgreSQL for crm : a new major version does not open the data files of the one before.
So the dialog asks what becomes of the data : moved to the new version, or a start with no data. Move. Change version. The data is exported from the old version into the backups of the project, the new version starts in a folder of its own, and the export is imported into it. crm is on the new PostgreSQL, with its data. The rules. A newer version keeps the data, in place.
An older version, or another major version of PostgreSQL, does not open it : move the data, or start empty. SQL Server and Oracle do not import what a newer version exported : going back to an older one 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. Database by database, with the accounts made on it, while it keeps serving : Stop ends it, and leaves no file. One file, with the name of the database, its engine and the time. The file is a zip : a manifest with the engine and its version, the databases, the accounts, and the size and SHA two five six of every part, then 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 the export of production's orders, made in Cloud mode. Before anything changes, the plan : the database it replaces, the ones it makes, the accounts, and everything that stays as it is.
Replacing needs a yes. 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 of MySQL, MariaDB, Percona Server or TiDB goes into any of the four, with a warning for what only one of them understands. The administrator Launchpad manages is never exported nor changed : 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, any version of Docker Hub. Connection strings written for you, and the instance in one click. A newer version in place, a new major version with its data moved. One export file for every engine, and 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:06Launchpad
Length 6:14Cloud mode
Length 6:56Clusters
Length 7:15Day two