Frequency is agent orchestration that runs your workflows without you. It analyses your codebase, generates workflow config and scripts, and runs them safely across parallel pipelines with automatic failure handling, cross-pipeline coordination, and file-backed state. Define once. Run continuously. At scale.

Those are general-purpose workflow engines for microservice orchestration with task queues, workers, and databases. Frequency is narrower: it is specifically for agent workflows where the primary operations are LLM calls and git operations, state is repo-local, and the execution model is poll-and-advance. Zero infrastructure overhead, but no distributed execution. If you need Temporal, you need Temporal. If you need a declarative way to run agent pipelines with file-backed state, that is what Frequency is.

Frequency is agent-agnostic. It works with any agent or CLI tool: Claude Code, Codex, Cursor, or your own tooling. About 40% of typical pipeline steps are agent calls where judgement is needed. The other 60% are deterministic scripts. Throwing an agent at a step that should be a bash script is slower, more expensive, and less reliable.

We proved the system by shipping 30 production apps at Cashew Crate. 10 parallel pipelines coordinated autonomously across ideation, build, review, deploy, marketing, bug fixes, and more. The system can push 3-5 apps per hour through the full pipeline, with the throughput ceiling being the token budget rather than the orchestration.

No. Frequency is config-driven and file-backed. Workflows are declared in YAML and stored in your repo. State is repo-local JSON files. Everything runs on the filesystem. You can inspect everything with git log.

Workflows coordinate through state predicates and shared resource locks, all declared in YAML. For example, the marketing pipeline waits until deploy confirms a live endpoint. Bug fixes feed back through build and deploy. You get automatic synchronisation without writing imperative callbacks or routing logic.

App development was our proving ground, but the runtime does not care what the workflow does. Frequency works for any repeatable multi-step workflow: content pipelines, data processing, release management, and more. We are working on additional workflows beyond app development.

We are opening Frequency to design partners. If you want agents building and running your workflows autonomously, safely and at scale, sign up on the homepage and we will be in touch.