§ For bootstrapped saas

Maintenance for the bootstrapped SaaS still earning quietly.

Your SaaS earns. The MRR pays you and maybe one or two collaborators. There is no CTO, there is no SRE, and there is no maintenance budget that isn't your own time. Renovate keeps sending PRs. Sentry keeps surfacing weird edge cases. Kebehut is the way to spend 60€ a month instead of one of your weekends.

§ What worries this audience

Three things you're probably already feeling.

  1. Dependency fatigue — too many Renovate PRs, too little time to decide which ones to merge
  2. A security advisory you only notice three weeks late, because the alert was buried in a folder
  3. Maintenance work eating the weekends you should be spending on product growth or rest

§ Pilot fit

How a pilot is shaped for you.

Recommended tier Basic 60€ / month

Basic is exactly the right tier for a bootstrapped SaaS. A monthly read, a short action list, and a record that survives the next time you have to remember what's installed. Step up to Pro on the month you actually want a stack upgrade shipped; drop back the month after.

First month — what lands in your inbox

  • Dependency and security audit, ranked by what matters for a single-product SaaS
  • Inventory of integrations and which ones are at risk of vendor deprecation
  • A short action list — most months it's empty, which is the point
  • Baseline rebuild-ready spec, useful for hiring or selling

§ FAQ

Questions, briefly answered.

We're EU-based with EU customers. Does Kebehut work with our compliance posture?
Yes. Kebehut is a Skadi Oy service operating from Finland. We do not store your code or customer data — we work against your repository through pull requests on your terms. Your DPO will be unsurprised by the engagement letter.
What if revenue dips and 60€ a month is too much?
Cancel any month. The schema is built for this — Basic is meant to be sustainable through quiet quarters. If revenue dips for a long time, we'd rather you pause Kebehut than skip a payroll.
Can we share one Kebehut engagement across multiple bootstrapped products?
Sometimes — if they share a monorepo, a deploy target, and roughly one set of dependencies. Separate repos are usually separate engagements. Talk to us; this is the kind of sizing question we answer in writing within a working day.

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]