Hanzo Auto

A run that survives the restart

1. 01 / 06Durable execution

   A run is a record, not a goroutine. Step state is written down as it goes, so a crash, a deploy or a rescheduled pod resumes where it stopped rather than starting over or losing the run.

   recordstep 1 / 5

   1. trigger
   2. GitHub
   3. Postgres
   4. Slack
   5. done

   pod rescheduled

2. 02 / 06The catalog is in the binary

   GET /v1/pieces lists the connectors this build has. No plugin registry to reach at boot, so the version you deployed is the version that runs, offline and forever.

   GET /v1/pieces…

   [
   

3. 03 / 06Triggers

   POST to a trigger and a run starts. Or start one by hand against /v1/runs. Either way it is the same run object with the same history.

   POST trigger/v1/runs

   run

   1. 01POST trigger
4. 04 / 06Watch it live

   The editor is React Flow, embedded in the binary, and it follows a run over a server-sent event stream — so the canvas you drew is the canvas you watch execute.

   server-sent eventstrigger

   1. step.startedtrigger
5. 05 / 06Draft, then publish

   Edit a flow freely; nothing changes for callers until you publish. What triggers fire is a published version, so editing in the afternoon does not change what runs overnight.

   draft

   1. trigger
   2. GitHub
   3. Postgres

   published

   1. trigger
   2. GitHub
   3. Postgres
6. 06 / 06Connections, not pasted keys

   A connection is a named credential the flow refers to. It is encrypted at rest through Hanzo KMS, and who may touch it is Hanzo IAM's answer, not a second login here.

   connectionGitHub

   ••••••••••••

   1. Hanzo IAM
   2. Hanzo KMS
   3. GitHub