This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
I spent the last year building a database engine from scratch in Rust — AetheriusDB
- One Rust engine for transactions, analytics and vectors - A database with vector search and time travel in SQL
AetheriusDB is a database engine written in Rust. It speaks the PostgreSQL wire protocol and runs transactions and analytics in one engine. It also has vector nearest-neighbour search and time-travel reads in plain SQL. Runs on macOS and Linux, and on Windows via WSL2.
Hi,
For the past year we've been building AetheriusDB, a database engine written from scratch in Rust. Today we're sharing it publicly for the first time.
Why build another database? We kept running three systems side by side: Postgres for transactions, a columnar warehouse for analytics, and a vector store for embeddings. We wanted to try putting all three in one engine, designed around how memory and CPUs actually work.
What it does today:
Speaks the PostgreSQL wire protocol. psql and standard Postgres drivers connect to it.
Transactions and analytics in one engine. New writes land in a mutable delta tier, and a background process seals them into 64 MiB columnar slabs. Queries read both tiers under snapshot isolation.
Vectors in plain SQL. A TENSOR(n) column type and ORDER BY emb <=> '[…]' LIMIT k for nearest-neighbour search.
Time travel. PULSE COMMIT 'before_migration' names a point in time, and SELECT … FROM orders @'before_migration' reads the table as it was.
Clients: Python, Java, .NET, Arrow Flight, a CLI, and a desktop Studio.
Runs on: macOS and Linux; Windows through WSL2.
What it isn't (yet): it's young (0.1.x). Clustering is not something we'd tell you to rely on yet. We'd love testers who will break it.
Biggest lesson so far: the hard part of a database isn't making it fast. It's making it correct after a crash, and correct while two sessions write at once. Most of our time went into crash-recovery and isolation tests.
No comment highlights available yet. Please check back later!
About AetheriusDB on Product Hunt
“High-Performance Data Engine”
AetheriusDB was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #245 on the daily leaderboard. AetheriusDB — one engine for SQL, vector search, graph traversal, and time-travel, with your logic running inside the database.
AetheriusDB was featured in Productivity (665.7k followers), Analytics (174.6k followers) and Artificial Intelligence (483.9k followers) on Product Hunt. Together, these topics include over 337.7k products, making this a competitive space to launch in.
Who hunted AetheriusDB?
AetheriusDB was hunted by Manjeet Chaudahry. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how AetheriusDB stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
I spent the last year building a database engine from scratch in Rust — AetheriusDB
- One Rust engine for transactions, analytics and vectors
- A database with vector search and time travel in SQL
AetheriusDB is a database engine written in Rust. It speaks the PostgreSQL
wire protocol and runs transactions and analytics in one engine. It also has
vector nearest-neighbour search and time-travel reads in plain SQL. Runs on
macOS and Linux, and on Windows via WSL2.
Hi,
For the past year we've been building AetheriusDB, a database engine
written from scratch in Rust. Today we're sharing it publicly for the first time.
Why build another database? We kept running three systems side by side:
Postgres for transactions, a columnar warehouse for analytics, and a vector
store for embeddings. We wanted to try putting all three in one engine,
designed around how memory and CPUs actually work.
What it does today:
Speaks the PostgreSQL wire protocol. psql and standard Postgres
drivers connect to it.
Transactions and analytics in one engine. New writes land in a mutable
delta tier, and a background process seals them into 64 MiB columnar slabs.
Queries read both tiers under snapshot isolation.
Vectors in plain SQL. A TENSOR(n) column type and
ORDER BY emb <=> '[…]' LIMIT k for nearest-neighbour search.
Time travel. PULSE COMMIT 'before_migration' names a point in time,
and SELECT … FROM orders @'before_migration' reads the table as it was.
Clients: Python, Java, .NET, Arrow Flight, a CLI, and a desktop Studio.
Runs on: macOS and Linux; Windows through WSL2.
What it isn't (yet): it's young (0.1.x). Clustering is not something
we'd tell you to rely on yet. We'd love testers who will break it.
Biggest lesson so far: the hard part of a database isn't making it fast.
It's making it correct after a crash, and correct while two sessions write at
once. Most of our time went into crash-recovery and isolation tests.
Site + downloads: https://aetheriusdb.com
Happy to answer anything: architecture, Rust, or why anyone would do this to
themselves.