Documentation

How to run ArtificialFlow, and how your own code talks to it. These pages follow the v1.1.0 guides in the product repository.

The source of truth is artificialflow/artificialflow v1.1.0. Release checklists and internal notes stay in that repository. What you need to operate the product is here.

Where to go

Choose a deployment

Docker Compose is the way to try it. One project, named artificialflow, starts Postgres, Kafka, Debezium, and Elasticsearch with the application, then connects them to your OIDC provider. Helm is the production path. It layers an environment file on values-external-iam.yaml and expects Postgres, Elasticsearch, and Kafka with Debezium to already exist, plus an ingress controller and TLS certificates.

Once it is up, pick a client. Node.js covers workflows, inbox calls, and workers. Python and Go cover workers. The HTTP guide, including Swagger UI and a Postman collection, is the contract for every other language.

The deploy builder writes a single Compose file, or a Helm values file and the matching install command.