sys_frequency_ai / orchestration_runtime / v2.1.0-stable
FREQUENCY
AI
AI
active_pipeline.log
›
Agent orchestration that runs your workflows without you. Define once. Run continuously. At scale.
Your repo already has patterns worth automating. Frequency analyses your codebase, generates the workflow config and scripts, and runs them safely across parallel pipelines.
OPTIONAL / TELL US ABOUT YOURSELF
✓ REQUEST LOGGED / WE WILL BE IN TOUCH
apps_shipped.production
30
at cashewcrate.com
parallel_pipelines.active
10
coordinating autonomously
throughput.apps_per_hour
5
full pipeline, end to end
From repo to
running workflow.
running workflow.
ARCHITECTURE / AUTO-GENERATED CONFIG / FILE-BACKED STATE
- WORKFLOW_ENGINEFrequency analyses your codebase and generates workflow config as YAML state machines. State stored as repo-local JSON. Inspect everything with git log.
- PIPELINE_COORDINATORCross-pipeline coordination through state predicates and shared resource locks. Marketing waits for deploy. Bug fixes feed back through build. All configured automatically.
- EXECUTION_RUNTIMEWorks with Claude Code, Codex, Cursor, or any CLI tool. Agent calls run in git worktrees with integration gates. Automatic retries for transient failures. Permanent failures dead-lettered for manual review.
subsystem_manifest / FREQUENCY / v2.1
Capability index.
SYS_01 / SCOPE
Any Repeatable Workflow
App development was our proving ground, but the runtime is workflow-agnostic. Content pipelines, data processing, release management, or your own multi-step operations. Run as many parallel workflows as you need.
SYS_02 / EFFICIENCY
Agents Where It Counts
~40% of 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 command is slower, more expensive, and less reliable.
SYS_03 / CONCURRENCY
Four Levels of Control
Global max workers, per-step limits, WIP limits, and named resource locks. We lost a week of runs before adding WIP limits when 15 agents conflicted on shared files simultaneously.
SYS_04 / PORTABILITY
Runs Where Your Agents Work
Frequency runs alongside your agents in the same repo. State is repo-local JSON, config is committed YAML. Wherever your agents can run, Frequency can orchestrate them.
sys.blog / LATEST DISPATCHES
From the blog.
DESIGN_PARTNER.REQUEST / QUEUE_OPEN
Get early
access.
access.
We're opening Frequency to design partners. If you want agents building and running your workflows autonomously, safely and at scale, we'd love to give you early access.
OPTIONAL / TELL US ABOUT YOURSELF
✓ REQUEST LOGGED / WE WILL BE IN TOUCH