Enterprise readiness

Define the environment.
Qualify the release.

12 claims, sorted strongest first. Each one carries the point where its evidence stops, so the weak rows are findable rather than buried.

Read the register Download trust pack Build a pilot brief
  1. 2 EVIDENCED A published artifact anyone can open and check.
  2. 2 MEASURED A bounded run with numbers, in a stated environment.
  3. 1 PUBLISHED Written down and inspectable. Not a measurement.
  4. 1 PILOT Defined, but it needs your environment to be true.
  5. 1 OUTLINE ONLY Drafted in engineering terms, not reviewed.
  6. 1 DESIGN ONLY The design exists. Nothing has been run against it.
  7. 1 NOT YET MEASURED Nothing has happened yet that could be measured.
  8. 3 NOT CLAIMED We do not hold this and are not claiming it.

Review the assurance boundary

Look at the contract and the evidence.

Move between the record, the declared scope and the remaining qualification work.

Open the evidence behind the statement.

Select an illustrated object to inspect its role.

01 / 03

Open the evidence behind the statement.

Check the source, version, environment and limitation before using a figure in an assessment.

Source-linked published records
Conditions & scope

Internal or local synthetic checks do not establish independent reproduction or customer validation.

Review our run files ↗
Architecture illustration · No operation performed
The register

Read the boundary before you read the promise.

“Measured” is not “production-ready”. “Design only” is not an integration claim. The right-hand column is the one worth your time.

  1. Deterministic verdict boundary

    The same input yields the same verdict, and the tests that show it are published.

    EVIDENCED
    Where the evidence stops

    Bounded synthetic inputs. It says nothing about inputs nobody has tried.

    Inspect

  2. Signed EvidencePack and independent verifier

    A signed demonstration pack and a standalone verifier you can run yourself.

    EVIDENCED
    Where the evidence stops

    Customer KMS custody is still a deployment gate.

    Inspect

  3. AWS target-representative run

    Capacity measured in a target-representative environment.

    MEASURED
    Where the evidence stops

    Not a customer production validation, and not an AWS endorsement.

    Inspect

  4. Change impact and selective replay

    When a source changes, what depended on it is replayed and the rest is shown untouched.

    MEASURED
    Where the evidence stops

    A reference store, not a customer graph. It works from declared dependencies.

    Inspect

  5. Offboarding and data erasure

    What a termination request deletes, what it cryptographically erases, and what was never held.

    PUBLISHED
    Where the evidence stops

    A published procedure. No customer has yet exercised it.

    Inspect

  6. Customer-boundary deployment

    The deployment pattern is defined and documented.

    PILOT
    Where the evidence stops

    Customer validation is still required. Nobody has run it in your boundary.

    Inspect

  7. Data Processing Agreement

    A published engineering outline of processing, retention and erasure.

    OUTLINE ONLY
    Where the evidence stops

    Not legally reviewed. Two clauses are named as unresolved.

    Inspect

  8. Multi-cloud portability

    An adapter map covering the supported cloud targets.

    DESIGN ONLY
    Where the evidence stops

    No equivalent applied run exists on a second cloud.

    Inspect

  9. Service level agreement

    No SLOs are published.

    NOT YET MEASURED
    Where the evidence stops

    No production deployment or pilot has run yet to measure them from.

    Inspect

  10. 24/7 managed operations

    No support or on-call commitment exists by default.

    NOT CLAIMED
    Where the evidence stops

    It must be agreed per pilot, in writing.

    Inspect

  11. Enterprise production readiness

    This page does not assert that EcoKure is production-ready for you.

    NOT CLAIMED
    Where the evidence stops

    It requires your infrastructure, your security review and a pilot.

    Inspect

  12. ISO 27001 / SOC 2 / ISO 42001 certification

    No certification is held.

    NOT CLAIMED
    Where the evidence stops

    Controls are designed to be reviewable. That is not accreditation.

    Inspect
Path to production

One workflow, five accountable gates.

A sequence, not a menu. Each gate is a decision somebody in your organisation signs, and none of them is ours to sign.

  1. 01

    Boundary

    Named owner, data boundary, intended use and excluded use, accepted in writing before anything runs.

  2. 02

    Shadow

    Run beside the existing process without actuating decisions. Measure review workload and exceptions.

  3. 03

    Change

    Introduce a controlled rule or source change and inspect what it affected and what it left alone.

  4. 04

    Evidence

    Generate a signed pack, replay it independently, and record the limitations you found.

  5. 05

    Go / no-go

    Your steering group decides whether the measured result supports the next stage.

EcoKure does not replace accountable people. It makes the decision boundary, control state and evidence trail visible enough for them to govern.

Limits

What this is not.

  • Not legal advice, not a certification, and not a conclusion that you meet a regulation.
  • Not model validation, clinical judgment or financial advice, and not a replacement for an accountable decision-maker.
  • Not a guarantee that every risk is found. Coverage is bounded by the Control Pack, the evidence and the pilot scope you choose.
  • Not production-ready because a benchmark passed. Your security, resilience, ownership and operational validation still apply.
Operations

Release checks you can run right now.

Machine-readable on purpose. A 200 means the check passed; the strict readiness check returns 503 while any required production gate is still open, which is an honest pending gate rather than a broken link.

Liveness

Checking…

Process-level check for the deployment platform. It does not depend on the database.

Open health check →

Readiness

Checking…

Checks the application and protected corpus databases, production secrets, transactional email, canonical HTTPS and reviewer SSO. The reviewer gate requires the ecosystem SSO client secret and a configured reviewer email allowlist. Until both are set, /readyz correctly returns 503 even while public pages are serving.

Open strict readiness check →

Handoff runbook

Checking…

Promotion, recovery, rollback, incident response and offboarding, in readable Markdown.

Open production runbook →
Go deeper

The rest of the material.

Next · Review the posture Trust centre