SWIRLS_
Memory

Memory

Where your system keeps state. Streams for structured workflow output, disks for files, and the Postgres you already have.

What it is. The three places a Swirls system keeps state, each shaped for a different kind of data.

Use it when a workflow produces data another run needs, an agent needs a working file system, or your existing database holds the records a workflow should read and write.

  • Streams: Swirls-managed persistent storage for workflow output. Structured, typed records you can filter and reuse in other workflows or later runs of the same one.
  • Disks: a file system. Arbitrary blob storage for unstructured data, shared between workflows and agents. Agents are very good at navigating file systems.
  • Postgres: your external PostgreSQL database, declared with its table schemas so workflows can run parameterized SQL against it.

A useful rule of thumb: workflow output goes to a stream, working files go to a disk, and business records stay in Postgres.