Can we use Kebehut as backup coverage when our engineer is out?

Yes. Bump to Pro for the weeks of coverage, drop back to Basic afterward. We won't pretend to fully replace the original author — nobody can do that in a week — but we can keep the codebase honest while they're away.

What if our engineer doesn't want a third party in the codebase?

Some don't, and that's fair. The framing that works best is: Kebehut is for the company, not for the engineer. It's continuity insurance for the business. Most engineers come around once they see the first report and realize we're not auditing their work — we're documenting the system.

Does Kebehut do knowledge transfer in both directions?

Yes — the monthly reports are written so that they capture what's in the engineer's head over time. After six months you have a written specification of the system that the engineer themselves can use as a reference.

§ For single-engineer shops

Maintenance for the company whose codebase has one author.

Your bus factor is one. The codebase has one author, the deploy pipeline has one operator, the on-call rotation has one person — and that person is going to take a vacation eventually. Kebehut is not a replacement for them. It is a second set of eyes that reads the codebase every month, writes down what changed, and is already up to speed when the call comes that they're sick.

Email us about a pilot → Run the cost calculator

§ What worries this audience

Three things you're probably already feeling.

The one engineer takes a vacation and a deploy breaks the day they leave the office
Burnout becoming an existential risk for the company, not just a personal one
Nobody else can read the codebase well enough to triage even a small production issue

§ Pilot fit

How a pilot is shaped for you.

Recommended tier Basic 60€ / month

Basic is the backup layer. A monthly written record of what's in production, what's changing, and where the brittleness sits. When the engineer is unavailable — vacation, illness, parental leave — you have something written down and someone you can email about it. Step up to Pro for those coverage months specifically.

First month — what lands in your inbox

Codebase walkthrough written for someone other than the original author
Identification of the parts of the system only one person knows
A dependency and security audit alongside what's already in your engineer's head
A rebuild-ready spec, useful for the day there's a second engineer in the company

§ FAQ

Questions, briefly answered.

Can we use Kebehut as backup coverage when our engineer is out?: Yes. Bump to Pro for the weeks of coverage, drop back to Basic afterward. We won't pretend to fully replace the original author — nobody can do that in a week — but we can keep the codebase honest while they're away.
What if our engineer doesn't want a third party in the codebase?: Some don't, and that's fair. The framing that works best is: Kebehut is for the company, not for the engineer. It's continuity insurance for the business. Most engineers come around once they see the first report and realize we're not auditing their work — we're documenting the system.
Does Kebehut do knowledge transfer in both directions?: Yes — the monthly reports are written so that they capture what's in the engineer's head over time. After six months you have a written specification of the system that the engineer themselves can use as a reference.

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