Download

Download and local access

Ethen’s primary experience is the authenticated web workspace. Additional desktop or local-runtime options may exist for users who need local model lanes or native tooling. Availability depends on product stage, operating system support, and account eligibility.

1. Web-first access

Most users should start in the browser console. The web workspace provides routing, review, and collaboration features without requiring a local install. If your organization restricts browser apps, work with IT on allowlisting and identity controls. Sign in only through official Ethen / Upcube domains.

• Browser console is the primary path.
• IT allowlisting may be required.
• Use official domains only.

2. Desktop or local components

Where a desktop app, sidecar, or local runtime is published, install only from official links provided in-product or on this site. Do not trust repackaged installers from third-party mirrors. Local components may need OS permissions for files, network, or microphone features you enable. Verify checksums or signatures when the product publishes them.

• Install only from official sources.
• Permissions depend on features you enable.
• Prefer signed builds when published.

3. Local model lanes

Local lanes can keep some model execution on customer machines. They require sufficient hardware, correct runtime setup, and ongoing patching. Local execution does not automatically remove all cloud account or metadata traffic. Map data paths before assuming a fully offline posture. See Privacy and Security policies for boundaries.

• Local lanes need hardware and maintenance.
• Cloud metadata may still exist.
• Map paths before sensitive use.

4. Security expectations

Keep devices patched, disk encryption enabled where appropriate, and admin privileges limited. Treat local caches and downloaded models as sensitive artifacts. Revoke device access when staff leave. Do not share machine-level credentials for team accounts. Report suspected trojanized installers immediately.

• Patch and encrypt endpoints.
• Treat local model artifacts as sensitive.
• Report suspicious installers.

5. Support and updates

Update channels depend on how a component is distributed. Use in-product update guidance when available. Unsupported modified builds may not receive help. Enterprise deployment may require IT packaging beyond consumer install flows. For access issues, use published support channels.

• Follow official update channels.
• Modified builds may be unsupported.
• Enterprise IT packaging may be required.

Availability

Downloadable clients, desktop shells, or local runtimes are offered only when published for your platform. If a download is not listed, use the web console. Private alpha features may be invite-gated.

• Web console: Primary access path for most users.
• Desktop/local paths: Available only when published for a platform.
• Invite stages: Some builds may be limited to approved testers.
• No fake links: This page does not invent installer URLs.

Status

Download page describes access posture without promising unpublished installers.

• Web-first: Console remains primary.
• Honest availability: No invented download buttons.
• Local responsibility: Customer devices need hardening.
• Security-linked: See Security Statement.

Not legal advice

These pages explain product and policy posture for Upcube / Ethen. They are not legal advice and do not replace counsel for your jurisdiction, industry, or use case.

Evidence and claim boundaries

This statement describes Ethen’s current posture without making unsupported certification or compliance claims. Configuration, provider selection, and enterprise agreements can change data paths and controls.

• No certification claim: No SOC 2, ISO 27001, HIPAA, PCI, or penetration-test guarantee is claimed here.
• Shared responsibility: Customers control members, keys, devices, and integrations.
• Provider-dependent paths: Third-party providers apply their own security practices.
• Continuous change: Controls evolve; public pages avoid frozen false guarantees.

Access paths

Users should be guided toward routes that are actually available and documented.

• Open the console
• Explore local lanes
• Read local model docs
• Ask a product question

Related policies

• Security Statement

  Security posture for accounts and devices.

• Privacy Policy

  Data paths including local lanes.

• Terms of Service

  Account rules.

• Console

  Primary product entry.

Frequently asked questions