What is scheduled, and what shipped this month.
One stream to mid-December 2026, each with the month it lands in. Nothing here depends on a cloud provider being set up; that work is scheduled separately, and this page does not promise it.
Scheduled
October to December 2026
- December 2026
The public registries. The packages on the public registries, when that release is decided.
Shipped in October
What landed in October
Shared or dedicated compute
Run on a node of your own, or share one and pay only your share of it, minute by minute: $0.060 a processor-hour and $0.008 a GiB-hour. Your charges name the size you ran on and for how long.
AI servers you allocate
An administrator attaches the servers that do translation, embedding, transcription and the assistant. Each credential is sealed and never shown again, work is spread across the servers, and it moves on when one stops answering.
Translation across more servers
Translation work is shared across every translation server you attach, so the way to translate more at once is more servers, each with its own GPU.
Spend checked at every stage
What work actually costs is checked against your budget at every stage, on every service, and work stops above 95% of it.
Shared compute that sizes itself
A shared node grows when demand rises and comes back down when it falls, always inside its size’s range. Ten heavy queries that took 287 seconds each took 137 once the node had grown, and when demand fell away it settled back to its floor and held there.
Only real charges on the pricing page
The pricing page in the UI now lists only the meters that carry a charge, and says why the rest carry none.
Shipped in September
What landed in September
PostgreSQL, against the tools you own
DataGrip, DBeaver, Power BI, psycopg, Npgsql and the JDBC driver each connect, browse and query, measured tool by tool, with a compatibility page per tool and what is refused said by name.
An Entity Framework Core provider
DataOil.EntityFrameworkCore: your own DbContext checked against each database's schema as it is today, LINQ in the engine's own dialect, every save guarded by the record's version, and migrations that refuse to overwrite what something else changed. A LINQPad 9 driver browses and queries any database with no classes written.
Rights for the groups you already have
A group your own directory asserts at sign-in holds an engine role, down to a collection, a column or a property - not only a console role and a database. The console acts on the engine as the person, so a rule about who may read a column is one the engine applies on every door.
A grant per database, from the console
A role's grant carries the database it holds in, so a permission written for one database stays there and an edit to the role never widens it.
Roles for a customer's own administrator
The Roles & Permissions page is a tenant administrator's for their own tenant, and offers the directory groups tokens have carried as members.
Client packages
DataOil.Client for .NET, dataoil for Python and @dataoil/client for JavaScript: the two headers, the streamed answer, typed errors and the retry a lost race needs, built in.
Retrievers and an MCP server
LangChain and LlamaIndex retrievers in the Python package, and @dataoil/mcp with four tools over one database for Claude Desktop, Cursor and any Model Context Protocol client.
The backups a database has, wherever they are
A nominated database's chain is listed from the instance its policy names, so the list a customer sees at the console is the chain a restore would use.
Under consideration
Not scheduled, and said so
Three things we are weighing for the quarter after. They are here so their absence above is not mistaken for a decision against them.
A one-command quickstart
the engine, the object store and the console with a seeded database, for a first hour without a call.
A self-serve sandbox tenant
a scratch tenant with a small allowance, provisioned from a sign-up rather than a conversation.
More retriever frameworks
the same statement-backed retrieval for whatever framework a customer's team already runs.
Plan against it
Tell us which of these your move waits on.
If the packages on the public registries are what you are waiting for, say so - the proof of concept can be scheduled to land when they are.