Know where every function stands. And prove it.

Stadig scores every business function against its recovery targets, maps what it runs on, and keeps the evidence behind each result. See where the whole portfolio stands, then trace any number back to where it came from.

Watch the tour See the capabilities

Bring any cloud or SaaS resource a function depends on. Stadig prices each one and flags what is over-provisioned for its target.

stadig · Reliability & cost narrated · 2 min

Readiness at a glance

Every function carries one of five readiness bands.

Each is scored across its recovery objectives, and its band shows the result. The number and the scoring code ride with the colour, so the band still reads when colour alone would not, including for colour-blind users.

1 Critical no_requirements_met

2 Poor some_requirements_met

3 Stale validation_stale

4 Near met_but_not_validated

5 Met all_requirements_met

What it does

Six surfaces, one continuity programme.

Each one scores the real state of a function against what it is supposed to be, then keeps the trail behind the result: its recovery targets, its risks, the resources it runs on, and what they cost.

Portfolio dashboard

Every function, scored against its recovery objectives.

Each business function is scored across service level, recovery time, recovery point, throughput and response, then rendered as readiness bands. Selecting one opens a drawer with its criticality, commitment tier and recovery strategy.

Programme maturity and a health trend over time
Per-function drawer: criticality, tier, strategy

Business functions5 live

Function	Readiness
Mobile Banking API	55454
Card Payments	43543
Customer Onboarding	32432
Fraud Detection	54455
Statements & Reporting	2132—

Needs attention

One prioritised feed of what to work on next.

The queue pulls several signals into one list: stale business impact analyses, reassessments still in draft, overdue recovery tests, service-map drift and risk-band transitions, with the most overdue at the top.

Five signal types, one extensible queue
Surfaced as a live count on the dashboard

Needs attention18 pending

Stale BIACard Paymentsbia · 412d old412d

In draftFraud Detectionreassessment6d

OverdueMobile Banking APIrecovery test+23d

DriftCustomer Onboardingservice map2d

Amber → RedPayments Gatewayrisk transition1d

Risk register & MBCO

Residual risk with the dated trail behind it.

Every identified risk is scored by likelihood and impact; Stadig computes a residual band and keeps a full band history, so when a risk moves from amber to red you have the dated reason why. The MBCO order ranks what must keep running, and in what sequence, when resources are scarce.

Likelihood × impact → residual band
Immutable, dated band-transition history

Risk registerresidual

Risk	L×I	Band
Region-wide outage	4 × 5	1
Key-person loss	3 × 4	2
Vendor SLA breach	2 × 4	3
Backup restore gap	2 × 3	4

Service map

The resources a function actually runs on.

A per-function canvas lays out the concrete resources a function depends on, grouped by tier, across any cloud or SaaS provider. Add anything: a managed database, a CDN, a message queue, a third-party SaaS dependency. Some are discovered automatically; others are added by hand. Stadig continuously tracks drift between what is declared and what is really deployed.

Any cloud or SaaS resource, discovered or added by hand
Continuous declared-vs-deployed drift

Service map · Mobile Banking API

Mobile Banking API

rds-postgresaws · discovered

redis-cacheazure · discovered

cloud-cdngcp · discovered

object-storeaws · manual

datadogsaas · manual

secrets-vaultazure · discovered

1 drift redis-cache plan changed since last sync

Reliability & cost

The cheapest option that still meets the target.

For each function Stadig picks the lowest-cost catalogue option that still meets its recovery targets and prices it. Just as importantly, it flags over-provisioning, surfacing more than ten thousand dollars a month of potential savings across the portfolio, function by function.

Pareto frontier of cost versus reliability
Over-provisioning flagged with the cheaper tier

Cost rollupoverprovisioned

Mobile Banking API$1,895/mo−$960

Card Payments$2,300/mo−$1,100

Customer Onboarding$1,800/mo−$900

Fraud Detection$1,150/mo−$540

Potential portfolio savings $10,420/mo

Resource catalogue

Building blocks under a governed lifecycle.

Reusable resource configuration options move through draft, review, publish and retire, so the building blocks that functions depend on are themselves version-controlled and approved before anything relies on them.

Draft → review → publish → retire
Composed (IaaS) and plan (managed) options

Option lifecycle · Primary database (Multi-AZ)

01Draft 02Review 03Published 04Retired

Recorded walkthroughs

See it driven, end to end.

Three recordings, narrated and unedited. Pick a chapter; each loads on demand, so nothing downloads until you press play.

stadig · Portfolio dashboard

Trust through traceability

Built to survive an audit.

Stadig answers one question with evidence: is this function adequately protected, and can you prove how you know? Every answer points back to the records that produced it.

A complete change history

Every approval, edit and rejection is recorded with its actor and timestamp. Nothing is silently overwritten, so the full history of how a function reached its current state is always there to read.

An audit pack behind every approval

Each approvable artefact moves through draft, review, approval and rejection. An approval links back to the complete, versioned audit pack that produced it, ready to hand to a reviewer.

Every number traces to its source

Residual bands, recovery aggregates and cost rollups all trace back to the inputs and records behind them, so you never present a figure you cannot defend.

The whole portfolio, scored in one place.

Recovery targets, risks and costs for every function, across every cloud and SaaS provider it runs on.

Watch the walkthroughs See the capabilities