Open-source project
BryanLunduke/LCOS avatar
BryanLunduke/LCOS

LCOS: Lunduke's Devuan-based desktop OS without Systemd, accounts or AI

The Lunduke Computer Operating System

531 stars31 forksCSSGPL-3.0

At a glance

What is it?
The Lunduke Computer Operating System is a Beta-stage Linux distribution built on Devuan, shipping stripped-down Brave Origin as its browser and a 90s-style desktop. It is a monarchy, not a community project, and the README says so plainly.
Who is it for?
LCOS is for people who want a Devuan-based desktop with no online accounts, no ID verification and no AI features, and who accept that a single person controls the project. It is not for anyone who needs community governance, a documented upgrade path between releases, or a support channel that does not require a Lunduke Journal subscription, because the README names the subscriber-only forum as the only place to ask questions or report issues.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 7 days ago.
What is it written in?
Mainly CSS, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 20, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • BryanLunduke/LCOS531 ★ · +154
Star history
Repository2026-09-172026-11-20
BryanLunduke/LCOS377531

154 Stars in the last 64 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What LCOS is, and the specific user it is built for

LCOS is a Linux system assembled by Bryan Lunduke, described in the README as "built by Lunduke, for Lunduke." That sentence is the whole positioning. This is not a distribution trying to win a general audience. It is a curated desktop whose selection criteria are stated as a list of refusals: no age or ID verification, no online accounts, no AI features, no Systemd, no forced Rust clones. The README sums the aesthetic up as "Modern Tech. 90s UI."

The base is Devuan, which the README calls "a high quality fork of Debian, which removes Systemd." So the Systemd refusal is not implemented inside LCOS; it is inherited from the distribution underneath. Anyone who has run Devuan already knows the package manager, the init system and the general shape of the system. LCOS adds a chosen desktop and a chosen set of applications on top, with stripped-down Brave Origin as the default browser.

The intended user is narrow and identifiable: someone who wants a classic desktop machine, who objects to account requirements and ID checks at the operating system level, and who is comfortable with a project whose direction is set by one person. If that description does not fit you, the README is not trying to persuade you otherwise.

How LCOS is assembled: packages, source lists and upstream-first rules

The repository is mostly documentation and package metadata rather than a giant source tree. Top-level entries include lcos-packages/, lcos-updates/, lcos-xlibre/, screenshots/ and a set of files named LCOS-02-PackageSourceList.md through LCOS-05-PackageSourceList.md. Each release has its own source list, and the README states that all source code for all packages, including the specific versions in use, is listed in PackageSourceList.md for each release.

That file naming is the most useful thing in the repository for an outsider. It means you can, for any given release, see exactly which upstream projects and which versions went into the build. For a distribution that advertises minimal deviation from upstream, a per-release source list is the artifact that lets you check the claim.

The stated policy is "Upstream First." LCOS prefers to ship vanilla versions of upstream projects, and when a fix is needed in an upstream project, the stated preference is to hire developers of that upstream project to make the change upstream rather than carry a patch. New code and new packages are written only "when there is a clear benefit in doing so." Whether that policy holds in practice is something you can only judge by reading the per-release source lists and comparing them against what the upstream projects ship.

Installing LCOS and taking a first look at the desktop

The README does not contain install instructions. It points to the Releases page as the place to get the latest release, and the repository ships screenshots of the 0.5 desktop, including a Notes view, a Games view, an Office view, a Media view and a Brave view. There is no ISO build script described in the README, no checksum list, and no written installation walkthrough in the available documentation. If you want step-by-step install instructions, the README is the wrong document and the Releases page is where you should look.

What the documentation does support is checking what is inside a release before you run it. The per-release source list is a plain file in the repository, so you can fetch it and read it directly:

bash
git clone https://github.com/BryanLunduke/LCOS.git
cd LCOS
ls LCOS-0*-PackageSourceList.md

The ls should list LCOS-02-PackageSourceList.md, LCOS-03-PackageSourceList.md, LCOS-04-PackageSourceList.md and LCOS-05-PackageSourceList.md, matching the 0.2 through 0.5 releases. Open the one for the release you intend to run and read the package list before you install anything. That is the only verification step this repository actually enables.

Once installed, the README describes a classic desktop with no online account step and no ID verification, with Brave Origin as the default browser. The screenshots show categorised application menus rather than a launcher-first interface, which is consistent with the stated 90s UI direction.

The monarchy model and what it costs you

The README states the governance model without hedging: "The Lunduke Computer Operating System is a Monarchy." It says LCOS is not a community project and that the King has total control, both technologically and organizationally. Two benefits are claimed: political activists cannot seize control as they have in other open source projects, and the project stays focused without committee distraction.

Take that at face value, because it cuts both ways. A single decision-maker can keep a project pointed in one direction for years. The same structure means there is no mechanism described in the README for resolving a disagreement with that direction, no contributor path, and no governance document that constrains the decision-maker. If your organisation has a policy about bus factor or about projects with a single maintainer, LCOS fails that policy by design, and the README is telling you so rather than hiding it.

The support channel follows the same logic. The README names the Lunduke Journal Forum as "the exclusive place to ask questions, provide suggestions, report issues, or talk with other LCOS users," and notes that the forum is available only to Lunduke Journal subscribers, explicitly to keep trolls away. So bug reports and questions have a paywall in front of them. There is no issue tracker described as an alternative route in the README.

Beta status, bugs and the upgrade question

LCOS is in Beta. The README says the system is considered "Feature Complete" for the 1.0 release but is likely to still contain potentially significant bugs. That is a candid statement and it should shape how you use it. Feature complete means the shape of the desktop is settled. Potentially significant bugs means you should not put it on a machine you depend on for work you cannot afford to lose.

The release cadence visible in the repository is fast: 0.3 on 2026-09-05, 0.4 on 2026-09-09, 0.5 on 2026-09-15. Six days between 0.4 and 0.5 is a short window for a desktop distribution. The last push to the repository was on 2026-09-15, so the project is being worked on right now rather than sitting idle.

What the README does not document is an upgrade path. There is no described procedure for moving an installed system from 0.4 to 0.5. There is an lcos-updates/ directory in the repository, which suggests update machinery exists, but the README does not explain how it is used or whether it handles release-to-release upgrades. If you install LCOS, plan on the possibility that a new release means a fresh install, and check the lcos-updates/ directory contents yourself before assuming otherwise.

Devuan as the obvious alternative, and where the difference actually lies

The most direct alternative is Devuan itself. LCOS is built on top of it, so choosing Devuan gets you the same Systemd-free Debian base without the LCOS layer. On Devuan you pick your own desktop environment, your own browser and your own application set, and you get a project with a longer history and a broader contributor base than a one-person distribution.

The practical difference is curation. Devuan gives you a base and leaves the desktop decisions to you. LCOS makes those decisions in advance: a chosen desktop, stripped-down Brave Origin as the default browser, and a stated set of exclusions around accounts, ID verification and AI features. If you would have made those same choices yourself, LCOS saves you the assembly work. If you would have made different ones, the LCOS layer is an obstacle rather than a convenience, and plain Devuan is the shorter path.

The other difference is governance, and it is not a small one. Devuan is a community project. LCOS is a monarchy by explicit design. That is a values choice as much as a technical one, and it is the cleanest way to decide between the two.

Licence, source availability and the cost of staying current

LCOS is licensed GPL-3.0, and the repository carries a LICENSE file at the top level alongside CodeOfEthics.md. The GPL-3.0 applies to the project's own code. The packages it pulls in carry their own licences, which is part of why the per-release PackageSourceList.md files matter: they are the pointer to what is actually in the image and therefore to whose licence terms apply to which component. This is not legal advice, and if you plan to redistribute LCOS or ship it inside a product, the source lists are where a lawyer would start.

The maintenance cost for a user is the release cadence plus the missing upgrade documentation. Four releases in the visible window, with the newest on 2026-09-15, means a fast-moving target. Each release has its own source list, so each release is a separate thing to evaluate. If you are the kind of user who wants to install once and apply updates for a year, this is not that project yet, and the README's Beta warning is the reason.

There is also the forum subscription. If your idea of support is filing an issue and getting a reply, LCOS requires a Lunduke Journal subscription to reach the only channel the README names. That is a recurring cost, and it is the project's stated anti-troll measure rather than an accident.

Editorial conclusion

LCOS is for people who want a Devuan-based desktop with no online accounts, no ID verification and no AI features, and who accept that a single person controls the project. It is not for anyone who needs community governance, a documented upgrade path between releases, or a support channel that does not require a Lunduke Journal subscription, because the README names the subscriber-only forum as the only place to ask questions or report issues. Before installing, verify three things: that the release you want has a matching LCOS-0x-PackageSourceList.md, that you can reach the Releases page to download it, and that you are willing to reinstall rather than upgrade, since the README describes no upgrade procedure.

Frequently asked questions

What is LCOS, the Lunduke Computer Operating System?

It is a Linux desktop system built by Bryan Lunduke, based on Devuan, with stripped-down Brave Origin as the default browser. The README states its core rules as no age or ID verification, no online accounts, no AI features and no Systemd, summarised as "Modern Tech. 90s UI."

How do I install LCOS?

The README does not include installation instructions. It directs readers to the Releases page on GitHub as the place to find the latest release, so that page is where you should look for the download and any install steps.

Does LCOS require an account or an internet connection to use?

The README states that LCOS needs no online accounts and has no ID or age verification, and that it ships with no AI features by default. It also says users are free to install whatever software they like, including AI tools, on their own machine.

Is LCOS stable enough to use as a daily driver?

The README says LCOS is in the Beta stage, considered feature complete for 1.0 but likely to still contain potentially significant bugs. Four releases appeared between 2026-09-05 and 2026-09-15, and the README does not document an upgrade path between them.

Where do I report a bug in LCOS?

The README names the Lunduke Journal Forum as the exclusive place to ask questions, report issues or talk with other LCOS users, and states the forum is available only to Lunduke Journal subscribers. No other reporting channel is described.

Official sources

  1. BryanLunduke/LCOS on GitHub
  2. Issues
  3. License: GPL-3.0
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/bryanlunduke-lcos.svg)](https://hysenlabs.com/projects/bryanlunduke-lcos)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/bryanlunduke-lcos.svg)](https://hysenlabs.com/projects/bryanlunduke-lcos)

Was this useful?