Your code on Mac
Your release on Windows

Flutter, Tauri, Electron, .NET or your own commands — one agent on your Windows PC. Send sources from Mac or Linux and download the result directly.

Windows 10 / 11 · x64/Free and open source

01Your source codemacOS / Linux / Windows
02Built on your PCRecipe → Windows x64
03Ready to shipArtifacts + manifest

Everything between code
and a finished release

Choose what to build.
Kilnbridge takes care of the rest.

Tools for your project

The agent installs the Flutter SDK, C++ Build Tools and Inno Setup. For other recipes, prepare the tools listed for your chosen stack.

One machine for different projects

Your code stays yours

Send a local Git folder, an ordinary folder or a prepared ZIP over verified HTTPS. The build machine needs no access to your GitHub.

A direct connection over LAN or VPN

Choose where results go

Keep installers, archives, CLIs, libraries and test reports on the agent, download them directly, or publish to S3 or GitHub Releases.

Build without a storage account

Works while you do

A background queue, build history and logs. Signed updates install when the agent is idle, with rollback if startup fails.

Close settings — the build keeps going

Different projects
One agent

Choose a ready-made recipe or supply your own commands. Save the configuration and send your project to build.

Project type

Flutter

A Windows app from Dart: dependencies, tests, a Release build and selected artifacts.

Project sources

Uses local Git to select tracked and unignored files and record the commit. Uncommitted changes require explicit inclusion. No remote access.

Path on the sending computer, used in the CLI command. Files are sent by the CLI; the website does not read them.

To use external build scripts, place them inside the source folder or ZIP and call them with a Custom commands recipe. A local preparation script can produce this folder or ZIP before submission.

A dot means the source root. Use apps/desktop or an archive’s top-level folder to select the project inside it.

The version and build number come from pubspec.yaml. This template disables build_runner; enable it in JSON if your project uses code generation.

Build artifacts

By default, the agent creates a ZIP of the output; Flutter can also create an Inno Setup installer.

Result delivery

No storage account or publication credentials needed. Files and a downloadable ZIP stay on your Windows PC.

Results remain on the agent for its configured retention period (7 days by default). Download them later, including after a failed publication.

On the build machine

The agent installs Flutter SDK, C++ Build Tools, Windows SDK, Git and Inno Setup. Include pubspec.lock and the windows folder in your sources.

flutter-windows.json
{
  "recipe": "flutter",
  "project": "my-app",
  "workDir": ".",
  "flutterVersion": "3.41.6",
  "skipCodegen": true,
  "skipTests": false,
  "publish": "local"
}
Download recipe

Save the JSON next to the CLI and run this command. The source path is relative to that terminal directory. Only agent connection settings are required; publication credentials depend on your choice.

CLI · macOS / Linux
./kilnbridge submit \
  --source-type git \
  --source ./my-app \
  --recipe flutter-windows.json \
  --env agent.env

Use updated CLI and agent versions for recipes, arbitrary artifacts, optional publication and Git / folder / ZIP sources.

Download a saved result
./kilnbridge download --job JOB_UUID --env agent.env

Connect your machines
just once

Then trigger Windows builds
from your usual release script.

  1. 01

    Set up your Windows PC

    Open the agent and click Prepare this machine for Flutter. For other recipes, install the listed tools and restart the agent.

  2. 02

    Connect the computers

    Copy the connection settings into agent.env on your work computer. Use your local network or a VPN.

  3. 03

    Send your project

    Choose a recipe above, save its JSON and pass it to the CLI with your sources. The agent builds the project and saves, returns or publishes the result.

Example build artifacts
release-candidates / job-id /
├─ dist/setup.msi
├─ dist/app.zip
├─ bin/my-cli.exe
├─ lib/core.dll
├─ reports/junit.xml
├─ SHA256SUMS.txt
└─ manifest.json
An explicit artifact list. S3 preserves these paths; sender downloads and GitHub Releases include them in a result ZIP.
Configure a build recipe

Build machine: Windows 10/11 x64. Initial Flutter setup needs internet access and at least 20 GB of free space. Other stacks need their own SDKs. Keep the PC on while builds are running.

Your Windows PC
can do more

Give it your next build.

For the build computer

Windows agent

One EXE. Open it, set up the machine and let builds run in the background.

Download for WindowsWindows 10 / 11 · x64
For your work computer

CLI to send builds

Send sources and follow your build right from your terminal.

All files and release notes

Downloads always point to the latest GitHub release.What's new