Ingestion and history
A Rust API accepts and queries events, with detail, trace, graph, workflow-query, runtime-metric, and idempotency-related paths.
useEventStack turns operational facts into governed workflow inputs, queryable state, and connected traces. This is an early-stage product; adoption, revenue, reliability at scale, and enterprise readiness are not claimed here.
Problem
Deployments, incidents, support requests, payments, product usage, and security changes describe how a company operates. They often live as isolated webhooks, logs, queues, and one-off automations.
Thesis
A shared Event → Workflow → Projection → Trace plane can connect application behavior without hiding cause and effect inside brittle integrations.
This is a product thesis, not evidence of category ownership, customer demand, or achieved business outcomes.
Product evidence
Repository breadth is engineering evidence, not a substitute for production, security, commercial, or customer diligence.
A Rust API accepts and queries events, with detail, trace, graph, workflow-query, runtime-metric, and idempotency-related paths.
The worker matches enabled organization workflows, executes approved custom WebAssembly actions under runtime controls, records failures, and emits derived events.
Workflow output can write projections. Sandbox, replay, consistency, failed-event, and dead-letter surfaces support evaluation and diagnosis.
The monorepo includes an Astro dashboard and docs, SDKs, examples, deployment infrastructure, monitoring assets, and smoke-test automation.
Diligence
Review the event lifecycle, workflow action boundary, projection model, replay behavior, and checks around each path.
Separate local and repository evidence from production operations, security assurance, recovery, and scaling evidence.
Request commercial, customer, fundraising, and traction information directly rather than inferring it from product code.