Software Maintenance and Support: Care Plans You Can Take or Leave

After launch, your software needs hosting, patches and the odd small change. You decide who handles that: your own team, a third party, or a Globaprom care plan at a fixed monthly fee. Saying no to a plan costs you nothing, because the code is yours either way.

Isometric illustration of a live app window with a heartbeat line, a shield, a wrench, a monthly calendar and a cloud backup.

Never Required, by Design

A care plan is never a condition of working with us. You own the code, the repository, the documentation and the infrastructure accounts, so your software keeps running whether or not we're involved after launch.

That's deliberate. A vendor whose maintenance revenue depends on being irreplaceable has the wrong incentive during the build. Ours runs the other way: the cleaner the handover, the easier we are to leave. And the more likely you are to come back for the next project.

Isometric illustration of a toggle switch, an open padlock, a repository cube with a key and a handover package.

What a Care Plan Covers

One fixed monthly fee takes the day-to-day running of your software off your plate:

Hosting and operations. We run the infrastructure, or manage it inside your own accounts.
Monitoring and alerts. We notice problems before your users do.
Dependency updates and security patches. The audits from the build continue on a schedule, so the codebase doesn't quietly age.
Backups. Taken, stored and tested, so restore day is boring.
Small changes. Text updates, minor tweaks, a new field on a form: handled within the plan, not quoted separately.

Care plans run €100–300 per month, depending on the size of the system and the level of cover. You get the exact coverage and fee for your software in writing before you choose, as step six of how we work describes. Plans are monthly and cancelable. Nothing locks you in.

Get your care plan fee in writing

Isometric illustration of a monitoring dashboard with a heartbeat line, an update arrow, a backup cloud, a shield and a monthly calendar.

Monitoring, security patches, tested backups and dependency updates keep running in the background, so problems get caught before your users notice them.

Running It Yourself Is a Real Option

We don't mention self-maintenance for legal comfort. The handover is built for it: documentation written for your next developer, a deliberately mainstream stack, and deployment configuration that lives in your repository, not in our heads. If you have an IT team, they can run the software from day one.

Many clients take a plan for the first months, then decide with real usage data. Others never take one. Both are normal, and neither changes the price of the build, which stays fixed under our fixed-price packages either way.

See how we hand over

Isometric illustration of an app window on a desk with a repository folder, a documentation book, a cloud deployment and a key.

What a Care Plan Is Not

Two boundaries keep the plan honest:

Fixes to our own mistakes are free, plan or no plan. If the software fails the written scope and acceptance criteria you approved, correcting it is part of the build, never a maintenance charge.
New features are new scope. A plan covers small changes. A new module or workflow gets its own written quote, so the monthly fee never turns into a blank check in either direction.

Planning a new module? Ask for a fixed-price quote and you'll have the scope, the price and the date in writing.

Isometric illustration of a fenced area holding a wrench, a monitor and a shield, with a new-module blueprint and price tag outside the fence.

Decide After Launch, Not Before

You don't need to pick a maintenance model to start a project. Book the scoping call, get your fixed quote, and choose how to run the software once it's real.

Request a fixed-price quote See pricing