Evidence
See signed, replayable demonstration records and the independent verifier.
Open evidence register →Download demo EvidencePack →Download verifier →Enterprise readiness
Proof that can survive the buyer conversation.
A concise route through what EcoKure can demonstrate today, what requires a customer pilot, and what is deliberately not claimed.
EVIDENCEDMEASUREDPILOTDESIGN ONLYNOT CLAIMED
Claim status
Read the boundary before you read the promise.
Each statement has a status and a route to the underlying material. “Measured” is not “production-ready”; “design only” is not an integration claim.
| Capability | Status | What that means | Inspect |
|---|---|---|---|
| Evidence chain and independent verification | EVIDENCED | Signed demo packs and a standalone verifier are published. | Open → |
| AWS target-representative run | MEASURED | Measured in a target environment; not a production customer certification. | Open → |
| Customer-boundary deployment | PILOT | The deployment pattern is defined; customer validation is still required. | Open → |
| Multi-cloud portability | DESIGN ONLY | The adapter map exists; equivalent applied runs are not yet proven. | Open → |
| ISO 27001 / SOC 2 / ISO 42001 certification | NOT CLAIMED | No certification is held. Controls are designed to be reviewable. | Open → |
| 24/7 managed operations | NOT CLAIMED | Support and on-call commitments must be agreed per pilot. | Open → |
Buyer pack
Everything needed to start an informed review.
Security
Review data handling, cryptography, deployment models and known gaps.
Open security pack →Deployment
Inspect the AWS reference path, portability map and production gates.
Open deployment readiness →Pilot
Choose one bounded workflow, shadow it, measure it and decide against written criteria.
Open pilot method →Control Packs
Map obligations into owned, versioned controls and evidence requests.
Open catalogue →Data processors
See which processors are used, where they sit and what remains customer-controlled.
Open subprocessors →Path to production
One workflow, five accountable gates.
01 · Boundary
Named owner, data boundary, intended use and excluded use accepted.
02 · Shadow
Run without actuating decisions; measure review workload and exceptions.
03 · Change
Introduce a controlled rule or source change and inspect impact.
04 · Evidence
Generate a signed pack, replay it independently and record limitations.
05 · Go / no-go
Customer steering group decides whether the evidence supports the next stage.
The operating principle
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, a certification, or an automatic conclusion that a customer meets a regulation.
- Not model validation, clinical judgment, financial advice or a replacement for an accountable decision-maker.
- Not a guarantee that every risk is found. Coverage is bounded by the selected Control Pack, evidence and pilot scope.
- Not production-ready merely because a benchmark passes. Customer security, resilience, ownership and operational validation still apply.
Operations
Release checks an operator can run.
Liveness
Process-level check for the deployment platform.
Open health check →Readiness
Database, protected corpus store and production secret configuration.
Open readiness check →Handoff runbook
Exact steps for promotion, recovery, rollback, incident response and offboarding.
Download production runbook →