Prisma Streams is a multi-tenant streaming service written in Rust, built on SlateDB, designed to store state in an object store while keeping servers stateless and acknowledging appends only after bytes are durable in object storage. It provides two HTTP APIs, a Prisma product API for typed collections and stream features, and a standards-compliant Durable Streams surface for raw interoperability. It also offers an `@prisma/streams` SDK for developers to create streams, append records, and subscribe to updates.
Project status
- Actively maintained: The source shows a very recent upstream push on 2026-10-02, and it has multiple tagged v0.2.0-rc updates in late August 2026, indicating ongoing development rather than dormancy.
- Update cadence: There were several updates close together (rc.2 on 2026-08-26, rc.3 on 2026-08-30, rc.4 on 2026-08-31), followed by at least some activity on 2026-10-02.
AI summary generated
Recent updates
v0.2.0-rc.4
v0.2.0-rc.4 (release notes not provided) introduces a new per-project memory-pressure admission backstop (round-13), plus changes to admission behavior so authentication happens before any tarpit and capacity refusal answers are computed. The diff also includes a correctness fix in postings caching for runs that straddle an index cut boundary, with new targeted unit tests.
BreakingFeaturesv0.2.0-rc.3
Release v0.2.0-rc.3 has no published release notes. The diff shows substantial changes to performance/capacity benchmarking tooling, and a core runtime behavior change related to the compute-1g LiveFeed/feed retention budget.
Featuresv0.2.0-rc.2
The release is tagged v0.2.0-rc.2, but no release notes were provided, so changes cannot be directly verified from the published documentation. Developers should review the diff between the prior release candidate (v0.2.0-rc.1, or the last known version) and v0.2.0-rc.2 to identify any undocumented API, behavior, or configuration changes before upgrading.
livefeed-canary-rc1
This release (livefeed-canary-rc1, version bumped to streams-slate 0.2.0-rc.2 in code) adds new multi-tenant enforcement infrastructure for Auth and Feed materialization, plus substantial CI and load-testing changes. No publisher release notes were provided, so all behavioral deltas must be inferred from the code diff.
BreakingSecurityFeaturesv0.2.0-rc.1
Release v0.2.0-rc.1 ships with no publisher release notes provided. The code diff shows substantial internal changes to the billing sweep scheduler, including new fairness/continuation logic and a concurrency fix in shard closing behavior, plus multiple build and soak-test automation improvements.
v0.2.0-preview.9
v0.2.0-preview.9 ships with no publisher release notes. The code diff shows several substantial behavioral changes, mainly around binary download diagnostics and stronger runtime identity verification (hashing), plus significant additions to the awsbench benchmark and debug/telemetry instrumentation.
BreakingFeaturesv0.2.0-preview.8
v0.2.0-preview.8 makes major Round-22 billing pipeline changes, including new usage correction fields, materialized correction totals, and stronger read spool reliability and readiness gating. It also adds new HTTP surfaces for billing readiness and project usage, and changes the behavior of /health in BILLING_MODE=required.
Featuresv0.2.0-preview.7
v0.2.0-preview.7 (round-21) introduces invoice-boundary behavior changes across billing, rollup, and fleet telemetry delivery. Key changes include switching billing computations to a trusted server clock, adding a durable read spool for sealed batches, moving the rollup storage namespace to a new account-scoped v2 layout, and updating the usage API response with new aggregation fields and month attribution fallbacks.
Featuresv0.2.0-preview.6
v0.2.0-preview.6 introduces a new observability billing telemetry architecture, including a durable operational event journal (_ops_events) and a usage ledger rollup (_usage -> rollup in SlateDB). The implementation removes the prior interval metrics system and the older billing emitter approach, replacing it with ledger-based telemetry, new startup configuration, and new routing for customer usage lookups.
Featuresv0.2.0-preview.5
This release is v0.2.0-preview.5, but the publisher provided no release notes or change log details. As a result, there is not enough information to reliably identify new features, breaking changes, bug fixes, security updates, or migration steps.