Ⅰ · The Bet
Databases become destinations.
Or they become storage.
The last decade of database investment rewarded raw engine capability — throughput, cost, HA, geo-replication. The next decade rewards what sits in front of the engine. Minimal is the governed runtime that converts a database into a destination enterprises build on directly.
Asset class
Runtime · governance · meta-logic
Fit
Database & infra platforms
Integration surface
One schema reader · four engines shipped
The Strategic Context
Engines are commoditising.
The surface is not.
Storage differentiation is narrowing. Every major engine now offers elastic compute, managed HA, and pay-per-query pricing. What customers increasingly buy is what the engine does for them — not how it stores bytes. Governed APIs, composable insights, customer self-service. The surface that sits on top of the engine is where the durable margin moves next.
Core Thesis
The engine that bundles Minimal
becomes a platform.
A database that ships governed Auto APIs, natural-language insights, customer-built apps, and autonomous signal discovery — out of the box, against a customer's existing schema — is no longer a database. It is an application platform. Enterprises stop writing backends against it and start writing against Minimal, against the database underneath. That is a far stickier relationship than a JDBC connection.
Why This, Why Now
Four bets.
All compounding.
01
AI favours runtimes, not generators
Generators produce artifacts that must be maintained forever. Runtimes infer at query-time. Every new AI coding tool strengthens the runtime argument; every release increases generator debt.
- →Constant surface-area AI
- →Zero-token steady state after translation
- →Schema change is not a breakage
02
Governance is now a purchase criterion
Role-scoped access, tenancy isolation, pre-query filter injection — these used to be enterprise tier. AI changes the threat model; they are now the price of admission.
- →Built-in from day one, not bolted-on
- →Enforced at the engine, not the middleware
- →Defensible against a "just use GPT over our DB" pitch
03
Self-service is the new expansion motor
Forge converts every customer into a builder inside their governed slice. Top-N customer-built apps become platform features. The backlog dissolves; the roadmap gets written by usage.
- →Zero-cost product discovery across N tenants
- →Network effect is data, not a social graph
- →Cross-tenant signal becomes defensible IP
04
Four engines. One runtime. A moat.
Postgres, MySQL, ClickHouse, MariaDB are shipped today. Oracle, SQL Server, Snowflake are in beta. A governed runtime that speaks every dialect is a rarer asset than any single-engine tooling stack.
- →Multi-Database access at runtime
- →Single governance model across engines
- →Portable; not locked to one engine
Acquirer Fit
Who gets
structurally better.
Database vendors — OLTP & OLAP
Adopters immediately ships an application-platform layer on top of their engine. Customer retention deepens. Developer-to-business-user expansion opens a new buyer. Competitive posture shifts from "faster engine" to "complete platform."
Data-warehouse & lakehouse platforms
A governed way to expose warehouse assets as first-class APIs and customer-facing apps, without a BI layer in between. Minimal turns the warehouse into a product surface rather than a reporting destination.
Infrastructure clouds
For hyperscalers, Minimal is the natural governance plane across their managed database offerings — one runtime spanning Postgres, MySQL, and analytics engines under one billing relationship.
Application platforms
For iPaaS, workflow, and internal-tool vendors, Minimal provides the data-access substrate they currently ask their customers to assemble from scratch.
For Investors
Why founders should
build on Minimal.
Every founder we speak to is running the same calculation: how much backend, BI, and reporting work can I avoid before I ship? Minimal collapses that calculation to zero. For the investor, that is the TAM — the universe of teams who would otherwise spend their first two engineering quarters wiring up data access.
"The right question is not whether Minimal should exist. It is which acquirer — or which founding team — gets to it first."