Rebuild your legacy software as AI-native. Without the heartbreak.
Kingsheart learns the rules of your code and rebuilds it. Your team controls every decision.
Your software knows things nobody wrote down.
The rules that make your software unique live in code nobody reads and in the heads of people who moved on. The risk: recreating all this knowledge during a rewrite. That is where the heartbreak comes from.
Kingsheart joins your team like your best software engineer and product manager and user experience designer and that go-to expert that seems to know all the answers.
Reads and understands
Your code, your documents and your tickets, all of it, before it changes a line.
Asks
Your people the questions the code cannot answer.
Learns
A picture of how your product really works, and keeps it current as the work goes on.
Rebuilds, but better
It adds the new things you have never been able to add.
Six steps. Your team signs off every one.
Nothing moves to the next step until someone on your team says yes.
Discover
It maps the product: the code, the business rules and the people who know them.
You confirm what it found.Plan
Findings become a plan in phases, each with the tests it must pass.
You approve the plan.Execute
The approved plan runs, step by step.
You review the work.Verify
The old and the new run side by side, checked rule by rule.
You accept the result.Deploy
The rebuilt product goes live when you say so, not before.
You choose the moment.Outcomes
A modern AI-native product with your retained IP that passed rigorous testing.
You see it all.
AI proposes. People approve. Proven systems execute.
It asks before it acts.
Kingsheart, Heart for short, finds what matters and asks the people who know.
It never forgets. And every fact has a signature.
Most AI memory is a silent scratchpad. Kingsheart keeps a versioned record of what it learned, where each fact came from and who approved it. The knowledge stays when people move on, and every next project starts further ahead.
Your code. Your IP. Your call.
- Kept apartEach product Kingsheart works on lives in its own workspace, fully separate from every other one.
- Nothing runs without a yesKingsheart proposes. A person on your team approves before any change is made.
- Every fact has a nameWhat Kingsheart learns is kept with its source and with the person who approved it, so you can always trace why.
What Kingsheart is not
An editor for developersA robot that ships on its ownA replacement for your teamAnother chatbot
It's the team that knows your whole product, and never forgets it.
What Kingsheart is
- 01
Overview
One place that shows where everything stands: what runs, what waits for you and what shipped.
Overview
Roadmap 96 stopped at a gate- 01Signature pending20 of 20Proration rounds the same way everywherePLN-001EREmil Rask
- 02Stopped4 of 15Overdue policy out of XML, into configurationPLN-002PLPetra Lind
- 03Blocked8 of 15Catalog: a missing plan change is an errorPLN-003IMIris Moreau
- 04Approval pending0 of 7Payment retry schedule readable in settingsPLN-004SKSven Kald
- 05Approval pending0 of 7Usage tiers priced in one placePLN-005IMIris Moreau
- 06Running8 of 10One calculation for what an account owesPLN-006NVNora Vance
- 07Signature pending7 of 7Every block decision goes through one checkerPLN-007PLPetra Lind
- 08Signature pending5 of 5A credit in the wrong currency is refusedPLN-008IMIris Moreau
- 09Signature pending5 of 5Settings say which values still come from a filePLN-009SKSven Kald
Releases 5Tenants and their API keys come across REL-0.5- 01A new tenant gets its own API key, and a key already assigned to another tenant is refused.replay
- 02A tenant external key longer than 255 characters is refused.rule check
Nothing else movedEvery tenant on Obelisk keeps the API key it has today.Shipped PR #8Earlier- Custom fields come across with the accountREL-0.4Judged partial, partly rolled backSep 14
- A usage record sent twice is counted onceREL-0.3Judged met, too early to knowSep 12
- Plans and prices read from catalog rows, no deploy neededREL-0.2Disputed: judged metSep 8
- Line item amounts round once, at the endREL-0.1Emil Rask judged it metSep 4
- 01
- 02
Planning
It turns what it found into a plan in steps.
Roadmap9 plans · 1 running · 6 waiting for youNew goalTHIS WEEK3 steps, side by side- 01StoppedOverdue policy out of XML, into configurationDunning a customer can change without a deployPLN-002·PLPetra·4 of 15 tasks·1h 05m agent time
- 02Signature pendingProration rounds the same way everywhereEvery proration matches the rule to the centPLN-001·EREmil·20 of 20 tasks·3h 20m agent time
- 03Approval pendingPayment retry schedule readable in settingsSupport can see and change when a failed payment is retriedPLN-004·SKSven·0 of 7 tasks
NEXT TWO WEEKS1 step- 04BlockedCatalog: a missing plan change is an error, not a fallbackA plan change with no matching rule fails loudlyPLN-003·IMIris·8 of 15 tasks·2h 10m agent time
Heart asks about the orderStep 10 waits on 04, and the blocked task on 04 has been open since yesterday. Do I keep 10 waiting, or split 04 so the part 10 needs can finish on its own?
Answer Heart - 03
Execution
Approved work runs step by step, and you see each task as it happens.
Waiting on youProration rounds the same way everywhere1 finding escalated to youStoppedOverdue policy out of XML, into configurationPhase 1, stoppedWaiting on youCatalog: a missing plan change is an error, not a fallbackOne task blocked on a catalog rule.No movement in 8 daysRunningOne calculation for what an account owesPhase 2 · 8 of 10 tasksReadyEvery block decision goes through one checker7 of 7 tasksReadyA credit in the wrong currency is refused the same way everywhere5 of 5 tasksReadySettings say which values still come from a shipped file5 of 5 tasks
For software too important to break
Engineering leaders
You run a product that is too old to change and too important to stop. Kingsheart moves it to a modern platform one step at a time, and stays on for the work after.
Private equity firms
You bought a company and its code. Kingsheart reads the estate, shows what is really in it, and rebuilds it with your team.