Runtime

Local-first, developer-controlled

Falck runs on your machine, uses OpenCode to orchestrate tools and models, and can run apps inside Lima containers when you want parity with production. No surprise clouds, no mystery costs.

Download Falck See the config

OpenCode

Tool orchestration without lock-in

Falck uses OpenCode to orchestrate models, tools, and workflows locally. You pick the model provider, and Falck keeps the experience consistent for every teammate.

Bring your own model and API keys

Local orchestration, no surprise latency

Open source tooling, no black boxes

Built on

OpenCode

Falck is built on OpenCode for reliable local orchestration. They are not affiliated, just excellent humans.

Container mode Lima + containerd

VM name

falck-dev (default)

Launch strategy

Dockerfile + dev command

Access

http://localhost:3000

Lima containers

Production parity when you want it

If your repo uses containerized dev servers, Falck can spin them up inside a Lima VM with containerd/nerdctl. The `.falck/config.yaml` declares it, Falck runs it.

Optional `launch.container` block

Lima VM + containerd / nerdctl

Same access URLs, same workflow

Want the spec?

The runtime is in your control

The Falck config describes setup steps with checks, secrets, and launch. It is versioned with your repo so everyone gets the same runtime story.

See the config Workflow safety