Trax .NET

Trax makes sure a process happens in the right order, by the right people, with nothing skipped, whether a person, a script or an AI agent is doing the work.

Outside Trax, a browser, a script and an AI agent each send a move, never the new state; the client code is yours or generated by Trax. Everything inside the dashed line is Trax. The move arrives through Trax's API, which knows who is calling. Trax then checks it against the stored state: is the move allowed from here, which Trax decides alone; may this caller make it, by rules you write; and do the data and evidence hold up, by guards you write. All three pass and Trax saves the new state and runs the work you wrote. Any one fails and the client gets a code such as GUARD_FAILED or FORBIDDEN with your reason, and nothing changes.

You define the process once, in C#. Any client can drive it, and the server checks every move and refuses a bad one with a typed error that says why. Every run is recorded in your own database. Trax is MIT licensed and targets .NET 10.

New here? Read Trax in five minutes: what Trax is for, in pictures, with no code.

Pick your way in

Deciding whether Trax fits

  • Trax in five minutes: the problem, the idea, and how the pieces fit.
  • What Trax does: every capability on one page, and where each is taught.
  • Trax compared: with Temporal, Durable Functions, Elsa, MassTransit, XState, Hangfire and Quartz.NET, and when each is the better fit.
  • Versioning and stability: what a release may change, and what Trax runs on.
  • Samples: complete applications you can run.

Building with it in .NET

  1. Quick start: one app from an empty folder, in-process to GraphQL.
  2. Trains and junctions: what a train is and how it runs.
  3. Test a train: with in-memory effects, no database.
  4. The Trax book: a whole shop, one feature per chapter.

Putting AI agents to work on it

Running it in production

The Glossary gives every Trax name its plain meaning.

Where to go

How these docs are organised explains the four kinds of page below.

Learn

  • The Trax book: build one shop from an empty folder to a deployed hub, workers and a React storefront, one feature per chapter.
  • Getting Started: build a server with one train, record its runs in Postgres, schedule it, open the operations console and call it over GraphQL.

Do

Understand

Look up

  • SDK Reference: every public type and method.
  • Packages: every package, what it is for, and which to install.
  • Glossary: the names Trax uses.
  • CLI: the trax command, which scaffolds a project from a GraphQL schema or OpenAPI spec.
  • Troubleshooting: startup and runtime errors, verbatim, with the fix.
  • Schema migrations: what each release changes in the database.

Upgrade and explore

  • Upgrading: the migration guides, newest first.
  • Samples: complete applications, each proving one feature end to end.