Cluster Pulse Point
Assessment detail

Cluster reliability assessment

A time-boxed examination of how your application cluster fails, recovers, and signals trouble — delivered as a formal reliability report.

On-site or remote review · 10–15 business days · Sydney office or your environment · Fixed project fee from AUD 18,500

Ask about this assessment See fee guidance

Who this is for

Platform leads, SRE managers, and risk owners who need an independent read of cluster reliability — especially when monitoring graphs look fine while outages keep recurring, or when a board paper needs more than screenshots.

Result

You receive a cluster reliability report covering failure modes observed or inferred, recovery paths, signal quality (what predicts trouble versus what only alarms after damage), and a ranked action list. The report is written for mixed audiences: engineers get specifics; sponsors get consequence language.

Scope included

  • Access briefing and inventory of the target application cluster (nodes, deploy path, dependencies you nominate)
  • Review of recent incidents, runbook excerpts, and the metrics you already collect
  • Application analytics pass focused on retry behaviour, saturation, and dependency lag — not a full architectural redesign
  • Draft findings for your technical contact, then a closed reading with agreed owners
  • Final PDF report plus a one-page executive brief

Scope excluded

  • 24/7 monitoring, on-call coverage, or tooling licences
  • Code rewrites, infrastructure provisioning, or vendor negotiations
  • Forensic investigation of a live breach (we will refer you to an incident specialist)

Provider

Work is led by a Cluster Pulse Point reliability analyst, with a second reader on the final report. We remain accountable for clarity of findings; remediation stays with your teams unless separately engaged.

Process & timeline

  1. Scoping call (30–45 minutes) — confirm cluster boundaries and decision the report must support
  2. Access & evidence (days 1–3) — credentials, sample logs, incident archive
  3. Analysis (days 4–9) — failure-mode mapping and application analytics review
  4. Draft & reading (days 10–12) — corrections, then owner briefing
  5. Final delivery (by day 15) — signed report

Preparation

Nominate one technical contact with authority to grant read access, and one decision owner who will attend the reading. Share at least ninety days of incident notes where available.

Constraints

We assess the cluster you name — not every system in the estate. Production write access is never required; read-only evidence is preferred.

Pricing basis

Fixed project fee from AUD 18,500, adjusted for cluster size and number of application surfaces. Multi-region estates are quoted separately.

Next step

Request a scoping call and mention “Cluster reliability assessment” so we can prepare the right questions.