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.
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
Choose what to build.
Kilnbridge takes care of the rest.
The agent installs the Flutter SDK, C++ Build Tools and Inno Setup. For other recipes, prepare the tools listed for your chosen stack.
Send a local Git folder, an ordinary folder or a prepared ZIP over verified HTTPS. The build machine needs no access to your GitHub.
Keep installers, archives, CLIs, libraries and test reports on the agent, download them directly, or publish to S3 or GitHub Releases.
A background queue, build history and logs. Signed updates install when the agent is idle, with rollback if startup fails.
Choose a ready-made recipe or supply your own commands. Save the configuration and send your project to build.
A Windows app from Dart: dependencies, tests, a Release build and selected artifacts.
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.
The agent installs Flutter SDK, C++ Build Tools, Windows SDK, Git and Inno Setup. Include pubspec.lock and the windows folder in your sources.
{
"recipe": "flutter",
"project": "my-app",
"workDir": ".",
"flutterVersion": "3.41.6",
"skipCodegen": true,
"skipTests": false,
"publish": "local"
}
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.
./kilnbridge submit \
--source-type git \
--source ./my-app \
--recipe flutter-windows.json \
--env agent.envUse updated CLI and agent versions for recipes, arbitrary artifacts, optional publication and Git / folder / ZIP sources.
./kilnbridge download --job JOB_UUID --env agent.envThen trigger Windows builds
from your usual release script.
Open the agent and click Prepare this machine for Flutter. For other recipes, install the listed tools and restart the agent.
Copy the connection settings into agent.env on your work computer. Use your local network or a VPN.
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.
release-candidates / job-id /
├─ dist/setup.msi
├─ dist/app.zip
├─ bin/my-cli.exe
├─ lib/core.dll
├─ reports/junit.xml
├─ SHA256SUMS.txt
└─ manifest.jsonAn explicit artifact list. S3 preserves these paths; sender downloads and GitHub Releases include them in a result ZIP.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.
Give it your next build.
One EXE. Open it, set up the machine and let builds run in the background.
Windows 10 / 11 · x64Send sources and follow your build right from your terminal.
All files and release notesDownloads always point to the latest GitHub release.What's new