API Maker

The backend engine for the AI era

MaskingEpisode 35 3:56 10 chapters November 2026

Database Name Masking: One Name in Code, Any Database per Developer

Your code names the production database, while your laptop, your staging server and your teammates have other copies. Database name masking keeps one name in the code and lets each account map it to another database: the same address, every API following the mask, and nothing committed to Git.

In the playlists The complete course Migrations & tenants

Chapters

What you will learn

  • One database name in the code
  • A mask, set in User Info
  • The same address reads another database
  • The Databases panel, and what follows the mask
  • Removing a mask
  • One name for people and AI assistants
In the docsMask database names
Transcript503 words · click a time to play from there

Intro

Your code names the production database. But your laptop, your staging server, and your teammates have other copies. Database name masking keeps one name in the code. And it lets each account point that name to another database.

Database names, the usual way

Usually, database names live in environment files. Someone renames them before every pull request. Two developers on one server write into the same tables. And code written by people or by AI hard codes the name of one environment. With API Maker, the code and Git keep the production name. Each account points it to its own database. And every API follows the mask. In this video: one name in the code, and many on servers, the same address before a mask, a mask in User Info, the same address after it, what follows the mask, and how to remove it.

One name in the code

The code, its schemas, and Git name the database sales. Production reads sales. Nisha reads her own copy, sales_nisha. And Daniel reads sales_daniel, on the same MySQL server. Nobody renames anything, because the mask lives on the account, not in the code.

The same address

First, we get a token of the API user of the account. Then we read the orders of sales. There are one hundred and eighty of them, from CH 2026 0001 on.

A mask in User Info

Open the user menu, then User Info, and its section Masked Database Names. There are none yet. Click Add. Pick the instance, mysql. Give the name in the code, sales, and its name on this server, sales_nisha. Click Add. The row is new, and not saved yet. Click Update User Info.

The same address (2)

Now we call the same address again, without changing one character. We get two orders: the test orders of Nisha. The API read sales_nisha. The Databases panel of mysql lists sales, with a mask. Its tooltip gives the name on this server. The real sales is hidden from this account. Its tables are the tables of the copy.

What follows the mask

Every generated API follows the mask. So do the custom APIs and hooks that use g.sys.db calls. Index Maker works on the masked database too. Git never carries a mask, in a commit or a pull. SQL text that you write yourself is not changed, and the security report says when a mask is in use.

Removing it

To go back, delete the row, confirm, and update. The same address reads the one hundred and eighty orders of sales again.

One name for people and AI

The production name is the only name in the code, and in Git. Code that an AI assistant writes uses that name too, and it still runs on the copy of each developer. Each copy is a database of its own. So the user of the instance needs rights on it, as on any database.

Recap

To sum up. There is one database name in the code. Each account sets its mask in User Info. The same address reads another database. Every API follows the mask, and Git never carries it. Next: API Testing in depth. API Maker. Build faster, spend smarter, deliver better.