Download Land
Source builds are active today. Public installers, signing, and verification artifacts are still being prepared.
System Requirements
A quick check before you download saves a reinstall later.
Minimum Requirements
Processor: Intel Core i5 or AMD Ryzen 5 / Apple Silicon
Memory: 4 GB RAM
Disk Space: 500 MB
Recommended for the Best Experience
Processor: Intel Core i7 or AMD Ryzen 7
Memory: 8 GB RAM
Disk Space: 1 GB SSD
Supported Operating Systems
macOS 11+Windows 10+Ubuntu 20.04+ / Fedora 35+ / Debian 11+
Verification Will Ship With Public Releases.
Release downloads will publish checksum and signature material when public installers are available.
Download Verification
SHA-256 Checksum
Available with public release artifactsRelease Signature
Available with public release artifactsSigned with key ID: Published with each release
Verification Instructions
Verification instructions will be published beside the installer, checksum, and signature artifacts.
Integrity Check
SHA-256 Checksum
Available with public release artifactsRelease Signature
Available with public release artifactsVerification Instructions
Air contains checksum and integrity code. Public release verification material will be published with the installers.
Previous Releases
Download an older version if you need to pin to a specific release.
| Version | Published | Size | Downloads |
|---|
Telemetry Is Compile-Gated in Land.
Land keeps telemetry and tracing behind explicit feature paths in the native code. The default public message is simple: do not claim silent uploads, and do not imply diagnostics are sent unless a build enables that infrastructure.
Telemetry Policy
Full disclosure on what Land collects - and what it does not.
Compile-gated by default.
Disabled
Land uses Rust feature gates for telemetry and tracing paths. Public builds should describe which feature profile was used instead of relying on a blanket privacy slogan.
Telemetry-related code is behind feature paths and should be documented per build profile.
No Microsoft endpoint dependency.
Disabled
Land is built from a CC0 Code-OSS-derived base with Microsoft service dependencies removed or replaced where the source path requires it. Crash reporting should be documented by the release profile that enables it.
CC0 -licensed Code-OSS-derived base with Land-owned service wiring.
No blanket tracking claim.
Disabled
The editor should say exactly which runtime services are enabled. Website analytics, account auth, and editor telemetry are separate systems and should not be collapsed into one claim.
Disabled feature paths stay out of the runtime.
Active
Rust
cfg(feature)gates can remove disabled code paths at compile time. That is the claim Land can make when a published build profile shows which features were compiled.Rust cfg(feature) gates eliminate dead code at compile time.
Need traces? Opt in. Your infrastructure only.
Optional
Tracing infrastructure exists in source for deployments that choose it. Public docs should name the endpoint and build feature before presenting it as enabled.
cargo build --features TelemetrySub-features: MetricsCollection,DistributedTracing
Extension host timing stays in the process.
Active
Cocoon has internal timing and service diagnostics for extension-host work. Unless a transport is configured, that data is local process instrumentation rather than an external product-analytics claim.
Effect-TS TelemetryService with TelemetryMock layer for zero-overhead testing.
Build Variants
9 named profiles across 16 test permutations. Every combination verified.
| Profile | Tier | Workbench | Features | Status |
|---|---|---|---|---|
| debug | Debug | Browser | Browser UI | Available |
| debug-mountain | Debug | Mountain | Mountain UI | Recommended |
| debug-electron | Debug | Electron | Legacy Check | Legacy |
| production | Release | Mountain | Release Path | Recommended |
| release | Release | Mountain | Bundle Path | Available |
| web-browser | Release | Browser | Web Path | Available |
| bundler-preparation | Build | - | - | Available |
| swc-bundle | Build | - | - | Experimental |
| oxc-bundle | Build | - | - | Experimental |
Deployment Strategies
Four deployment modes from development to production.
Development
Change a file, see it instantly. Hot-reload in Tauri with the Sky dev server. No manual rebuilds needed.
bash Maintain/Dev-Mountain.shHot ReloadInstant PreviewDev ServerNo Bundling
Debug Build
Full debug symbols for stepping through code. Three profiles: Browser, Mountain, and Electron.
bash Maintain/Debug/Build.sh --profile debug-mountainDebug Symbols3 ProfilesSource MapsFile Watch
Release Build
Optimized release packaging path. Public signing and published verification artifacts are still being prepared.
bash Maintain/Release/Build.sh --profile productionOptimizedSigning PlannedClean BuildPackaged
Web Deployment
Run Land in the browser without installing anything. No native shell needed.
bash Maintain/Release.sh --profile web-browserNo InstallBrowser OnlyWeb DeployOXC Bundled