A smooth first run matters: stillOS aims to make it painless
A confusing 30‑minute setup multiplied across thousands of endpoints becomes a payroll line, not a product feature. stillOS is a new Linux distribution built around that problem: reduce friction for non‑technical users during first use, and make updates less of a trap for IT.
“We got annoyed with Windows making us the product, and Linux being too complicated. So we made stillOS. We believe stillOS is the first truly consumer ready Linux distribution. Thanks to atomic updates, stillOS is able to stay as stable as a rock while still bringing you new features. App and OS updates are automatic, so there’s no need to worry about keeping your OS and apps up to date.”
, stillOS website
In a ZDNET review the distro was described as “aimed at consumers, ” said to “make it incredibly easy to start using Linux, ” and called “one of the best Linux onboarding experiences” the reviewer had seen (ZDNET reviewer). The praise is strong, but the same review also flags stability and UX issues that matter for enterprise adoption.
Priority gaps: the issues IT should know first
- Layout switching can break sessions. The reviewer reports repeated logouts, required reboots, and at least one case where they could not log back in without rebooting. After several layout switches the desktop became unresponsive and needed a hard reboot.
- Atomic updates are claimed but not documented. stillOS advertises background, atomic updates that apply on reboot; the reviewer observed this behavior but the underlying implementation (ostree/rpm-ostree/transactional-update/Nix/custom) is not specified. Without documentation, teams cannot verify rollback guarantees, signed updates, or auditability.
- Migration guidance and app compatibility are thin. The installer groups apps by category (including an LLMs category), but it’s unclear whether listed tools are native packages, PWAs, web shortcuts, or links to cloud services. That ambiguity matters when you must support Windows‑dependent workflows.
- Vendor and legal details are missing. The review does not confirm licensing, closed‑source components, firmware blobs, or any OEM preinstall partnerships. Those are essential for compliance and procurement decisions.
What stillOS gets right right now
- Familiar desktop by default. It uses GNOME under the hood but configures panels, icons, and a system tray to feel recognizable to Windows users, which reduces training overhead.
- Centralized onboarding (First Steps app). Users can pick apps by category, choose a layout, configure displays and devices, connect online accounts, and join the stillHQ community, all from one place.
- App selection organized for newcomers. Installer categories include web, productivity, music, creative, gaming, utilities, and an LLMs category. The review lists productivity names shown during setup (OnlyOffice, LibreOffice, Planify, Todoist, Trello, monday.com, ClickUp, HubSpot) but does not clarify packaging types (native installer vs. PWA vs. cloud link).
- Background, atomic-style updates. The distro applies updates in the background and activates them on reboot, which, if implemented with a reliable transactional backend and rollback, reduces partial‑upgrade breakage for non‑technical users.
How to evaluate stillOS for pilots and deployments
Don’t treat the ZDNET review as a final verdict. Treat it as a single, useful data point. If you’re responsible for procurement or endpoint strategy, run a short, focused pilot and ask for documentation up front.
- Pilot size & length. Start with 25-50 non‑critical endpoints for 4-6 weeks. That’s large enough to surface hardware compatibility and helpdesk trends but small enough to contain risk.
- Test acceptance criteria. Example goals: under 5 new helpdesk tickets per 100 pilot users per week tied to OS issues; atomic update rollback success rate 100% in test runs; layout‑switch operations complete without need for hard reboots.
- Scripted tests to run. Switch layouts repeatedly, apply updates and reboot, simulate interrupted updates, and validate peripherals (printers, Bluetooth). Test any included LLM tools for whether they run locally, require cloud connectors, or simply provision shortcuts.
- Ask for these documents. Update backend (which transactional system is used), rollback procedure and recovery time, signed update model, list of included LLMs and AI tools (names and versions), MDM/fleet management integration options, and a full licensing list for shipped binaries and any closed‑source components.
Practical IT checklist: questions to bring to stillOS or your vendor
- Which atomic‑update backend does stillOS use (ostree/rpm‑ostree/transactional‑update/Nix/custom)? Provide docs.
- Exactly how do rollbacks work and how long do they take in a real recovery scenario?
- Are updates signed and auditable? Is there an update log/manifest you can verify?
- What MDM, fleet management, or config‑management tools are supported (e.g., Ansible, Salt, JumpCloud, proprietary MDMs)?
- Which LLMs and AI tools are included by name, version, and delivery method (local binary, container, cloud connector, or PWA)?
- Provide a complete licensing and third‑party components list, including firmware and proprietary drivers.
- Are there announced OEM partnerships or a hardware compatibility matrix? If not, what validation testing has been run on mainstream consumer hardware?
- What security hardening is present out of the box (AppArmor/SELinux, secure boot, disk encryption defaults)?
Why this matters to business leaders
Onboarding is an operational cost. Lowering it affects training budgets, helpdesk load, and rollout time. Atomic updates that truly allow safe, fast updates with instant rollback reduce risk exposure at scale, but only if the implementation is transparent and tested.
stillOS combines sensible choices, a recognizable UI, a single onboarding app, categorized app selection (including an LLM category), and background updates, into a package that eliminates many early annoyances. That combination is precisely the kind of user experience enterprise deployments need. The open questions and reported bugs, however, are operational blockers until proven fixed and documented.
Three clear next steps
- Pilot deliberately. Deploy to 25-50 non‑critical endpoints for 4-6 weeks with scripted tests that exercise layout switching, updates, rollback, peripherals, and any included LLM tooling.
- Demand documentation. Require written answers to the checklist above (update backend, rollback procedure and timing, signed updates, MDM support, LLM list, licensing, security defaults, hardware compatibility).
- Set acceptance criteria. Define measurable thresholds for helpdesk tickets, rollback success, and session stability before wider rollout.
Key questions: quick answers
- Is stillOS easy for new users?
The ZDNET reviewer found the onboarding flow intuitive and called it “one of the best Linux onboarding experiences” they’d seen. The First Steps app centralizes setup actions so non‑technical users can pick apps, layouts, and devices without terminal work.
- Does stillOS use atomic updates?
stillOS advertises background, atomic updates that apply on reboot (stillOS website). The reviewer observed atomic‑style behavior, but the underlying update technology and rollback guarantees were not documented in the review, verify with the project.
- Can I customize the desktop without Linux skills?
Yes. The First Steps app exposes layout presets (Windows‑like, macOS, GNOME, elementaryOS‑like, ChromeOS‑like) and GNOME extensions so users can change appearance and behavior without CLI knowledge.
- Are there stability problems to worry about?
The reviewer reported layout switching that sometimes required repeated reboots and a case where the desktop became unresponsive and needed a hard reboot. These are material issues to test in a pilot.
- Does stillOS include LLM tools out of the box?
The installer shows an LLMs category during app selection, but the review does not list specific LLM packages or whether the tools are local binaries, containers, cloud connectors, or PWAs. Confirm exact titles and delivery methods.
- Is stillOS ready to be preinstalled on consumer PCs?
The design is close to “consumer‑ready, ” but as of the review there were no confirmed OEM preinstall partnerships or published hardware certification lists. That needs confirmation before OEM deployment.
- Is stillOS fully open source?
The review does not specify licensing details or the presence of closed‑source components. Ask for a complete licensing manifest and third‑party components list before commercial use.
Bottom line
stillOS delivers a thoughtful onboarding experience that addresses the most costly part of an OS switch: first run and configuration. The combination of a familiar UI, a central First Steps app, categorized app selection (including an LLMs category), and background updates is rare and valuable for mainstream users.
However, reported stability issues around layout switching, the lack of published details about the update backend and rollback mechanics, and missing licensing/OEM information mean IT teams should treat stillOS as a pilot candidate today, not a ready drop‑in replacement for mass endpoint fleets. Recommended next action: run a disciplined pilot, demand the update and security documentation listed above, and only expand once acceptance criteria are met.