Support & careSLAProject rescue

Website & app maintenance in MalaysiaWe keep it turning.

Launch is the start, not the finish. We look after what we build, and what others started, with support sized to how critical your system is, security in every release, and a handover you can actually use.

Support that fits the project.

Every support arrangement comes with an SLA. What's in it depends on how complex and how critical your system is, so we agree response times, hours and scope with you rather than force a one-size package.

For websites & simple apps

Essential

Keep it healthy, secure and up to date.

  • Uptime monitoring
  • Security & dependency updates
  • Backups
  • Business-hours support
For business systems & apps

Standard

Everything in Essential, plus room to keep improving.

  • Agreed response times
  • Monthly hours for fixes & small changes
  • Performance checks
  • Regular health reports
For critical platforms

Critical

For systems your business can't run without.

  • Priority response
  • Extended support hours
  • Incident handling & reporting
  • Capacity & disaster-recovery planning

Response times, support hours and monthly allowances are set in your SLA, based on the project.

Secure on every deployment.

Security isn't a phase at the end. These checks are part of how every release goes out.

  • Hardened configurationSecure defaults, least-privilege access, no debug settings in production.
  • Encrypted everywhereHTTPS on every endpoint, encrypted secrets, nothing sensitive in the code.
  • Dependency scanningKnown vulnerabilities checked and patched before each release.
  • OWASP-minded codeInput validation, safe authentication and protection against common attacks.
  • Backups you can restoreAutomated backups, and restores actually tested.
  • Logging & monitoringSo problems are spotted early, not reported by your users.

A handover you can use.

Whether we keep supporting it or your team takes over, you get everything needed to own the system.

  • Source code & ownershipFull repository access, transferred to your accounts.
  • Credentials & accountsHosting, domains, app stores and services, handed over securely.
  • DocumentationArchitecture, setup and deployment guides your next developer can follow.
  • Walkthrough & trainingA live session with your team, recorded for later.
  • Admin guideHow to manage content, users and settings day to day.
  • Warranty periodWe stay on hand to fix issues found after go-live.

Stuck or broken? We'll take a look.

Projects stall: a developer leaves, a deadline slips, something breaks and nobody knows why. We start with an honest health check, then help you decide what to do next.

01

Health check

We review the code, infrastructure, security and what's been delivered so far.

02

Honest report

What works, what's at risk, and what it would take to finish, in plain language.

03

Stabilise

Fix what's urgent first: security holes, crashes, broken deployments.

04

Continue

Finish the build, or move it onto a support plan, whichever fits.

Sound familiar?Developer disappearedHalf-finished build Keeps crashingCan't deployNo documentationSecurity worries
Request a health check

Good to know.

Do you support projects you didn't build?

Yes. We start with a health check so we understand the system before taking it on, and we'll be honest if a rebuild makes more sense than a repair.

How is the SLA decided?

By how complex and how critical the system is. We agree response times, support hours and what's covered with you before anything is signed.

Can we switch from support to our own team later?

Of course. The handover gives your team the code, accounts and documentation to take over smoothly.

What happens if something breaks outside support hours?

That depends on your plan. Critical systems can include extended hours; for others, monitoring catches issues early and we respond within the agreed times.

Let's keep it running.

Tell us about your system, whether we built it or not, and we'll suggest the right level of support.

Get in touch