Skip to the content.

Pulpitum

Append-oriented, partition-local hot/cold table routing for CockroachDB and S3-compatible storage.

Pulpitum keeps recent records in CockroachDB and can serve immutable historical buckets from object storage without making callers choose a tier. Its core concern is the cutover protocol: fence writes, verify an immutable archive, publish a durable route, and only then clean up hot rows.

Status: experimental. The supported safe default is a v4 hot-store deployment. Deployment-owned archival is disabled unless explicitly enabled after environment-specific fault acceptance.

Start here

Core model

((table_id, partition_key, bucket_key), (event_time, sort_key))

The built-in chat mapping is:

Logical column Core field
channel_id partition_key
timestamp event_time
id sort_key
value record payload

Supported deployment profile

Pulpitum currently supports a deliberately narrow operational profile:

See Capabilities before enabling archival or exposing the SQL sidecar.

Engineering references