Skip to main content

Monthly maintenance

An engineer who knows your system, every month

The system is running, but nobody updates the libraries, nobody checks that the backups still restore, and when something small breaks you don't know who to call. With a maintenance plan I take care of that regularly within the agreed hours and send you a status report every month.

Talk about maintenance
  • You work directly with the engineer, no middleman.
  • Scope, price and timeline agreed in writing before any work.
  • NDA available if you need one.

A good fit when

  • The system runs your day-to-day business but nobody is responsible for it.
  • The original developers have handed over, or no longer offer support.
  • You want someone who already knows the system to call when something goes wrong.
  • Security and library updates are needed regularly, but nobody in-house can do them.

What's included

  • Library and framework updates, bug fixes and small improvements within the plan's hours.
  • Monitoring, and handling incidents during the agreed support hours.
  • Backup checks and regular test restores.
  • Help with releases, a monthly status report, and keeping the documentation current.

Good to know

  • Support hours, response times, incident levels and what isn't covered are all written into the contract. This isn't 24/7 support.

How it works

4 steps, each one known in advance

  1. 01

    Get to know the system

    If I haven't worked on your system before, we start with a Health Check to see where it stands.

  2. 02

    Agree the plan

    Hours per month, support window, response times and severity levels, all written into the contract.

  3. 03

    Regular work

    Updates, fixes, backup checks and incident handling within the agreed window.

  4. 04

    Monthly report

    What was done, how many hours were used, and which risks to watch next month.

About me

You work with me directly

For more than 15 years I've built and run systems at major technology platforms in Vietnam. At GocFix, the person you talk to is the one reading the code, configuring the servers and answering for the result.

What I work with day to day

Servers and deployment
DockerKubernetesNginx / CloudflareCI/CDRollback
Databases
MySQLPostgreSQLZero-downtime migrationQuery tuning
Backend and queues
KafkaRabbitMQCelery / RedisFastAPI
Data security
Envelope encryptionVaultKey managementAudit log
Document automation and AI
OCRRAG

FAQ

Common questions

See all services
Is it 24/7?

No. The support window and response times are written into the contract. I work alone, so I don't promise what I can't keep.

What if we need more hours than the plan includes?

Extra hours are billed at the agreed rate. How you're warned before the hours run out is written into the contract too, so the invoice is never a surprise.

Do you maintain systems built by someone else?

Yes. We usually start with a Health Check so I understand the system before taking responsibility for it.

Do we sign a contract?

Yes. Before any work starts, the scope, cost, timeline and how the work is signed off are put in writing. I'm happy to sign an NDA as well if you need one.

How do you keep code and data safe?

I only ask for the access the job needs and give it back at handover. How data is handled and an NDA are agreed before we start. Please don't send passwords or API keys through the form on this page.

Contact

Talk about a maintenance plan

Tell me briefly about the system, who looks after it now, and what support you need.

  • I only take on a few projects a month so each one gets proper attention.
Your contact details and the problem

Leave an email or a phone number. Either one is fine.

Please don't send passwords, API keys or sensitive data through this form.

More details (optional)

I only use this to reply to you.