API Maker
The backend engine for the AI era
ArchitectureEpisode 70 7:26 11 chapters November 2026
How API Maker works, in six minutes: the life of one request through Caddy, the token and groups, your hooks, the API and one envelope. Then the four families of APIs, the two tokens and their gates, where your code runs in eight languages, the servers, what a save does and why everything is in git.
In the playlists Start here The complete course
API Maker is a server you install, not a library you add to your code. In this video, we follow one request, from your app to your databases and back. And you see the pieces that make it work.
A backend is usually many parts: a web framework, an auth layer, a cache, a job runner, and a deploy pipeline. They are glued together by hand, each with its own rules. With API Maker, one server does all of it. Every request takes the same path, through the same checks. And everything you build is a file in Git. In this video: the life of a request, one base URL, two tokens and two gates, where your code runs, the servers, what a save does, and Git.
Let us follow one request. Your app calls a URL, with the token of its API user in a header. Caddy handles HTTPS, and passes the call to API Maker, on one port for the APIs and the WebSockets. The token and its groups come first. No valid token gives a four hundred and one. And no group that allows this API gives a four hundred and three. Then your pre hooks run.
They can add a filter, change the request, or answer at once. Then the API itself runs: a table, read or written through its schema, your code in a sandbox, or a system API. With caching on, Redis answers first. Post hooks can change the answer, and the reply goes back in one shape. WebSocket subscribers are told, and the call is logged and counted.
Every API lives under one base URL, in four families. Schema APIs: the operations of every table, through its schema. Generated APIs: the same operations, without a schema. Custom APIs: your function, in one of eight languages, on the path and method you choose. System APIs: ready made ones, for tokens, encryption, the cache, events, and indexes. And there is code that nobody calls over HTTP: events, schedulers, initializers, migrations, hooks, and test cases.
API Maker runs it for you. In the panel, every table lists its APIs. The products of MongoDB have thirty four: seventeen through the schema, and the same seventeen without it. Nobody wrote them. A URL of a table reads from left to right. First the family, schema. Then the API path of the account, calmhome. Then the instance, mysql, the database, sales, and the table, orders. Then the operation, which is empty for get all.
The query follows, in plain parameters. And the answer has success, the status code, and the data. Every API answers in this shape.
There are two tokens. The API user is an application: your web app, your mobile app, or a partner. Its token goes in x-am-authorization, and its groups are the API gate. They say which APIs, tables, and fields it can use. The person is a row of your users table, or a Google, Microsoft, or AWS identity. An auth provider makes its token. A pre hook is the row gate.
Of the rows an API reaches, it keeps only the rows of that person. Public APIs skip both. A new account allows everything. So replace its default API user and group before you go live.
Your code runs beside the server, not inside it. A sandbox is a Docker container of the account and its language, with only the packages that the account adds, and a time limit for every run. There are eight languages: TypeScript on Node.js or Bun, Python, PHP, C#, Go, Rust, Java, and Kotlin. Code marked run on native process runs on the machine itself, for a browser, or for the lowest delay.
Settings and schemas are TypeScript that API Maker runs the moment you save. And all of it gets the same g: the request, the response, and every API of API Maker. From the dashboard, open Sandbox Settings. You see the eight languages, each with the image it runs in, ready on this server. Python has its image, and the packages of the account. Nothing is downloaded while code runs.
On a server, API Maker is one program, run by systemd, with its threads on every core. Caddy stands in front, for HTTPS. MongoDB holds the data of API Maker itself: accounts, schemas, code, and logs. Your data stays in your databases, wherever they are. Redis holds the cache, the counters, and what the servers share. API Maker serves the admin panel, on its own port. More servers behind Caddy make a cluster.
A save reaches every server through Redis, and each scheduler runs once per tick.
A write through a schema API passes these stages, in order. Keys that the schema does not know are refused. Values get their types. Text is trimmed and cased, and defaults are filled in. Your conversion function runs. Fields are encrypted or hashed. Ids are made. Then the rules and your validator decide. Anything wrong comes back at once: four hundred, with one entry for each problem, and nothing is saved.
Generated APIs skip all of it.
And everything you build is a file. Schemas, settings, custom APIs, hooks, events, schedulers, utility classes, migrations, test cases, and the security report live in one Git repository. The panel commits and pushes, and a pull on another server is the deployment. Secrets never go to Git. Each server keeps its own.
That is the point of one path. Every request meets the same gates, the same hooks, the same answer shape, and the same logs, whoever wrote the API: you, a teammate, or an AI assistant. Code that an assistant writes cannot skip a check, because the check is not in its code.
To sum up. A request goes through the token and groups, pre hooks, the API, post hooks, and one answer shape. There are four families under one base URL. There are two tokens, and two gates. Code runs in sandboxes, in eight languages, with one g. There is one program per server, with MongoDB and Redis beside it. And everything is in Git. Next: your first API, in ten minutes.
API Maker. Build faster, spend smarter, deliver better.
Length 6:35Quick start
Length 5:25Generated APIs
Length 6:54Authorization
Length 6:36Sandboxes