The acquisition just closed. How fast can month 1 start?

Usually within a week. We don't need access to anything beyond the repository and your deployment logs. We're often asked to start before all the original engineers have offboarded — earlier is better, because we can ask them questions while they're still around.

There's no documentation. Will Kebehut work?

Yes. No documentation is the most common shape we see in this situation. The output of the first month is the documentation — the inventory, the dependency map, the action ledger. After that, we keep it current.

Can you help us decide whether to rebuild or maintain?

Yes — the rebuild-ready specification is built for exactly that conversation. A few months of Basic gives you a written record of what the codebase does, what it costs to keep, and where the brittleness lives. That document is what makes the rebuild-vs-maintain call cheap to make. There's no minimum term — drop us the month you have the answer.

§ For acquired codebases

Maintenance for the codebase you just inherited from an acquisition.

The acquisition closed. The earn-out timer is running. The original engineers either left at signing or will leave at vesting. You own a codebase you did not write, in a state nobody can fully describe, and it is in production right now. Kebehut is what you put in front of that codebase while you decide whether to invest, rebuild, or wind down.

Email us about a pilot → Run the cost calculator

§ What worries this audience

Three things you're probably already feeling.

Original engineers leaving after vesting, taking the last complete mental model of the codebase with them
A ticking security or compliance time bomb you don't know exists yet because nobody mapped it
Spending a quarter just figuring out what you own, while the production app keeps drifting underneath you

§ Pilot fit

How a pilot is shaped for you.

Recommended tier Basic 60€ / month

The first job is mapping. Basic for one or two months produces a clear inventory of what you own. From there: Pro to start patching once the map exists, or a tier-up only when an upgrade is actually scheduled. We don't push you to action before you have ground to stand on.

First month — what lands in your inbox

Complete dependency and architecture audit, written so a non-author can read it
Identification of risks that look small but cluster around acquisition handovers
A ranked action list separating must-do, should-do, and can-wait
A rebuild-ready spec — most useful when 'should we rebuild' is a real question

§ FAQ

Questions, briefly answered.

The acquisition just closed. How fast can month 1 start?: Usually within a week. We don't need access to anything beyond the repository and your deployment logs. We're often asked to start before all the original engineers have offboarded — earlier is better, because we can ask them questions while they're still around.
There's no documentation. Will Kebehut work?: Yes. No documentation is the most common shape we see in this situation. The output of the first month is the documentation — the inventory, the dependency map, the action ledger. After that, we keep it current.
Can you help us decide whether to rebuild or maintain?: Yes — the rebuild-ready specification is built for exactly that conversation. A few months of Basic gives you a written record of what the codebase does, what it costs to keep, and where the brittleness lives. That document is what makes the rebuild-vs-maintain call cheap to make. There's no minimum term — drop us the month you have the answer.

Email us about a pilot.

One paragraph about the app, the stack, and what's worrying you. Reply within one working day, from [email protected].

[email protected] →

← All audiences