Skip to content
Niqcode

Managed Service

Software does not stop needing attention after launch. Managed service is the arrangement for the years after, whether we built it or someone else did.

Ongoing operation of what we or someone else built: monitoring, deployment, security patching, incident response and a monthly change budget.

What we do

Managed Service

We take over operation of a running system: monitoring and alerting, deployments, security patching, backup verification and incident response. If we did not build it, the engagement starts with an audit and a written picture of what we are taking on.

Response commitments are agreed by severity, so an outage and a cosmetic bug are not treated as the same thing. What we are on the hook for, and what we are not, is written down before the first month starts.

A monthly change budget covers the small work that would otherwise wait for a project: a report, a field, a permission, an integration change. Anything larger is quoted separately rather than absorbed quietly.

Managed Service

What you get

  • Monitoring, alerting and an on-call path agreed by severity

  • Deployments, security patching and verified backups on a stated schedule

  • Incident response with a written cause and correction after the fact

  • A monthly change budget for small work, with what it covers made explicit

  • An entry audit when we inherit a system we did not build

Our Expertise

Typical stack

  • Docker: containerised builds and deployments
  • Kubernetes: orchestration for multi-service systems
  • Go: high-throughput services and integrations
  • Node.js: APIs, jobs and integration workers

Start with one conversation

Describe the problem and you get our reading of it, a scope and a price. If we are not the right fit, we will say so.