Public demo
Try the example checks and inspect their evidence before setting up a workspace.
Open the demo →Start free.
Choose what you need.
Try a check, download the Terminal or inspect the tools. When you need hosted checks, use your JARVI3 account and credit wallet. Team workspace access is agreed separately.
Choose your entry point
One workflow. Different ways in.
Explore the technical entry point, graphical workspace and the permission boundary between them.
Select an illustrated object to inspect its role.
01 / 03
A technical surface for the work.
Start at the ECO> prompt, inspect local commands and connect to an approved organisation workspace when available.
Windows preview / current release recordConditions & scope
Explore the available Terminal ↗Terminal 2.0 is the product direction. The published download version and fingerprint are defined by the release record. Local commands use your Windows permissions.
What you can use today.
EcoKure Terminal
Use the local command prompt without an account. Connecting to an EcoKure workspace needs that workspace’s access and a read-only key.
View the current download →Standalone tools
Run UnitGate, EvidencePack or ReplayGate yourself. Each repository includes its own source, setup instructions and MIT licence.
UnitGate source ↗ EvidencePack source ↗ ReplayGate source ↗JARVI3
One account and purchased-credit wallet for supported hosted checks. Each check shows its price before you confirm. See current plans and credit options on JARVI3.
View JARVI3 plans ↗ Check hosted availability →SafeGate on EcoKure.net
Existing SafeGate plans keep their allowance. Supported shared-wallet checks are shown separately in your account, so a sign-in never silently converts or cancels a subscription.
Open EcoKure.net ↗EcoKure app & team pilots
The desktop app connects to your organisation’s workspace. Request access, or scope a pilot with a written price before any paid work.
Get the app → Discuss a pilot →Four stages. The first two cost nothing.
For work on your own systems, we agree the workflow, evidence question and price before a paid pilot begins.
Start on your own
Clone an open-source gate and run its suite, download the offline Lighthouse library, or verify an exported EvidencePack with the standalone verifier. None of it calls us.
Scoping
One workflow, one owner, one evidence question. We agree what a pilot would have to demonstrate, and what would count as failing it.
Control Proof, a bounded shadow pilot
The workflow runs beside your existing process, never in front of it. One controlled change is introduced. You get the evidence and a go / no-go against criteria agreed before the start.
See what is in it →Licence
Control packs you own, deployed where you choose — local node, your private cloud, or air-gapped.
Why pilots are quoted: a pilot is scoped to one workflow, one owner and one evidence question, and those differ enough that a published figure would be a guess dressed as a quote. The scoping conversation is free and ends with a written scope and a price, or with us saying it is not a fit.