Company

Nobody’s best work is an API layer.

Yet almost every team builds one.
We built Minimal so yours never has to.

What we believe.

The schema already knows

A table definition contains almost everything an API needs. Writing that API by hand is transcription, and machines are better at transcription than we are.

English is enough

The person who understands the job should not need a second language to describe it. Not a policy file, not a config format, not SQL.

Data should not have to move

Every copy is a new place to secure and a new thing to go stale. So we read where the data already lives and keep nothing.

01What we build

01 / 06

You already run

Your database

15 engines · 5 file formats · unchanged

Minimal

Derived at runtime

RESTfor apps

MCP toolsfor agents

Identityfor both

ClickHouse · Postgres · MySQL · MariaDB · Aurora MySQL · Percona · TimescaleDB · Vitess · TiDB · CockroachDB · Citus · YugabyteDB · SingleStore · StarRocks · RisingWave

Point at the database. Everything else derives.

No migration, no code generation, no copy of your data. No credentials held, no port opened, nothing persisted.

02The problem

02 / 06

The data is there. The access is not.

Weeks per integration. One backend engineer per data source. The same work, rebuilt every time the schema moves.

03Why now

03 / 06

Every consumer of your data used to be an app you controlled. Now it is also Claude, Cursor, ChatGPT, Gemini and every agent built on them, all asking through MCP.

One access layer. Apps, agents, identity.

Hand-built APIs already cost weeks per consumer. Agents add a new kind of consumer that expects MCP, scoped per identity. Building it twice is not an option. Minimal derives both from the schema.

05Proof

05 / 06

3.9MDownloads

~1MEvents a day

<1msAverage API latency

$15Infrastructure a month

Already carrying a million events a day.

Talk Dialer, a live consumer app on Minimal. Real users, every day. API Bay and Chat Studio launch October 2026.

06Write to us

06 / 06

founders@littlebit.in

Talk to the founders.

One address, read by the three of us. Customers, partners and anyone curious about how this is built.

Book 30 minutes →Other addresses

Get in touch.

A booked session is the fastest route to an answer — it is a real conversation with the people who built the thing, not a qualification call.

Book a session

Thirty minutes on your data or ours. Bring a database, a question, or a security questionnaire.

Open the calendar

Email

Four addresses, so your message lands with the person who can answer it. We read everything that arrives.

Contracts and notices

legal@littlebit.in

Your data and your rights

privacy@littlebit.in

Vulnerability reports

security@littlebit.in

Complaints, to our Grievance Officer

grievance@littlebit.in

Documentation

If you would rather read first and talk later, start here.

Docs

Whoever sets up your first session is who you will still be talking to a year from now. That is not a support policy — it is a consequence of being small on purpose.

Schedule a Personal Session See the products