Local preview available
A database built
around the commit.
Transactions, durable state and replayable events in one history. Build locally with Polybase today. A hosted SaaS is coming soon.
Free evaluation · macOS & Linux · v0.1.0-preview.1
projects/one → active
projects/two → plannedone active
two plannedcommit #1
2 mutationsIllustration of the local commit model.
From a commit to a live view
State and change,
kept together.
Polybase uses committed transaction records to recover state and read events. A snapshot gives you a starting position. Later changes follow strictly after it.
Native query subscriptions return filtered snapshots and net changes per transaction. Resume with a saved cursor, within retained history.
Understand the history boundary ↗A real local workspace
Try the database.
See each change.
Browse byte-key records, stage a batch and commit it explicitly. The included console shows query changes, durable request outcomes and storage controls.
The preview runs on your machine. This screenshot uses synthetic records.

What you can evaluate
Atomic writes and recovery
Commit several mutations together. Reopen the directory to recover committed state. Detected protected corruption fails closed.
Concurrent local transactions
Optimistic validation, validated MVCC snapshots and declared-key locking share one bounded commit sequencer.
Snapshots and resumable queries
Query byte-key ranges with whole-value predicates. Checkpoint or compact explicitly; older history can expire.
A three-node research lab
Explore one fixed replicated partition on loopback, with majority acknowledgments, leader changes and original-request reconciliation.
Next up
Polybase SaaS
is coming soon.
We’re preparing a hosted version of Polybase. Until then, download the local preview and explore the database on your own machine.
Hosted signup is not open yet. No launch date or hosted service is included in this preview.
Download the previewBefore you start
A few useful details.
Is the download free?
Yes. The executables are free for personal or internal evaluation, experimentation and development. The source remains private. Production use and commercial redistribution are outside the evaluation license.
Do I need Rust or a cloud account?
No. Extract the package and run the included tools. Python 3.10+ is needed only for the optional three-node launcher.
Is this ready for production?
This is an experimental evaluation preview. Use disposable data. There is no production support or service-level agreement. Read its guarantees and limits.
What does “events in one history” mean?
The same committed records that reconstruct local state also produce commit events. A snapshot position and later deltas share that history. Delivery can repeat; your application must save its result and cursor together.