No schema, no setup, no scans: how the Skapi database works, and why it is built for AI agents

The question we get more than any other is some version of "how do I set up my database?" Where is the schema designer. Where do I define the tables. What about indexes, migrations, the query planner. The answer is that you do not. There is nothing to set up. You write a record, and the table exists. You delete the last record, and the table is gone. If that sounds like something that cannot possibly hold up under real load, this article is for you. It explains the model behind the Skapi database, schema-free and index-on-write: why it does the work you reach for a relational database to do, why it never falls into the full-table scan that quietly drains production budgets, why the same mechanism is what keeps your data secure, and why it is the right shape for a world where AI agents write most of the code.

The question, answered once

A Skapi project has no database to set up, because there is no moment at…