SirehOS Lite
Independent open-source project · Benih 1.0 · Experimental beta

Infrastructure insight.
Wherever you work.

Diagnose · Monitor · Automate — Anywhere.

A portable, USB-live Linux environment for practical diagnostics, troubleshooting and learning. Boot it, explore your system, and collect evidence—without installing a replacement operating system.

Ubuntu 24.04 LTS base · x86-64 · CLI-first with a lightweight desktop · Safety-first diagnostics

SirehOS Lite green betel leaf emblem
Our history, purpose and direction

Every release has a name. Every name has a story.

🌱 Where SirehOS began

SirehOS takes its name from sireh, the Malay word for betel leaf, with a personal connection to Kebun Sireh in Penang, Malaysia. It began as an independent passion project: a wish to make infrastructure troubleshooting more approachable, portable and useful.

Our first release family follows the language of growth. Benih means seed: a small beginning with room to grow.

🧭 Our mission and vision

Mission: Build practical, transparent and safety-first tools that help people understand their systems, diagnose problems and learn by doing.

Vision: Grow an international open-source community where engineers, students, educators and curious newcomers can contribute tools, exchange knowledge and build useful technology together.

“A seed does not need to be big to grow into something meaningful.”

SirehOS Lite is not trying to be another everyday Windows replacement. Think of it as an infrastructure Swiss Army knife you can carry on a USB drive. The goal is original, integrated troubleshooting workflows—not merely a collection of unrelated utilities.

Meet the first flagship application

One Doctor. Ten ways to investigate.

Sireh Doctor is a graphical diagnostics workspace for beginners and experienced engineers. These are implemented beta tabs, not a claim of complete diagnosis or recovery. Results can be inconclusive, and some capabilities are intentionally limited for safety.

SD-05

Crash Detective

Investigate crash logs, application artifacts and Windows evidence when accessible.

See actual screen →
SD-06

Security Doctor

Inspect local access, network exposure and configuration evidence.

See actual screen →
SD-07

Data Rescue

Discover devices safely; recovery and copying are not enabled in this beta.

See actual screen →
SD-08

Repair Advisor

Turn existing findings into prioritized, non-destructive next steps.

See actual screen →
SD-10

Health Report

Consolidate cached findings and export or print a diagnostic report.

See actual screen →
The real boot experience · Beta 4 in QEMU

From the first boot screen to your own diagnostic workspace.

This is SirehOS Lite itself — not just a standalone application. Follow the actual Beta 4 boot sequence through GRUB, the branded splash, the live desktop and Sireh Doctor. All five images below are genuine QEMU screenshots captured during testing.

Actual QEMU Beta 4 screenshot: SirehOS Lite 1.0 Benih — Start Live System and Debug Boot
GRUB boot menuSirehOS Lite 1.0 Benih — Start Live System and Debug Boot · click to view full size
Actual QEMU Beta 4 screenshot: SirehOS Lite leaf emblem displayed during boot
Branded startup splashSirehOS Lite leaf emblem displayed during boot · click to view full size
Actual QEMU Beta 4 screenshot: Actual Beta 4 QEMU desktop with Sireh Doctor and Sireh Terminal shortcuts
SirehOS Lite desktopActual Beta 4 QEMU desktop with Sireh Doctor and Sireh Terminal shortcuts · click to view full size
Actual QEMU Beta 4 screenshot: Full Health Check running inside the booted SirehOS environment
Sireh Doctor in the live sessionFull Health Check running inside the booted SirehOS environment · click to view full size
Actual QEMU Beta 4 screenshot: SirehOS Lite wallpaper, launcher icons and bottom panel
Desktop and taskbarSirehOS Lite wallpaper, launcher icons and bottom panel · click to view full size

Testing on real hardware? Share your device model, UEFI or Legacy BIOS mode, and what worked (or failed) in SirehOS Discussions. Boot appearance and compatibility may differ across machines.

Real software · Real screens

See what the beta actually looks like.

These are genuine captures from Sireh Doctor. No fabricated success scores or simulated diagnostics. Some screenshots show tests run on a Linux Mint development machine, while the live environment is being tested separately in QEMU.

Actual Sireh Doctor beta screenshot: Full Health Check — before audit
Full Health Check — before auditActual beta capture · click to view full size
Actual Sireh Doctor beta screenshot: Full Health Check — completed audit
Full Health Check — completed auditActual beta capture · click to view full size
Actual Sireh Doctor beta screenshot: Hardware Doctor
Hardware DoctorActual beta capture · click to view full size
Actual Sireh Doctor beta screenshot: Storage Doctor
Storage DoctorActual beta capture · click to view full size
Actual Sireh Doctor beta screenshot: OS & Boot Doctor
OS & Boot DoctorActual beta capture · click to view full size
Actual Sireh Doctor beta screenshot: Crash Detective
Crash DetectiveActual beta capture · click to view full size
Actual Sireh Doctor beta screenshot: Security Doctor
Security DoctorActual beta capture · click to view full size
Actual Sireh Doctor beta screenshot: Data Rescue
Data RescueActual beta capture · click to view full size
Actual Sireh Doctor beta screenshot: Repair Advisor
Repair AdvisorActual beta capture · click to view full size
Actual Sireh Doctor beta screenshot: Command Clinic
Command ClinicActual beta capture · click to view full size
Actual Sireh Doctor beta screenshot: Health Report
Health ReportActual beta capture · click to view full size
Try it · Test it · Tell us what breaks

Download Benih 1.0 — Beta 4

Your first SirehOS Lite adventure starts here. Download the experimental USB-live ISO directly from the official GitHub release—no hunting through repositories or collapsed menus.

PUBLIC PRE-RELEASE · BETA 4

SirehOS Lite 1.0 Benih

Bootable ISO · Approximately 1.3 GB · 64-bit PCs

Official GitHub-hosted release asset. Your browser should begin downloading the .iso file when you select the green button.

Experimental beta: SirehOS Lite is not a guaranteed repair or data-recovery solution. UNKNOWN does not mean PASS. Data Rescue copying and automatic repairs are disabled. Test on a spare computer or virtual machine first, and keep backups of important data.

🧭 Prefer downloading through GitHub?

Open the Beta 4 release page, scroll to the bottom, expand Assets if it is collapsed, and select SirehOS-Lite-1.0-Benih-Beta4.iso. Do not choose “Source code (zip)”—that is not the bootable image.

▼ Assets 3
⬡   SirehOS-Lite-1.0-Benih-Beta4.iso ← Choose this ISO
▤   Source code (zip) Not the ISO
▤   Source code (tar.gz) Not the ISO

Illustrated guide based on the release page; GitHub's appearance may change.

🔐 Verify your download

Compare the SHA-256 checksum of your downloaded ISO with the checksum on the official Beta 4 release. The values must match exactly.

Linux
sha256sum SirehOS-Lite-1.0-Benih-Beta4.iso
Windows PowerShell
Get-FileHash .\SirehOS-Lite-1.0-Benih-Beta4.iso -Algorithm SHA256

Run the command from the folder containing the ISO, or provide its full path. A checksum verifies integrity, not overall software safety.

Getting started

Turn the ISO into a bootable USB.

You cannot make a bootable USB by copying the ISO file onto a drive as a normal document. Writing an ISO image replaces the USB's existing contents. Back up your files first.

🪟 Windows: Rufus

1. Download the ISO from the official SirehOS release page and verify its checksum.
2. Download Rufus from its official site. Insert an empty USB flash drive (8 GB or larger is a practical starting point).
3. In Rufus, select the correct USB device and choose the SirehOS ISO under Boot selection. Keep the suggested settings unless the release notes specify otherwise.
4. Select START, read any image-writing prompts carefully, and confirm only after checking the USB device. All data on that USB will be erased.
5. Restart your computer, open its boot menu (often F12, F9, Esc or another vendor-specific key), and select the USB drive.

🐧 Linux: Ubuntu, Debian, Fedora and Red Hat

The same Linux imaging method works across these distributions. Identify the removable drive using:

lsblk -o NAME,SIZE,MODEL,TRAN,MOUNTPOINTS

Unmount any mounted partitions on the selected USB first. Then write the ISO to the whole USB device, not a numbered partition:

sudo dd if="/path/to/SirehOS.iso" of=/dev/sdX bs=4M status=progress conv=fsync
sync
Danger: /dev/sdX is a placeholder, not a command to run unchanged. Replace it only after positively identifying your USB drive. Choosing your internal disk will destroy its data. NVMe/USB naming can differ. Do not use /dev/sdX1 (a partition).

After writing completes, safely eject the drive and use your computer's firmware boot menu to start SirehOS.

Boot behavior varies by firmware, Secure Boot configuration and hardware. Beta testers should try a spare machine or virtual machine first. SirehOS does not need to be installed to the internal disk.

Growth, not hype

From Benih to Tunas and beyond.

1.0 Benih · Seed
Experimental live system, Sireh Doctor, boot and diagnostic testing, evidence collection and feedback.
1.1 Tunas · Sprout
Richer diagnostics, improved usability and a reviewed catalogue of optional community tools.
1.2 Pucuk · Young shoot
Iterative capabilities shaped by reliability testing and community contributions.
1.3 Pokok · Tree
Longer-term growth, with release timing determined by technical readiness.

The broader Sireh Core vision includes OneScan, TimeShift, EvidencePack and PathFinder. Roadmap items are goals, not promises of features already available in Beta 4.

Engineers · Students · Curious minds

Come curious. Leave something better.

Boot it. Explore a diagnostic tab. Tell us what worked, what confused you, and what hardware you tested. Beginners are welcome, and respectful bug reports are as valuable as code contributions. We want to build a community that learns together.

Join GitHub Discussions for questions, ideas, feedback and community conversations. Use GitHub Issues for reproducible bugs and technical problems. Please remove passwords, tokens, personal identifiers and sensitive system information from shared reports.

“Built for infrastructure. Driven by community.”