Most people meet ScrivaDB as a server on :5433. But if your program is written in Go and is the only writer, you can skip the server entirely — go get the engine, call Open, and get a real database in-process. No daemon, no network, no gRPC in your binary.
The selling point is that you can cat your database. Encryption at rest sounds like the opposite of that. Here’s how ScrivaDB reconciles the two — by encrypting values at a single boundary and keeping compaction, indexing, checksums, and backups completely key-oblivious.
The interesting moment in any storage engine is kill -9 in the middle of a write. ScrivaDB’s crash story is three unglamorous rules — append-only, truncate the torn tail on open, and CRC32C every record — that together mean a crash can cost you the last write but never a record that was already there.
Half the time you reach for a database, what you actually needed was a file you could trust. ScrivaDB is the space between json.Marshal to disk and standing up Postgres — durable, queryable, and still just text you can cat.
