SlateDB – An embedded storage engine built on object storage
SlateDB is an embedded storage engine built as a log-structured merge-tree. Unlike traditional LSM-tree storage engines, SlateDB writes data to object storage (S3, GCS, ABS, MinIO, Tigris, and so on). Leveraging object storage allows SlateDB to provide bottomless storage capacity, high durability, and easy replication. The trade-off is that object storage has a higher latency and higher API cost than local disk. To mitigate high write API costs (PUTs), SlateDB batches writes. Rather than writing every put() call to object storage, MemTables are flushed periodically to object storage as a…
SlateDB – An embedded storage engine built on object storage launched on August 14, 2024 with 26 votes, #889 of 5,471 launches that month and more than 75% of that year's launches. The site was still online in September 2026, 2 years on.
In plain words
SlateDB is an embedded storage engine that uses object storage services like S3 and GCS instead of local disk. Built as a log-structured merge-tree, it offers unlimited storage capacity, high durability, and simple replication across systems. To overcome object storage's higher latency and API costs, SlateDB batches writes into periodic flushes and provides an async put method, letting developers choose between strong durability and lower latency. It's designed for applications needing scalable embedded storage without traditional disk constraints.
written from the facts on this page · September 2026
From the sources
A cloud native embedded storage engine built on object storage. - slatedb/slatedb
In the maker’s words, at launch
SlateDB is an embedded storage engine built as a log-structured merge-tree. Unlike traditional LSM-tree storage engines, SlateDB writes data to object storage (S3, GCS, ABS, MinIO, Tigris, and so on). Leveraging object storage allows SlateDB to provide bottomless storage capacity, high durability, and easy…
Does a similar job
all alternatives →
Parseable Log Storage2022 · parseable.com · ▲79Over the past few months, we've been building Prism; a fast, developer-first observability UI that's deeply integrated with our open-source database, Parseable. Prism is designed for engineers who debug distributed systems, sometimes at odd hours, and need answers right now, without having to deal with five different tools. Backstory: We spoke to dozens of observability practitioners in large enterprises. Across the board, we heard two things: (1)The RoI on observability tools is hard to justify. (2)OSS leads to tool sprawl, metrics in Grafana, logs in ELK, traces… somewhere. We wanted a…
Serverless Postgres2024 · github.com · ▲159This is a MVP for Serverless Postgres. 1/ It uses Fly.io[0], which can automatically pause your database after all connections are released (and start it again when new connections join). 2/ It uses Oriole[1], a Postgres extension with experimental support for S3 / Decoupled Storage[2]. 3/ It uses Tigris[3], Globally Distributed S3-Compatible Object Storage. Oriole will automatically backup the data to Tigris using background workers. I wouldn't recommend using this in production, but I think it's in a good spot to provoke some discussion and ideas. You can get it running…
- IBI built a MySQL storage engine which is InnoDB compatible2016 · upscaledb.com · ▲106
upscaledb - a blazingly fast embedded key-value store with analytical functions
ZeroFS – A log-structured filesystem for S3Jul 2026 · zerofs.net · ▲128ZeroFS serves S3-compatible buckets as POSIX filesystems over NFS and 9P, or as raw block devices over NBD. Data is compressed and encrypted before upload.
A simple distributable object-storage system in Go2016 · github.com · ▲19Simple Object Storage (I wish I could call it Steve's Simple Storage, or S3 ;) - skx/sos
CallFS – S3-style object store in one Go binary (MIT)2025 · github.com · ▲66We started CallFS after yet another late-night “why did the uploads vanish?” incident. Our small team had stitched together rsync, a fragile NFS mount, and an S3 bucket—none of it observable, all of it waiting to bite us. So we wrote a single-process file service in Go that: • Speaks the S3 API (so existing tooling works). • Stores hot data on local disks for speed; cold data can sit in any S3-compatible bucket. • Exposes Prometheus metrics and JSON logs by default, because “what happened?” shouldn’t be guesswork. • Ships as a ~25 MB static binary—no external deps, MIT license. Today it’s…
More dev tools this month
the category →

open-source IDE for thoughtful software design. Contribute to devdotfast/whiteboard development by creating an account on GitHub.
Dev tools · 28d ago · github.com

Contribute to reladraw/reladraw development by creating an account on GitHub.
Dev tools · 26d ago · github.com
OpenBot▲362Grok Bot alternative: free, local, open-source, multiplayer
Dev tools · 23d ago · openbot.run
Talanoa▲346Hi HN, I’m a fullstack developer, and honestly, I’ve lost count of how many side projects I’ve worked on over the years. But one idea kept coming back to me: a different kind of email client. It first came to me in 2014: “What if we could handle emails more like conversations?” Every year, I’d revisit this concept in my “Build Notes.” Ten years later, no one had built exactly what I had in mind — so I finally decided to do it myself. That’s how Talanoa was born. I wanted something focused on people, not timelines. I was tired of marking messages as unread just to remember to reply later, or…
Dev tools · 21d ago · talanoa.email
CoreSpeed▲332One MCP for everything your agents need: apps, memory, tools
Dev tools · 28d ago · corespeed.io
Source: Show HN post ↗ · launch text quoted in part
Launched alongside, August 2024
the whole month →



Jupitrr AI▲1,195Jupitrr AI turns raw talking videos into scroll-stopping content for coaches and consultants. Research, script, record, edit, and publish in one app.
AI · 2024 · jupitrr.com

Hey there HN! We’re Joe and Stopa, and today we’re open sourcing InstantDB, a client-side database that makes it easy to build real-time and collaborative apps like Notion and Figma. Building modern apps these days involves a lot of schleps. For a basic CRUD app you need to spin up servers, wire up endpoints, integrate auth, add permissions, and then marshal data from the backend to the frontend and back again. If you want to deliver a buttery smooth user experience, you’ll need to add optimistic updates and rollbacks. We do these steps over and over for every feature we build, which can…
Dev tools · 2024 · github.com