Most months belong here. One monthly read on the codebase, no code changes — the quiet baseline you stay on until something demands more.
- Dependency and architecture analysis
- Tech debt + dependency debt mapped
- One prioritized report each month
Keep production software
earning, until you're
ready to rebuild.
Kebehut is a monthly maintenance service for React and Next.js apps already in production. One fixed fee replaces yearly spikes and emergency rescues — and every month leaves you with a written record of what the system does.
Reply Within one working day. From [email protected].
§ Pilot deliverables
Four things land in your inbox
every month, in writing.
The pilot is not a discovery call series. You get the same artifacts a long-term customer gets — scoped to a single app, billed by the month, ended by you the moment it stops being useful.
-
Dependency map
A current, navigable picture of every package, version, and what it actually does for your product — kept up to date each month.
-
Technical debt ledger
A ranked register of risks and quick wins, with effort estimates and concrete next actions. Nothing fuzzy, nothing vague.
-
Monthly action list
A short, prioritized list of changes shipped that month — security patches, version bumps, perf fixes, dead code removed.
-
Rebuild-ready spec
A living specification of what the app actually does today, so when the next version starts you scope from evidence, not memory.
§ Service tiers
Fixed monthly cost.
Change tier any month.
Most teams live on Basic. When the workload picks up — a launch, a security patch wave, a thorny migration — bump to Pro or Enterprise for a month or two, then drop straight back. No annual commitment, no notice period, no upgrade form.
Code Tier What it is Price
Bump up for a busy month — a working engineer day, in writing and in code, then drop back to Basic when the burst is done.
- Up to 1,500 net lines of change
- Clear specs, async updates, crystal-clear prioritization
- One engineer day per month, at engineer-day pricing
Step up further for a heavy quarter. Replaces a 1–3 person maintenance team while the work is hot, ticketing-system included.
- Up to 3,000 net lines of change
- Enterprise ticketing system integration
- Replaces a 1–3 person maintenance team
Numbers nag at you? Compare them against your current annual spend.
§ Pages directory
Find the page
that fits your situation.
Three ways into Kebehut. Read the one that sounds most like you. If two of them fit, read whichever you read first.
- For By company shape. Maintenance pages tuned for founders, internal-tools owners, R&D teams, acquired codebases, and seven more specific shapes. founders · internal tools owners · r&d teams · acquired codebases · post-launch startups · yc-shaped startups · … 10 pages
- Maintenance By stack. What we keep current and how, written one stack at a time. Next.js up first, more landing across the cohort. Next.js 1 page
- vs Compared honestly. When the alternative wins, when Kebehut wins. The same honest framing we use in client emails. hiring a contractor · migrating to a static site (lastupdate.site) 2 pages
One email gets a pilot moving.
No discovery call series.
Tell us the app, the stack, and what's worrying you about it. We reply within one working day with a yes, a no, or a clarifying question — not a calendar link.
[email protected]- Cohort
- 01 — 2026
- Seats
- Limited
- Change tier
- Any month
- Cancel
- Any month