Move one endpoint, webhook, background job, or AI agent action into Causet. Get a deterministic timeline you can inspect, replay, fork, repair, and audit, without rewriting your app.
Works for existing backend workflows and AI agents. Causet is a deterministic runtime for state, events, intents, projections, replay, and repair.
Browser tutorial + CLI available now · Cloud early access · Self-hosting coming soon
Try the browser tutorial, install the CLI, validate and compile a .causet model, and request Cloud early access for live runtime workflows.
Public Docker/self-hosted runtime and outbound HTTP webhook delivery are coming soon.
View product statusLogs tell you what code said. Causet shows how state changed.
When something fails mid-flow, logs scatter across services. Causet keeps one timeline of what changed.
Instead of searching logs across services, Causet shows the state history of the workflow: the intent, emitted events, failed step, retry, and projection updates.
request_access
access_requested
approval_required
access_approved
notification_sent
send_notification
access_request.status = approved
Replay, fork, and repair actions are available in Cloud early access. Public self-hosted runtime support is coming soon.
You do not need a rewrite. Keep your frontend, database, queues, services, and domain model. Start with one fragile endpoint, webhook, background job, or agent action. Causet becomes the replayable timeline for the state transitions that matter.
Your routes and response shapes stay the same.
Use it as the app-facing read model while Causet records the timeline.
Validate in your endpoint, then hand the fragile work to Causet.
Make approvals, failures, and side effects visible on one timeline.
Use projections or webhook-style updates so your app stays in sync. Outbound HTTP webhook delivery is coming soon.
Move more workflows over when the pattern proves useful. Replay, fork, and repair are available in Cloud early access.
Causet does not replace your database, queue, frontend, services, vector DB, or observability stack. Learn what Causet handles →
Most teams start with retrofit. AI agents and production repair use the same timeline model.
For payment flows, onboarding, access requests, support escalations, webhook handlers, and background jobs.
Promise: Keep the old endpoint. Submit an intent. Move the fragile downstream state into a replayable timeline.
For agents that make decisions, call tools, update memory, or trigger business actions.
Promise: Record the memory, decision, tool call, approval, and emitted business event so agent behavior can be inspected and replayed.
For workflows where logs are not enough. Available in Cloud early access.
Promise: Inspect the timeline, fork from a known point, replay with corrected inputs, and repair downstream projections safely.
Causet is designed to fit existing apps through webhook-style updates and projections. Your app can keep reading from its existing database while Causet records the workflow timeline.
Documented today. Keep the webhook URL, verify the signature, submit an intent, and return quickly. Causet owns the downstream workflow timeline.
Coming soon. Until then, sync state back with projections or your existing app-side update paths.
Causet does not replace your frontend, database, queue, vector store, or services. It records the workflow and state timeline around the operations that need inspect, replay, fork, or repair.
Causet is useful anywhere state changes matter. AI agents make the problem sharper because their decisions, memory, tool calls, approvals, and side effects need to be inspectable.
A replayable state timeline for backend workflows and AI-driven systems.
Payments, onboarding, webhooks, and jobs fail in the gaps between services. A timeline beats scattered logs.
Memory, tool calls, decisions, approvals, and emitted events all need provenance, not just retrieval.
Intent → events → projections → inspect / fork / replay / repair. Whether a human, job, or agent started it.
Clear boundaries reduce adoption risk. Causet is a timeline layer, not a stack replacement.
Old fragile flow → Causet version → what you can inspect. Replay, fork, and repair are available in Cloud early access.
Chargeback webhook updates DB, emails ops, opens a ticket, and syncs finance. Retries live in route code.
Webhook submits RECORD_DISPUTE. Causet records status, notifications, and finance projection updates.
DISPUTE_OPENED → EVIDENCE_REQUESTED → OPS_NOTIFIED → FINANCE_SYNCED
See which step failed. In Cloud early access, fork before a bad sync and replay with corrected dispute metadata.
Form handler inserts a lead, sends email, pings Slack, and syncs CRM inline.
Keep POST /api/request-access. Validate, submit intent, return quickly.
LEAD_CREATED → WELCOME_EMAIL_SENT → SALES_NOTIFIED → CRM_SYNCED
Audit who was notified and when. Retry a failed CRM sync without re-sending email in Cloud early access.
Agent or rule escalates in code; Slack, CRM, and SLA timers update in separate places.
Escalation is an intent. Policy check, human approval, and side effects land on one timeline.
TICKET_ESCALATED → POLICY_CHECKED → HUMAN_APPROVED → SLA_TIMER_SET
Explain why escalation fired. Fork and replay with corrected policy input in Cloud early access.
Provider webhook does five downstream calls. Timeouts and duplicate deliveries hide in the handler.
Verify signature, normalize payload, submit intent with an idempotency key, return 2xx.
WEBHOOK_ACCEPTED → STATE_UPDATED → SIDE_EFFECT_FAILED → RETRY_SCHEDULED
Inbound webhook pattern is documented today. Outbound HTTP webhook delivery is coming soon.
Agent retrieves context, calls tools, and updates systems. Memory and decisions are opaque.
Record memory used, decision output, tool call, approval, and emitted business event on one timeline.
MEMORY_RETRIEVED → DECISION_EVALUATED → TOOL_CALLED → REFUND_ISSUED
See which memory shaped the decision. Replay with corrected context in Cloud early access.
One endpoint owns validation, DB writes, emails, CRM, and retries. Hard to debug in production.
Keep the endpoint and frontend. Submit an intent. Move fragile downstream state into Causet.
INTENT_ACCEPTED → domain events → side effects → projection updates
Adopt one workflow at a time. Expand only where replay and audit matter.
You keep your existing services and database. Causet sits beside your application for the workflows and agent actions that need inspect, fork, replay, and repair.
A user, webhook, job, or agent asks for something to happen.
Logic decides which events and decisions are valid.
State changes become durable facts in the timeline.
AI output, rule results, and approvals are recorded with context.
Readable views are built from the event ledger.
Re-run timelines in Cloud early access to verify corrections.
Branch state before a mistake in Cloud early access.
Validate locally. Run in Cloud early access. Self-hosting coming soon.
Use the browser tutorial to learn Causet without an account. Use the CLI to validate and compile .causet models locally. For live runtimes, Causet Cloud is available in early access. Public Docker and self-hosted runtime support are coming soon.
.causet models locally with the CLI.Conservative labels. No overclaims. Full detail lives in the docs.
| Capability | Status | Notes |
|---|---|---|
| Browser tutorial | Available now | Learn Causet in-browser. No install |
| CLI validate | Available now | causet build validate: fully local |
| CLI compile | Available now | causet build compile: fully local |
| Managed Cloud | Early access | Live runtime for approved accounts |
| SDK packages | Preview | Typed clients; public package publish in progress |
| Timeline inspector | Early access | Available against Cloud early-access runtimes |
| Replay / fork / repair | Early access | Supported in early-access runtimes |
| Inbound webhook pattern | Documented | Verify, submit intent, return quickly |
| Outbound HTTP webhook delivery | Coming soon | Not generally available yet |
| Local runtime / Docker | Coming soon | Public Docker Compose stack not yet released |
| Self-hosting | Coming soon | Public self-hosted runtime support not ready |
Details: What runs today · Install Causet · Roadmap
Causet turns fragile workflows into replayable timelines. You add it beside your existing app to record intents, events, decisions, and state transitions so teams can inspect, replay, fork, repair, and audit how important flows changed.
No. Keep your frontend, database, queues, and services. Start by wrapping one fragile endpoint, webhook, background job, or agent action.
No. Causet is useful anywhere state changes matter. AI agents are the sharpest version of the same problem: decisions, memory, tool calls, and side effects need to be inspectable. Backend workflows and agents share the same timeline model.
No. Public Docker and self-hosted runtime support are coming soon. Today you can use the browser tutorial and CLI validate/compile locally, then request Cloud early access for live runtimes.
Not yet. Outbound HTTP webhook delivery is coming soon. Inbound webhook patterns for existing apps are documented today, and projections can sync state back to your app.
No. You keep your existing database. Causet sits beside your application as the timeline layer for flows where correctness, auditability, and repair matter.
Browser tutorial and CLI validate/compile are available now. Managed Cloud, timeline inspector, and replay/fork/repair are early access. SDK packages are preview. Local runtime/Docker, self-hosting, and outbound HTTP webhook delivery are coming soon. See What runs today?
Keep your app. Pick one endpoint, webhook, background job, or AI agent action. Start with the browser tutorial or the retrofit guide.
Turn hidden workflow logic into a replayable timeline. Browser tutorial + CLI available now. Cloud early access. Self-hosting coming soon.