Connect your team to EcoKure.
A Windows console with an ECO> prompt. Point it at your company's EcoKure workspace, sign in with a read-only key, and each person sees their projects and records with their own permissions.
The download and local command prompt are free, with no account needed. Workspace access is managed separately for your organisation.
ECO> connect https://ecokure.example.com Runtime set to https://ecokure.example.com. Type login to authenticate. ECO> login Read-scoped API token (hidden): Login accepted for this session only. ECO> projects prj_4f2a91 Ward 4 medication checks prj_8c03de Invoice controls ECO> status Environment production Role reviewer Console READ_ONLY Host shell NOT EXPOSED ECO>
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 recordTerminal 2.0 is the product direction. The published download version and fingerprint are defined by the release record. Local commands use your Windows permissions.
Three steps for each person.
- Install itExtract the ZIP and run the installer. It only writes to your own user profile: no administrator rights, no background service. Local commands work straight away.
- Connect your workspace when you need itType
connectwith your company's EcoKure address, thenloginwith a read-only key from Settings in the app. Your workspace must already grant you access. - Work from the prompt
projects,projectandstatusshow what you are allowed to see, with links straight into the app.
One account, one credit balance.
Type account login to sign in through your browser, then credits to see your JARVI3 plan and purchased JV3 balance. EcoKure reads the same wallet, so there is nothing to transfer.
Type checks to open supported online checks. You review the input and price before spending credits. Local Terminal commands stay free; your organisation manages workspace permissions separately.
Read-only where it meets EcoKure.
- EcoKure only answers questions.The connection accepts a short list of read-only commands. It never runs anything on your company's server.
- Your permissions apply.Each person sees only the projects their account can open. A key with the wrong scope is refused, and a revoked key stops working at once.
- Your key stays in memory.It is forgotten when you log out, connect somewhere else, or close the window.
- On your own PC it is a normal command prompt.Commands like
gitordirrun with your Windows account's access, as they would in CMD. It is not a sandbox, so follow your IT team's software policy.
Compare the fingerprint before you install.
This preview is not code-signed yet, so Windows may warn you. Check that your file matches this SHA-256 fingerprint:
84347882364f45247867dd389b6b138adffe65d23e9b07c49179d44d61483bcf
Get-FileHash .\EcoKure-Terminal-Windows-x64.zip -Algorithm SHA256
A matching fingerprint shows the file has not changed since we published it. It is not the same as a publisher signature.
Rolling it out to a whole team?
We can help you set up the workspace, keys and permissions for a pilot.