TypeScript · Python · Rust · TCC Engine · Cloud
Durable execution without history replay.
Trigora is a high-performance, lightweight durable execution platform for long-lived AI agents and programs. Powered by the TCC Engine, it restores committed program state instead of replaying execution history.
⚡ Ultra-fast recovery — as fast as 0.06 ms.
🔄 Zero history replay — restore and resume directly from committed state.
🚀 Lightweight by design — powered by a portable Rust/WASM engine.
💻 Write normal code — TypeScript, Python, and Rust.
Write normal application logic. Trigora can suspend execution across events, timers, external effects, and child programs, then recover from committed continuation state after failure.
import { effect, waitForEvent } from "@trigora/sdk";
export default async function approval() {
const result = await effect("generate", () => 42);
const review = await waitForEvent("approved");
return { result, review };
}Deploy once. Start executions from the CLI, an API call, a webhook, or a cron trigger. Let them run for seconds, hours, or days.
Traditional replay-based durable execution systems reconstruct program state by re-executing previously recorded control flow. As execution histories grow, recovery can require replaying an increasingly long sequence of completed work.
Trigora takes a different approach. At durable boundaries, Transparent Continuation Checkpointing (TCC) commits the program's resumable continuation and the live durable state needed to continue. After an interruption, Trigora restores that committed continuation directly instead of re-executing the completed prefix.
The result is a simple programming model with recovery work tied to the committed continuation, not to the full execution history.
Trigora is built for workloads that:
- run long-lived AI agents;
- call models, tools, APIs, and external systems;
- wait for humans or external events;
- sleep for minutes, hours, or days;
- coordinate durable child executions;
- branch dynamically; and
- need to survive worker or process failure.
Install the SDK, client, and CLI for your language.
npm install @trigora/sdk @trigora/client trigorapip install trigora trigora-client trigora-cliRequires Python 3.10–3.14.
cargo add trigora trigora-client
cargo install trigora-cliThen initialize a project:
trigora initStart the local runtime:
trigora devWhen you're ready to run in production:
trigora deployTrigora Cloud brings TCC-powered durable execution to production, handling deployment, persistence, recovery, and execution management so you can focus on application logic.
It provides:
- durable execution;
- deployment and program versioning;
- events and timers;
- cron and webhook triggers;
- project secrets;
- execution inspection and observability;
- workspace access and API tokens; and
- managed persistence and recovery.
Start building on Trigora Cloud →
Trigora is split into focused repositories.
| Repository | What it contains |
|---|---|
| trigora | CLI, local runtime, public contracts, and ecosystem entry point |
| trigora-typescript | TypeScript authoring SDK and API client |
| trigora-python | Python authoring SDK and API client |
| trigora-rust | Rust authoring SDK and API client |
| tcc-engine | Portable TCC execution engine, language frontends, host protocol, and specifications |
trigora-dev/trigora contains the Trigora CLI, the native local runtime used by trigora dev, shared public contracts, and release coordination. Language-specific authoring APIs and the TCC Engine are maintained in their respective repositories above.
TCC Engine is the portable execution technology underneath Trigora.
It is implemented primarily in Rust, supports native and WebAssembly embedding, and has declared frontends for TypeScript, Python, and Rust.
The engine is available separately for teams that want to embed TCC into their own runtimes or infrastructure.
TCC Engine is source-available under the Business Source License 1.1 and converts to Apache 2.0 under its license terms. The Trigora SDKs, clients, CLI, and public contracts are MIT licensed.
The public research covers:
- continuation-based recovery;
- matched recovery versus history replay;
- live-state scaling;
- crash recovery and fresh-process restore;
- frontend semantics;
- host responsibilities; and
- limitations and failure windows.
Explore the research →
Read the technical report →
- Website: trigora.dev
- Cloud: cloud.trigora.dev
- Docs: trigora.dev/docs
- Research: trigora.dev/research
- TCC Engine: github.com/trigora-dev/tcc-engine
Trigora is built by Trigora, Inc.
- For general inquiries: info@trigora.dev
- For product questions and support: support@trigora.dev
- For commercial terms: sales@trigora.dev
- For security reports: security@trigora.dev
MIT © 2026 Trigora, Inc.