Changelog

What shipped, when.

Written for people who want to know what changed rather than what we are excited about.
Newest first.

Minimal Core: a free 60-day trial licence

  • A free trial licence for Minimal Core on your own hardware: 3,000,000 requests, 60 days, every feature, no card, no commitment.
  • Sign in with Google or GitHub at license.littlebitlabs.com, with any email address. No marketing follow-up.
  • Six steps from sign-in to licence file, shown on the Minimal Core page.
  • Privacy and the consent notice now say "email address" rather than "work email address", and name Google and GitHub sign-in as a source of your name and email.

Terms: users per plan, and the Minimal Core non-compete

  • §3.2: Users are not licensed individually. Each plan includes the number of users published for it, as applicable by product. It no longer says paid plans permit unlimited users.
  • §3.10: While you use Minimal Core under any licence, paid or trial, you may not build or market a competing product. "Associates" becomes "sister companies". A grant binds for seven years from the grant, however long the licence was used.
  • §3.11: Both changes apply at once to new sign-ups. For an organisation that accepted the Terms earlier, they take effect on the later of 3 December 2026 and 30 days after notice.

Terms: protecting the software

  • Terms of Service §13.4 to §13.14 added: you may not reverse engineer, decompile, decrypt or modify Minimal, defeat licence validation, extract outputs to train a competing model, or probe the Hosted Service without permission.
  • Rights the law gives you are kept (§13.6), and good-faith security research is welcome: report to security@littlebit.in (§13.7).
  • A breach of §13.5 cannot be cured, ends the licence, and carries whatever compensation a court decides (§13.9, §13.13). §14.2, §14.4, §14.6 and §16.2 are amended to match.
  • New for everyone who accepts the Terms from 3 November 2026. For existing customers they take effect on the later of 3 December 2026 and 30 days after our notice (§13.14, §18.1). See the Terms.

Chat Studio, in beta

  • An AI chatbot for your website that answers only from the knowledge you give it — your pages and documents — never the model’s general knowledge. Answering from Minimal-served data goes public in December 2026.
  • Ten personas at launch: support, sales, docs, onboarding, HR and more. Each sets the voice and what it declines to answer.
  • Bring your own Claude, OpenAI or Gemini key on every tier. Free tier, no card. One line of code to embed as a floating widget or inline panel.
  • See Chat Studio.

API Bay pricing is now two-sided

  • Using data: 100 requests a day free forever, then a prepaid wallet at $1 per 1,000 requests. No overage bills by construction.
  • Publishing: flat parking from $5 a month (1 GB) to $625 (1 TB), a $1 per 5,000 traffic meter, and any price you set from $0.20 per 1,000. 0% commission.
  • The old Free/Build/Scale plan matrix for API Bay is retired. Details on pricing.

Fifteen engines, tested and listed

  • ClickHouse, Postgres, MySQL and MariaDB lead the tested set.
  • Eleven more engines verified, including TimescaleDB, CockroachDB, YugabyteDB, Citus, RisingWave, TiDB, SingleStore, StarRocks, Percona, Vitess and Aurora MySQL.
  • Flat files supported alongside live databases: CSV, Parquet, JSON, NDJSON and Excel.

Identities carry per-action permissions

  • Read, write and delete are separate grants rather than one access level.
  • An identity that can list a table no longer implies the ability to change it.
  • MCP tools exist only for the tables you chose to expose.

Your own MCP server, over OAuth

  • Every connected database now stands up an MCP server without you writing one.
  • Authentication is OAuth rather than a shared secret in a config file.
  • Tools are scoped to the exposed tables.

Want to know what is next?

The roadmap is short and we would rather discuss it than publish it. Ask in a session and you will get a straight answer about what is coming and when.