End-to-end
Web, mobile, data and infra
100% yours
Code and infrastructure
Reversible
Documented handover at any time
8
Products in production that we maintain
Packages
Four day volumes, one contract
The higher the monthly volume, the lower the day rate. The scope of every day is agreed with you before it is used: you know what the package delivers before you pay for it.
Essential
A live product that is stable
3 days per month
€1,500excl. VAT
per month
€500 per day
The package that keeps an already stable product in good shape. Fixes, updates and small adjustments, without pulling a roadmap into the month.
This package covers
- Fixes on the bugs reported in production
- Dependency updates and security patches
- Small interface and content adjustments
- Error and alert monitoring
- A written report at the end of every month
Active
A live product that keeps evolving
5 days per month
€2,400excl. VAT
per month
€480 per day
€100 saved every month
Everything Essential covers, plus one feature increment every month. The product does not simply hold, it moves forward.
This package covers
- Everything in the Essential package
- One feature increment shipped every month
- Monitoring follow-up and alert handling
- A review of performance and slow queries
- A prioritisation call before the month starts
Most chosen
Intensive
A product in active growth
10 days per month
€4,500excl. VAT
per month
€450 per day
€500 saved every month
A real slice of roadmap shipped every month, with dedicated time on performance and priority handling for your requests.
This package covers
- Everything in the Active package
- A roadmap batch shipped to production every month
- Front-end and database performance work
- Priority handling for urgent requests
- A staging environment kept up to date
Dedicated
A team that needs an engineer on hand
20 days per month
€8,400excl. VAT
per month
€420 per day
€1,600 saved every month
The equivalent of an engineer dedicated to your product. Continuous development, architecture work and a voice in your product decisions.
This package covers
- Everything in the Intensive package
- Continuous development on your product roadmap
- Architecture work and rework of the critical parts
- Input on product trade-offs and specs
- Automated tests and continuous integration in place
Technical scope
The same team, the same stack, on a monthly contract
Support covers the layers we build your products on. Nothing is outsourced and nobody discovers the stack along the way.
Full-stack React web
We work directly inside your application: interface fixes, new pages, framework upgrades and refactoring when the code starts to weigh on delivery.
- Next.js
- React
- TypeScript
- Tailwind CSS
Database and backend
Schema migrations, slow queries, missing indexes and data access rules. We only touch the database with a verified backup taken before any structural change.
- Supabase
- PostgreSQL
- Prisma
- Neon
Payments and subscriptions
Webhooks that fail, plans to add, VAT to fix, invoices to generate. This is often the piece that needs the most attention once the product is live.
- Stripe
- Paddle
- Lemon Squeezy
Mobile applications
Fixes, OS and SDK upgrades, over-the-air updates. We handle the submissions and follow the review process on both stores.
- Expo
- React Native
- App Store
- Play Store
Automations and AI
Your workflows run every day and break when an API changes. We watch the runs, repair the scenarios and add the steps your team needs.
- n8n
- Make
- Trigger.dev
- OpenAI
Infrastructure and observability
Deployments, environment variables, certificates, quotas and hosting costs. Errors land in a tracking tool and we handle them before your users report them.
- Vercel
- Railway
- Sentry
- Cloudflare
The Devodev stack
Every layer of your product, covered.
Industry-leading services for every layer: from auth, payments and databases to mobile, automations and observability.
Analytics
PostHog
Mixpanel
Amplitude
Plausible
Authentication
BetterAuth
Clerk
Auth0
WorkOS
Okta
Automation
- Custom AI-first solution
n8n
Make
Zapier
Pipedream
Activepieces
Temporal
CMS
- Custom AI-first solution
Sanity
Contentful
Strapi
Payload
Collaboration
- Custom AI-first solution
Liveblocks
Figma
Slack
Notion
Cron Jobs
Vercel
Trigger.dev
Inngest
Upstash
Database
Supabase
PlanetScale
Neon
MongoDB
Prisma
Deployment
- Vercel
Netlify
AWS
Cloudflare
Railway
Render
Fly.io
Docker
Design System
Tailwind CSS
Radix
MUI
Chakra UI
Transactional Emails
Resend
SendGrid
Postmark
Mailgun
Loops
Feature Flags
- Custom AI-first solution
LaunchDarkly
Statsig
Flagsmith
Split
Internationalization
- Custom AI-first solution
Crowdin
Lokalise
Localazy
Phrase
Mobile Apps
Expo
React Native
Flutter
Swift
Kotlin
Capacitor
RevenueCat
Observability
Sentry
Datadog
Grafana
New Relic
BetterStack
Notifications
- Custom AI-first solution
Knock
Novu
Courier
OneSignal
Payments
Stripe
PayPal
Paddle
Lemon Squeezy
Adyen
Security
- Cloudflare
Arcjet
Snyk- Okta
SEO
- Custom AI-first solution
Ahrefs
Semrush
Moz
Google
Storage
- AWS S3
- Cloudflare R2
- Supabase
Cloudinary
UploadThing
Backblaze
Webhooks
- Custom AI-first solution
Svix- Zapier
- Make
Hookdeck
Stack adapted to every product
What does an application maintenance contract cover?
Application maintenance means handing the upkeep and the evolution of software that is already in production to an outside team. It covers corrective maintenance, meaning the bugs, preventive maintenance, with version upgrades and security patches, and evolutive maintenance, which adds the features your users ask for. At Devodev, the three sit inside the same retainer: you never have to arbitrate between fixing and moving forward. The volume of days you reserve simply sets how much is left for new work once the fixes are handled.
What a month of support looks like
Before the month starts, we review the backlog with you and settle what will ship. During the month, work moves in short batches: every item goes to staging, gets a review, then goes to production. You follow progress on the same board we use, without having to ask where things stand. At the end of the month, you receive a written report with what shipped, the days used, the days rolling over and the priorities we propose for the following month.
Why the team that built the product is the right one to maintain it
An application is faster to maintain when you know the reasons behind its architecture. When we built the product, there is no discovery phase to bill and a fix reaches production the day it is asked for. We also take over applications we did not write: in that case, we start with an audit of the code, the dependencies, the security, the performance and the technical debt. That audit produces a costed, prioritised plan, which we agree with you before the first month of support begins.
Terms
What you sign, in black and white
Four simple rules, the same ones on every package. They are in the contract, not only on this page.
A commitment in three-month periods
The contract runs in three-month periods and renews by period, not month by month. That horizon is what makes it possible to plan work beyond the immediate fix.
Days roll over to the following month
Days left unused in the month roll over to the following month and stay usable until the end of that rollover month. The rollover absorbs a quiet month, it is not a reserve that keeps building up.
Backlog prioritised before the month
We prioritise the backlog together before the month starts. A day is always spent on something you have approved, never on an initiative decided without you.
Your code and your infra stay yours
You remain the owner of the code, the repositories and the access during and after the contract. At the end of a period, you leave with all of it and with the documentation needed to take over or hand it to someone else.
The contract
What holds true on every support contract
One point of contact
You talk to the engineer who works on your code, with no project manager in between.
Days you can trace
Every day used is tied to a named task, visible on the board you share with us.
Nothing outsourced
The work is done by the Devodev team, on the stack it already uses every day.
An exit without friction
At the end of a period, you get back the code, the access and the handover documentation, with no negotiation.
They put their trust in us
Major Prépa
Voyey
Sonvinfra
Covergy
FavikonMajor PrépaVoyeySonvinfraCovergyFavikonFAQ
Frequently asked questions
What founders ask before signing a support contract.
What happens to the days I have not used?
They roll over to the following month and stay usable until the end of that rollover month. After that they do not accumulate any further: the rollover is there to absorb a quiet month, not to build a stock nobody could ever deliver.
How does the three-month commitment work?
The contract runs in three-month periods and renews by period unless you end it. To stop it, you tell us before the end of the current period: the contract ends at its term, with no penalty and no exit fee.
Do you take over an application you did not build?
Yes, and it is a large part of what we do. We start with an audit of the code, the dependencies, the security and the infrastructure, then we hand you a prioritised plan. Support starts once that plan is agreed, which avoids spending the first days discovering the project.
What counts as support and what counts as a project?
Anything that fits inside the existing application counts as support: fixes, new features, optimisations, integrations. A full rebuild, a new product or a piece of work far beyond the monthly volume falls outside the contract and gets its own quote. The line is drawn during prioritisation, never discovered on the invoice.
How do you handle a production emergency?
A blocking incident jumps ahead of the backlog for the month and is handled first, on the days in your package. You reach us on the channel agreed when the contract starts, and we tell you what is under way and what moves back to absorb the emergency.
Can I move up to a larger package during a period?
Yes. Moving up to a larger package takes effect the following month and opens a new three-month period at the new volume. Moving down to a smaller package, on the other hand, only takes effect at the end of the current period.