Skip to content
Snigdha OSDecentralized

Product Identity & Genesis

About Snigdha OS Decentralized

An independent, privacy-focused live operating system built from first principles on Arch Linux, engineered for user sovereignty and verifiable security.

Why Snigdha OS Decentralized Exists

In an era of ubiquitous digital surveillance, centralized telemetries, and invasive ad-driven ecosystems, operating systems have increasingly become tools of corporate observation rather than sovereign personal tools.

Snigdha OS Decentralized was initiated within the Snigdha OS project to construct a hardened, stateless, and censorship-resistant operating environment. Unlike standard desktop Linux distributions that assume long-term disk persistence and open outbound networking, Snigdha OS Decentralized starts from the foundational premise that untrusted networks and physical hardware seizure require proactive architectural containment.

Edition Architecture Disambiguation

Snigdha OS Decentralized vs. Snigdha OS Eclipse

The Snigdha OS project develops two fundamentally distinct operating system editions targeted at different computing needs. It is critical not to confuse their threat models.

Sovereign Privacy EditionDecentralized

Snigdha OS Decentralized

  • ›Execution Medium: 100% Removable Live USB media; non-installable to internal storage.
  • ›Session State: Volatile RAM (Amnesia); zero disk footprints upon shutdown.
  • ›Networking: Transparent torification via NetGuard; non-Tor traffic dropped fail-closed.
  • ›Primary Mission: Privacy, censorship resistance, whistleblower safety, and security research.
General Purpose EditionEclipse

Snigdha OS Eclipse

  • ›Execution Medium: Installed directly to NVMe SSD or hard drives via Calamares.
  • ›Session State: Fully persistent standard Linux installation.
  • ›Networking: Standard clearnet networking with optional VPN/wireguard.
  • ›Primary Mission: Daily computing, high-performance gaming, development workstations.
Upstream Architecture

Why Arch Linux Baseline?

Most privacy distributions rely on Debian Stable. While Debian provides conservative stability, its multi-year release freezes create critical limitations: outdated hardware drivers for modern Wi-Fi chipsets, stale Tor and cryptographic libraries, and complex legacy packaging overhead.

Modern Hardware Support

Arch Linux LTS kernels provide out-of-the-box driver initialization for contemporary Intel, AMD, Wi-Fi 6E/7, and NVMe controllers without custom backports.

Clean ArchISO Foundation

Built from the official minimal baseline profile, excluding unnecessary desktop services, cloud agent daemons, and tracking dependencies.

Unprivileged Reproducibility

Utilizes user-namespace fakeroot wrappers allowing anyone to audit and compile the full distribution ISO without granting unrestricted root permissions to build scripts.

Target Use Cases

Who Should Use Snigdha OS Decentralized

  • ✓Journalists & Whistleblowers: Communicating under hostile network observation or crossing borders where devices may be seized.
  • ✓Security Researchers & Auditors: Executing isolated security testing tools from Penetration Center without contaminating their workstation.
  • ✓Privacy Advocates: Browsing untrusted networks, public Wi-Fi hotspots, or restrictive institutional connections without leaving residual logs.
  • ✓Developers: Signing Git commits, handling OpenPGP keys, or managing credentials inside an ephemeral memory environment.
Inappropriate Use Cases

Who Should NOT Use Snigdha OS Decentralized

  • ✗Heavy Gamers: AAA gaming with proprietary anti-cheat (EasyAntiCheat, Vanguard) and Steam proton libraries is unsupported on an amnesic live OS.
  • ✗Users Requiring Continuous Background Torrents: Bittorrent over Tor degrades the network for everyone and leaks non-TCP traffic.
  • ✗Those Expecting Permanent Desktop Installation: The OS is explicitly designed to never touch internal hard drives.
  • ✗Anyone Believing in “Magic Invulnerability”: No OS can protect you from compromised UEFI firmware, hardware keyloggers, or reckless human mistakes.

Dive deeper into the architectural implementation

Explore the 7-layer trust stack and fail-closed NetGuard packet filter.

Inspect Architecture Blueprint