redeven

Redeven

Secure the real Environment, not just the browser tab.
Turn any host into a secure Environment for files, terminals, monitoring, ports, browser development, desktop access, and optional AI-assisted work.

Get Desktop | Install CLI | See what it does | Common workflows | Docs | License

Redeven runs on the host where your Environment lives. Open that Environment from the browser, from Redeven Desktop, or from a local URL while the real files, terminals, processes, services, and app state stay where they belong: in that Environment.

Why it feels different

• 🔐 Real Environment first — you operate the actual runtime state, not a thin illusion of it.
• 🧭 One place to work — files, terminal, monitoring, ports, notes, and browser development sit together instead of splintering across separate tools.
• ⚡ Fast entry from browser or desktop — choose the Environment, open the workspace, and start with the context already nearby.
• 📦 Distribution stays auditable — the same project ships as CLI and Desktop through public GitHub Releases with checksums and signatures.

What Redeven lets you do

Redeven gives you a secure workspace for a real Environment. Open it from the browser or desktop, then inspect files, run commands, watch processes, reach services, start a browser IDE, and bring AI into the task without leaving the Environment context.

A typical session

1. Choose an Environment from the browser or desktop.
2. Check files, logs, resource usage, and running processes.
3. Open a terminal exactly where the problem is.
4. Start a browser IDE only when you need deeper code editing.
5. Open ports or app previews from the same workspace.
6. Ask AI for help when the task benefits from it.

Common workflows

When an SSH Host Environment is opened from Redeven Desktop, Flower can use the Desktop Local Environment's model configuration through a short-lived local broker while tools still execute on the SSH host. Provider API keys stay on the user's machine and are never copied into the remote runtime config.

Quick start

From zero to a live endpoint in a few minutes.

1. Install the CLI

curl -fsSL https://raw.githubusercontent.com/floegence/redeven/main/scripts/install.sh | sh

Prefer a native shell? Download Redeven Desktop from GitHub Releases.

Redeven Desktop keeps environment entry simple on purpose: one launcher, one card system, and one place to open your Local Environment, compatible provider environments, saved Redeven Local UI URLs, and SSH hosts.

2. Bootstrap once

redeven bootstrap \
  --controlplane https://<redeven-environment-host> \
  --env-id <env_public_id> \
  --bootstrap-ticket <bootstrap_ticket>

Bootstrap writes the Local Environment config to ~/.redeven/local-environment/config.json by default. Each OS user / Redeven profile state root has one Local Environment identity, and that Local Environment is bound to one provider Environment at a time; running bootstrap again with a fresh one-time ticket rebinds that Local Environment.

Desktop and browser-assisted flows use the same one-time bootstrap_ticket contract. The desktop/runtime exchange contract is described in docs/DESKTOP.md.

3. Run the endpoint

redeven run --mode hybrid

Expected result:

• redeven run starts without config validation errors.
• The endpoint shows online in the control plane.
• The browser workspace can open basic file and terminal actions.

4. Pick how this Environment should run

Security, without stealing the spotlight

Redeven leads with capability, but the runtime is still the trust boundary because it owns the real Environment.

• The runtime lives on the endpoint and keeps plaintext there.
• The control plane issues bootstrap payloads, grants, and immutable session metadata.
• Flowersec carries encrypted bytes between the client and the endpoint runtime.
• Effective permissions come from server-issued session grants, clamped by the local permission policy.
• Local config, E2EE material, audit logs, and diagnostics stay in the endpoint state directory.
• GitHub Releases remain the public source of truth for binaries, checksums, and signatures.

Read the full contract in docs/CAPABILITY_PERMISSIONS.md, docs/PERMISSION_POLICY.md, and docs/RELEASE.md.

Docs by task

For developers

Build, lint, and verify from source.

./scripts/lint_ui.sh
./scripts/check_desktop.sh
./scripts/build_assets.sh
go build -o redeven ./cmd/redeven

./scripts/install_git_hooks.sh
node scripts/generate_third_party_notices.mjs --check

License

Redeven is licensed under the MIT License. Third-party dependency notices are tracked in THIRD_PARTY_NOTICES.md; release archives and Desktop packages include these files alongside the runtime artifacts.

Open-source scope

This public repository covers the endpoint/runtime layer, Redeven Local UI behavior, the desktop shell, and the GitHub Release contract.

Organization-specific deployment automation, control-plane implementations, and site-specific packaging wrappers are intentionally out of scope here.