Questions an engineer actually asks.

Actae is durable execution and synchronization infrastructure for AI agents. It persists ordered events, versioned state, tool-execution records, and immutable fork lineage so long-running agents can recover from crashes, avoid duplicate side effects, and fork at exact boundaries. Actae runs beside your agent as the durable layer underneath; it does not choose prompts, models, tools, or plan tasks.

No. LangGraph, LangChain, the Claude Agent SDK, the OpenAI Agents SDK, CrewAI, Codex, and GitHub Copilot stay in control of the execution loop. Actae is framework-neutral durable infrastructure underneath those frameworks, exposed through Python, Go, and TypeScript SDKs plus native adapters.

They draw a different boundary. Temporal owns the application's control flow through workflow definitions it executes. Actae does not own your execution loop: it records and coordinates it, so your framework or application remains authoritative. Actae is a narrower fit for teams that want framework-neutral durability and stateful execution lineage; Temporal is a strong fit when a general workflow engine should own the whole application lifecycle.

The SDKs are open source (MIT). The Actae server is proprietary, but a free self-hosted community edition is available at no charge. Managed Cloud and the licensed Self-Hosted Team edition are the paid offerings, adding operated runtimes, signed updates, the portal/fleet, and support.

Durable events, state versions, cursors, and operation records survive in PostgreSQL. The agent resumes from its last committed cursor with inherited state, and steps that already completed are not re-invoked. The flagship workflow forks at a chosen step so you can refine the next action without re-running the expensive prefix.

Every tool invocation is recorded in an idempotent tool-execution ledger keyed by a stable operation key and a parameter fingerprint, guarded by leases and fencing tokens (claim, complete, fail, heartbeat, cancel). A retry of an operation that already completed replays the stored result instead of executing again, and a stale worker is fenced out. Actae never executes the tool itself; the caller runs it, and Actae makes the retry explicit and safe.

Actae guarantees atomic event-plus-state transitions, durable idempotency keys, and fenced leases. For side effects outside PostgreSQL, exactly-once is a property of the caller's integration: use the operation key and, where the external system supports it, its own idempotency key. Actae makes the ambiguous window explicit rather than pretending it does not exist.

A fork copies the source channel's state snapshot at or before the fork cursor into a new child channel, records a lineage marker pointing at the parent boundary, and returns an immutable fork receipt describing the requested and resolved cursors. The child inherits the parent's real accumulated state, so only the steps after the boundary run. SDKs default to a strict boundary mode that refuses a silent fall-forward.

Python (pip install actae-client), Go (go get github.com/BViganotti/actae-go), and TypeScript (@actae/sdk, Node 20+ ESM) SDKs cover the full API. Native adapters exist for LangGraph, LangChain, the Claude Agent SDK, the OpenAI Agents SDK, CrewAI, Codex, and GitHub Copilot. Any language with an HTTP client and WebSocket support can integrate directly against the REST and WebSocket API.

With self-hosted Actae, events and state stay in the PostgreSQL environment you operate, and payloads are not uploaded to the SaaS control plane. With Actae Cloud, each customer gets a dedicated runtime and persistent volume. The control plane stores accounts, entitlement, lifecycle, and aggregate usage; it does not receive event payloads merely to meter usage.

Actae ships as a single binary that serves the HTTP API, WebSocket endpoint, dashboard, and (in embedded mode) a managed PostgreSQL instance. Production deployments run the same binary with your own PostgreSQL, or the provided Docker Compose stack with TLS and rate limiting. Actae Cloud provisions a dedicated hosted runtime for you.

Not yet. Actae Cloud currently states its operating posture plainly rather than claiming a service-level agreement. Multi-node recovery, PostgreSQL high availability, an independent security review, formal on-call ownership, and measured margins must be evidenced before a public SLA is offered.

Two limits govern hosted plans: data written (the monthly flow of events, saved state, and tool results accepted) and retained data (the current logical payload Actae stores, including state versions and fork copies). Enforcement is atomic inside the runtime's PostgreSQL transaction; when a cap is reached, further durable writes are rejected before they can change state.

Yes. Actae Self-Hosted Community is free: one self-contained binary with embedded PostgreSQL and no account, card, or control plane. It includes exact-boundary forks, the idempotent tool-execution ledger, crash recovery, and the SDKs — single-node, with community support. Download it at actae.dev/download. Managed Cloud and the licensed Self-Hosted Team edition add operated runtimes, signed updates, the portal/fleet, and support.

Download the free self-hosted build and fork a run on your own machine in about a minute, or bring one workflow that already runs for ten minutes or longer. Actae reviews the architecture, provisions a dedicated Cloud endpoint or a licensed self-hosted evaluation, and helps you prove crash recovery and safe retry against your own agent. Contact hello@actae.dev to start.