Ursula: thread-per-core, multi-Raft Rust runtime for HTTP event streams
Ursula is a self-hosted, distributed server designed for managing replayable event timelines. It utilizes the Durable Streams Protocol to provide low-latency, durable event streaming over HTTP. The architecture supports independent Raft groups and is optimized for high performance and scalability.
- ▪Ursula allows document editors and workflows to manage event streams over the public internet.
- ▪It maintains open-source self-hosting, low write latency, and quorum-replicated durability.
- ▪Ursula can sustain 35.2k appends per second while delivering low-latency streaming to numerous subscribers.
Lobsters files mainly under programming. We currently carry 187 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/tonbo-io/ursula |
| Publication time | Thu, 21 May 2026 10:53:05 -0500 |
| Retrieval time | 2026-05-21T16:01:31.036Z |
| Last seen | 2026-05-21T16:01:31.036Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | gW_N1ilzGE3G |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Ursula Docs: ursula.tonbo.io Ursula is a self-hosted, distributed server for the replayable, append-only event timelines behind document edits, agent runs, workflows, and chat. It speaks the Durable Streams Protocol over plain HTTP and SSE. What Ursula keeps Event streams live outside the broker network. Document editors, agents, and durable workflows need timelines that browsers, mobile apps, and serverless functions can read, write, and tail over the public internet. That asks for HTTP-native, distributed, S3-backed infrastructure, not the SDK-locked, single-network shape Kafka-style brokers were built for. The Durable Streams Protocol nails that wire format, but its reference server is a single process: a node loss is data loss.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.