Everything it reads is monitored.
We monitor everything the agent does, automatically and with people. If something shouldn't reach the AI provider, we filter it out of the context.
01 · WHAT IT DOES
Four jobs you can hand to Kilby.
Start with the work your team never gets to.
Tickets keep losing to the roadmap.
WHAT KILBY DOES
Takes tickets, small to large: bugs, features, drivers and CRA reports. Every change is tested on your board.
WHAT YOU GET
A pull request with test results, reviewed by a human engineer.
- BUGKB-142
Sensor stops answering after a supply dip
Assigned to Kilby - FEATUREKB-151
Low-power mode for the data logger
Assigned to Kilby - DRIVERKB-158
Driver for the STSAFE-A120 secure element
Assigned to Kilby - CRAKB-163
CRA vulnerability report in a third-party library
Assigned to Kilby
Your engineers lose days on reports they can't reproduce.
WHAT KILBY DOES
Reproduces the report on the bench and measures what happens on the board.
WHAT YOU GET
A yes or no, with log, trace and measurements. Real bug? Kilby can fix it next.
CUSTOMER REPORTSUP-2291
"The device restarts when the relay switches."
From your support deskVERDICT
Confirmed: real bug
· supply dips to 4.4 V when the relay closes· reset reason: brown-out· reproduced on every try
Ticket created with log, trace and measurements.Nobody has time to flash every change and run regression tests by hand.
WHAT KILBY DOES
Every night Kilby flashes the day's work and runs the regression tests on hardware.
WHAT YOU GET
A morning report: what broke, and a proposed fix.
MORNING REPORT · 07:00
Deployed yesterday's mainok
Regression suite on hardwaredone
UART drops bytes at high baud rateregression
Proposed fixready
Say go and Kilby makes the change.
Your specs are a pile of PDFs. No product matches them anymore.
WHAT KILBY DOES
Reads your firmware, tickets and documents, and keeps one spec next to the code. Every change updates it.
WHAT YOU GET
One spec in your repo that matches what runs on the product.
TODAYOUT OF DATE
spec_v3_final.pdfspec_v4_FINAL2.pdfspec_v4_FINAL2_review.pdfspec_current.docx · which one is right?
SPEC · IN YOUR REPOSITORY
One living spec
· matches firmware v2.4 on the board· updated with every change· versioned like your code
Last change: KB-142, sensor bus recovery.02 · THE FLOW
Assign a ticket. Get back a tested pull request.
WORKS WITH JIRA · AZURE DEVOPS · OPENPROJECT
Kilby does the work.
Engineers decide what ships.
03 · THE BENCH
What's on the bench.
Kilby connects to your lab through a harness and tests hardware in the loop, like an engineer at the bench. An engineer sets the limit on every output, and a request past it is refused.
WHILE THE TEST RUNSThe bench runs the test.
The bench runs the test.
Kilby sleeps.
A test can run for hours without Kilby. He only wakes up when a check fails or the run is done.
APPROVED
STEP 5 OF 5 · KILBY ACTIVE
Passed. Ready for review.
Kilby hands in his work. A human engineer reviews it, then you get the pull request.
Why not just a coding agent with skills?
A coding agent with skills is great with a developer next to it. Skills tell the agent how to work. Kilby also gives it a bench and limits it can't pass, so you can hand over a ticket and walk away.
A coding agent with skillsKilby
WHERE IT WORKSIn a terminal, with a developer watchingOn the ticket, with nobody at the keyboard
HARDWAREOnly what you script yourselfA real bench, with limits it cannot pass
LONG TESTSThe agent waits, and uses contextThe bench runs alone, and wakes the agent when needed
YOUR CODE AND KEYSWhat it can read, the model can seeSealed agent, with your keys and ignored files out of reach
SIGN-OFFUp to you, afterwardsA human engineer, before it reaches you
A coding agent runs out of context. Kilby keeps going.
A coding agent~1M tokens, context full
CONTEXT FULL
Kilby12M+ tokens →
Your code goes in.Three doors lead out.
The agent works in a sealed container. These three ports are the only way out.
It tests on your real board.
Real power, real measurements, no simulator. An engineer sets the limits, and a request past one is refused.
Nothing leaves without a human.
The platform runs the checks and a human engineer reviews the work. You get a pull request on your own repository. Merging is up to you.
IGNORED FILES
Your ignored files never reach the agent.
Everything on its way to the agent passes a guard. What you keep back stays outside, even when a piece of it shows up in a build.
- GOES INFiles you allow, and build output without your secrets.
- IGNOREDFiles in .kilbyignore stay outside. Your builds still use them.
- REDACTEDA piece of an ignored file is cut out. The agent only sees a marker.
06 · KNOWLEDGE
Kilby learns. Only for you.
What he learns about your product grows in a knowledge graph of its own. Nothing crosses over to other clients.
07 · WHY KILBY
In Dallas, Jack Kilby builds the first chip. In Brussels, the Atomium opens.
Our Kilby is named after him, and built in Belgium.
- SUMMER 1958New at Texas Instruments, he had no holiday yet. The lab was empty, so he kept working on his idea.
- 12 SEP 1958The first integrated circuit works: a bar of germanium of 11 by 1.6 mm.
- ON A SCOPEThe proof was a sine wave on an oscilloscope. That's why our Kilby's face is two traces.
- DID YOU KNOWHe missed the MIT entrance exam by three points: 497, where 500 was the minimum.
- 2000Nobel Prize in Physics, for his part in the invention of the integrated circuit. He held more than 60 patents.
Before you hand over a ticket.
The questions embedded teams ask us first.
Still a question? hi@kilby.be
Q01What kind of boards and chips does Kilby work with?
Firmware for embedded boards, whatever processor is on them. Tell us what you build on when you join the waitlist, and we'll make sure the bench fits your board.
Q02Does Kilby really test on our hardware?
Yes. Kilby works on a bench with your board, a bench power supply and a debug probe. Real power, real measurements, no simulator. How the bench is configured for your board is something we agree on in the pilot.
Q03Is it safe to let an AI drive a power supply?
An engineer sets a limit on every output before Kilby starts. A request past a limit is refused, and the bench switches off.
Q04Does our code leave the company?
The agent works on a copy of your repository in a sealed container. Files in your Kilby ignore file are never shown to it. What it does read goes to an external AI model, and we monitor that, automatically and with people. What Kilby learns about your product stays with you and never crosses over to other clients.
Q05Can Kilby push to our repository or merge?
No. The agent has no keys and cannot push. The platform runs the checks, a human engineer reviews the work, and you get a pull request on your own repository. Merging is up to you.
Q06What happens when a ticket is unclear?
Kilby asks on the ticket, like a colleague would, and waits for the answer before it starts. If it gets stuck, it says so on the ticket instead of guessing.
Q07What do we need for a pilot?
A board, a user for Kilby in your ticket system (Jira, Azure DevOps or OpenProject), access to your repository and a contact person. Join the waitlist and we'll reach out.
09 · WAITLIST
Put your board on Kilby's bench.
Join the list and we'll contact you about a pilot. All it takes: a board, a user in your ticket system, repository access and a contact.
BUILT IN BELGIUM