RELEASE AUTOMATION FOR KICAD · COMING SOON
Send a release package your fabricator can trust.
Upload a complete KiCad project. KiBot runs in an isolated worker and returns one traceable archive with manufacturing files, evidence, and the exact config that made them.
In development. Registration and release runs are not open yet.
ILLUSTRATIVE RELEASE PACKAGE
release / sensor-node-r12
Project uploaded
42 files · rev R12
KiBot executed
config.kibot.yaml · 2m 18s
Evidence verified
manifest + checksums
Release packaged
sensor-node-r12.zip · 18.4 MB
BUILT FOR THE HANDOFF
One canonical archive
Checksummed evidence
Complete project uploads
Isolated runners
FROM PROJECT TO PACKAGE
Release work becomes a repeatable run.
Keep the project together, let KiBot do the mechanical work, and hand off evidence instead of assumptions.
01
Upload the whole project
Bring the KiCad files and every auxiliary file the design depends on.
02
Run your KiBot config
An isolated worker executes the shared KiBot kernel and records the run.
03
Download the release
Get manufacturing outputs, manifest, config, logs, and checksums in one archive.
PROOF IN EVERY PACKAGE
Know exactly what ran before the files leave your workspace.
Every release keeps the revision, KiBot configuration, engine version, timestamps, logs, and artifact checksums together.
ILLUSTRATIVE RUN MANIFEST
run-manifest.json
Everything the fab asks for, in one package.
Each output is produced by KiBot from the exact revision you selected, then recorded in the run manifest.
Gerbers
RS-274X, protel extensions
Drill files
Excellon, plated and NPTH
Bill of materials
CSV and XLSX, grouped
Pick & place
CPL for top and bottom
Assembly drawing
PDF with fabrication notes
Schematic PDF
Multi-sheet, A3
Interactive BOM
Self-contained HTML
Run manifest
Revision, config, engine
RELEASE EVIDENCE
Every release explains itself.
Instead of relying on a testimonial, show the verifiable facts shipped with each package. The evidence stays useful before the first customer quote exists.
Artifact manifest
File names, sizes, and checksums for every generated output.
Configuration snapshot
The exact KiBot YAML used to create the release package.
Toolchain identity
KiCad, KiBot, and configuration versions recorded with the run.
Your next release starts here. Coming soon.
We are building a repeatable release workflow for KiCad. Check back here for launch updates.