01
On demand
You call, we step in.
- A bug, an evolution, a migration to plan
- Assessment of the work, then intervention
- Billed on time spent, with a quote for larger scopes
Software in production is alive: bugs appear, needs evolve, dependencies age. Krafter handles corrective and evolutionary maintenance for your Python, Vue.js, Flutter or Symfony applications. Senior developers who read the code in depth, not a helpdesk that opens tickets.
Your software is in production. It has to stay there.
The problem
The most common scenario: a vendor builds your application, deploys it, and moves on. Six months later, a bug shows up. You reach out. They are on another project. They get back to you in ten days, with someone who has never seen your code.
Meanwhile, your teams work around the problem by hand. Data drifts, frustration builds. And every month without dependency updates widens the gap with security patches. Maintenance is not a side service: it is what guarantees your software investment keeps producing value instead of becoming dead weight.
What we handle
A bug in production, an unexpected behavior, a module that stops responding. We diagnose, we fix, we document.
Let’s talkYour processes change, your users raise new needs. Your software evolves with you, without starting over.
Let’s talkFrameworks, languages, databases: upgrades planned, tested on a dedicated environment, deployed cleanly.
Let’s talkCode built elsewhere, no longer maintained or incompatible with your target versions: audit, action plan, restoration.
Let’s talkConviction
“Maintenance is development. Diagnosing a bug means reading the code, understanding the architecture, finding the root cause. Upgrading a major version means adapting the code, migrating the data, testing every flow. It’s not support work. It’s senior developer work.”
François Pluchino
Co-founder & CTO, Krafter
How we engage
We don’t sell packages with an imposed number of hours per month. Two engagement modes depending on your need, contracted simply.
01
You call, we step in.
02
Flexibility without the annual commitment.
Every intervention is tracked: what was done, why, and how long it took.
FAQ
A bug in production, dependencies to update, code to take over: describe your situation, we’ll tell you how we can help.
Discuss my situationIt depends on the volume of work. An isolated bug fix takes 1 to 2 hours. A feature evolution: 1 to 5 days. A major version upgrade: 1 to 4 weeks. Our work is billed between €700 and €1,100 excl. VAT per day. Time credits offer a preferential rate on predefined volumes.
Yes, that is the core of application maintenance. We start with a quick technical audit: stack, architecture, code quality, technical debt, dependencies. Then we take over corrective and evolutionary maintenance, with a realistic action plan.
The ones we run in production every day: Python, Vue.js, Flutter, Symfony, PostgreSQL, Docker. If your application relies on a stack too far from ours, we tell you in the first conversation rather than learning on your invoice.
For a critical bug in production: within 48 hours whenever possible. For a planned evolution or migration: start within 1 to 2 weeks depending on our workload. Time credits let you prioritize your requests. Without a contract or a track record, these lead times cannot be guaranteed.
Yes, as part of a one-off intervention or a time credit: dependency updates, security patches for frameworks and libraries, version upgrades of critical components. It is often the most dangerous debt in software left without follow-up.
30 minutes on a call with a founder. Answer within 24 to 48 hours. Pitch deck optional.


