Service 04

Maintenance & Support

Maintenance and technical support for websites and software already in production, whether we built them or not.

Software is not finished when it ships. It is finished when it is retired. The work here is unglamorous by design: automated deploys, backups that have actually been restored from, alerts that fire before your customers notice. We would rather you never think about this layer at all.

What we build

  • Bug fixing
  • Content and minor updates
  • Technical maintenance
  • Performance monitoring and optimisation
  • Security maintenance and updates
  • Database maintenance
  • Server and deployment support
  • Backup support
  • Minor feature adjustment

Packages

Start here, then we scope the rest

Every figure below is a starting price. What you pay is settled after we understand the requirement, not before, and we will say so if a smaller package would do the job.

Basic

Start from

Rp350.000/ month

Rp500.000

Straightforward websites and simple systems that need a safety net.

Response
2×24 hours
Monitoring
Minor changes
  • Bug fixing
  • Basic technical support
  • Security updates
  • Email support
Start on Basic

Standard

Populer

Start from

Rp750.000/ month

Rp1.000.000

Businesses that want routine maintenance rather than a call when it breaks.

Response
1×24 hours
Monitoring
Included
Minor changes
Included
  • Everything in Basic
  • System monitoring
  • Performance checks
  • Backup monitoring
  • Minor changes
  • Full technical support
Start on Standard

Professional

Start from

Rp1.500.000/ month

Rp2.000.000

Systems that keep evolving and cannot wait a day for an answer.

Response
4–12 hours
Monitoring
Included
Minor changes
Included
  • Everything in Standard
  • Ongoing feature development
  • Priority support
  • Performance optimisation
  • Regular reporting
Start on Professional

Custom

Start from

Rp3.000.000/ month

Critical systems needing dedicated cover and an agreed response time.

Response
Agreed
Monitoring
Active
Minor changes
Included
  • Everything in Professional
  • Dedicated support
  • Response times you set
  • Active monitoring
  • Custom reporting
  • On-demand work outside the retainer

Response times, cover, and reporting are agreed in writing before the term starts.

Discuss a custom plan
Starting prices
Every figure is a starting point. The final price is set after requirements are gathered, scope is agreed, and a proposal is written.
Why these figures
We are a small team without the overhead a larger agency carries, and we price accordingly. Nothing in the scope is thinner for it. The same people build every project, and the deliverables are listed above in full.
What moves the price
Page and feature count, number of users and roles, workflow complexity, third-party integrations, reporting, APIs, and the level of support you need.
Domain and hosting
Included for the first year on website packages, at the specification set in the proposal. Renewals afterwards are billed at cost.
Scope changes
Anything outside the agreed scope is estimated before it is built, never after.

How we work

Monthly, or on a contract term

  1. Assessment

    We look at what exists, what state it is in, and what it will actually need.

  2. Maintenance plan

    The cover is written down: what is included, what is not, and what happens when something breaks.

  3. Monitoring and fixing

    Problems are found and fixed, ideally before anyone using the system notices them.

  4. Reporting

    You see what was done and why, rather than an invoice with no story behind it.

What you get

  • Maintenance plan
  • Bug fixes and updates
  • Monitoring
  • Regular reporting
  • Technical support

Built with

  • Docker
  • GitHub Actions
  • Vercel
  • Cloudflare
  • Sentry

Good fit if

  • Deploys are manual, risky, or done by one person
  • You have no visibility when something breaks
  • An existing system needs ongoing care, not a rebuild

Not for: Systems nobody can hand over. If the original build is undocumented and unowned, we start with an audit instead.

Tell us what you are building.

Send the problem rather than a spec. We will tell you which of these it needs, and what it would actually take.