Append-only temporal data engine
The data engine for applications that need one reliable source of truth, with the ability to time-travel.
Embed Stardust in your application through its C API or Go, Clojure, Python, Rust and Odin bindings.
The cosmos is within us. We are made of star-stuff.
We are a way for the universe to know itself.Carl Sagan, Cosmos, 1980
Live demo
Ask about a live demo to see how Stardust works and discuss your use case.
The next live demo has no date yet.
Ask about a demoWhy Stardust
Applications often coordinate data across several sources. This adds coordination logic and inconsistent state. It also increases load and makes applications harder to scale.
Data duplication and inconsistency can prevent access to valuable data. The resulting missed opportunities waste resources and reduce revenue.
The real problem is that data is not treated as a first-class citizen.
Stardust is an embedded temporal data engine. Your application reads and changes data through its C API or language bindings.
The library runs in your application process and stores data in local database files.
As an append-only temporal data store, Stardust keeps history queryable so users can explore data over time.
StardustApplications read and write through one engine, removing synchronization between separate operational stores.
Every accepted transaction remains available. Temporal queries return the database state at a specified time.
Go, Clojure, Python, Rust and Odin bindings use the same C API. Each package includes examples for all five languages.
Build a microlith: keep your application and data engine in one process, with clear boundaries between components. Call Stardust through native language bindings and deploy the library with your application.
Schemas let data change shape without migrations. They project and validate data independently from the stored facts.
Perpetual licenses
Licenses are perpetual and include one year of updates. After that, you can optionally renew your license annually to continue receiving updates.
You can buy any license now: Community, Solo or Team.
Your year of updates and support does not start until the alpha is over. It does not start on the day you buy.
Use Stardust only as your license allows: Community for non-commercial use, and Solo or Team for the one project each license names.
Alpha has no stability or file-format compatibility guarantees. Later builds may not open existing databases. Production use is at your own risk. BitFlip excludes liability for alpha production use to the extent permitted by law. See the pre-release terms.
StardustMultipass
Non-commercial
Hobby work, learning, open research. Named after your account.
StardustMultipass
Commercial · 1 dev
One commercial project. Buy one license per project.
StardustMultipass
Commercial · 10 devs
One commercial project for a team of up to ten.
EnterpriseDesign and support
Work with the Stardust developers on your data model and system design.
Stardust inspired us to create Datastar and related web tooling. Datastar made real-time web applications simpler to build.
Now our focus is Stardust: an embedded data engine that keeps current state and complete history together.
Questions
Stardust is an embedded temporal data engine. It stores current facts and their change history. Applications use its C API or Go, Clojure, Python, Rust and Odin bindings.
Use the alpha to experiment with queries, mutations and historical data in your application. The tutorials and API reference describe the available operations.
The Stardust license is perpetual and does not expire. It includes one year of updates. During the alpha, that year has not started: it starts when the alpha is over. After that year, you can renew updates each year or keep using the version you last updated to. During the alpha, the license token you download from your account expires 30 days after download; download a new one at any time.
Stardust is in alpha. You can buy any license and use it now, within what your license allows. Formats and interfaces can change between alpha builds, so we highly recommend that you do not use Stardust in production; for now it is for experiments only. We have not set a date for general availability.
Sign in and open your account. Every paid license includes the release packages for each platform, with their minisign signatures and SHA256SUMS. Before your first download, and again whenever it changes, you accept the end user license agreement.
Read the tutorials and API reference for the available operations. Email enterprise@stardustdb.com to discuss your use case or ask about a demo.
No. Read the tutorials and API reference before you buy a license.
Yes. You get a full refund within 14 days of purchase. After that, purchases are final. A license you download during those 14 days is temporary and expires when the 14 days end; download it again after that for your full license. A refund revokes the license. To ask for one, reply to your Stripe receipt or email enterprise@stardustdb.com.
Prices are subject to change. A change never affects a license you already bought.
