If you're a parent running Linux at home, you've probably discovered that parental control options are surprisingly limited. The mainstream parental control tools — Bark, Qustodio, Net Nanny — have weak or non-existent Linux support. The open-source options are often incomplete, poorly documented, or require installing software that your child can easily disable.

I'm a technologist and parent. I run Ubuntu at home, and my kids have their own Linux machines. I've tried every Linux-compatible parental control solution I could find, and I built Leassh because none of them actually solved the problem: understanding what your child is doing on their computer without installing spyware.

Here's what actually works for Linux screen time monitoring in 2026.

The Linux parental control problem

Most parental control software is designed for Windows and macOS first, with Linux as an afterthought. Here's what I found when researching Linux options:

The gap: Linux parents have two choices: no monitoring at all, or installing software that requires root access and can be disabled by tech-savvy kids. Neither option is acceptable.

What actually works on Linux

1. SSH-based monitoring (Leassh's approach)

Here's the key insight: Linux already has a built-in remote monitoring protocol — SSH. Every Ubuntu, Fedora, Debian, and most other Linux distributions have SSH enabled by default or can enable it with one command:

sudo apt install openssh-server
sudo systemctl enable --now ssh

Once SSH is enabled, you can monitor what's running on the system without installing anything. The Linux process table (ps) tells you exactly which applications were running, when, and for how long. SSH lets you query this remotely without touching the user session.

Leassh uses this approach. It connects to your child's Linux machine via SSH, queries the process history, and tells you what they were doing — not just how long they were on the computer.

2. Native Linux tools (for DIY parents)

If you want to roll your own solution, here are some options:

# View current processes
ps aux

# View process history (requires auditd)
sudo ausearch -c firefox

# Monitor command execution (requires auditd)
sudo auditctl -a exit,always -F arch=b64 -S execve

These tools work, but they require significant setup and ongoing maintenance. They also only give you raw data — no narrative reports, no weekly summaries, no insight into what your child was actually building or learning.

Why commercial parental controls fail on Linux

Let's be honest about why the big parental control companies don't support Linux well:

  1. Market size: Linux desktop market share is still small (maybe 3-4% of home desktops). Their ROI calculation doesn't justify heavy Linux development.
  2. Installation friction: Most commercial tools require installing a persistent agent with root privileges. On Linux, this is more visible and more easily removed than on Windows or macOS.
  3. Fragmentation: Linux distributions vary wildly in their package managers, desktop environments, and system architectures. What works on Ubuntu might not work on Fedora or Arch.

The result: Linux parents are left with subpar options or forced to use Windows/macOS-focused tools that don't work on their primary computing platform.

Leassh for Linux: The practical solution

Leassh is designed with Linux first. Here's how it works:

Setup (takes 5 minutes)

  1. Enable SSH on your child's Linux machine (if not already enabled)
  2. Create a dedicated monitoring user (or use an existing one)
  3. Add the SSH credentials to Leassh configuration
  4. Done
# Example: Create a monitoring user (optional)
sudo adduser leassh-monitor
sudo usermod -aG sudo leassh-monitor

# Enable SSH
sudo apt install openssh-server
sudo systemctl enable --now ssh

# Get the machine's IP address
hostname -I

What you get

Technical details for the curious

For parents who want to understand exactly how this works under the hood:

Process history collection

Linux tracks process information in several places:

Leassh queries /proc and uses ps history to build a timeline of what was running. It doesn't rely on shell history (which is easily manipulated) — it looks at what the OS actually executed.

Privacy considerations

SSH-based monitoring is inherently more private than agent-based monitoring because:

Common questions

What if my kid disables SSH?

This is a legitimate concern. However:

With SSH-based monitoring, the relationship is different. You're not installing "spyware" — you're using a standard system protocol to query process information. It's transparent and can be discussed openly with your child.

Does this work for multiple machines?

Yes. Leassh is designed for fleets of machines. You can monitor:

All data is aggregated into a single dashboard with activity timelines and weekly summaries.

What about Wayland vs X11?

SSH-based monitoring doesn't care about the display server. It queries process information at the OS level, which is independent of whether you're using Wayland, X11, or anything else.

Linux distributions tested

Leassh works on any Linux distribution with SSH available. Specifically tested on:

If your distribution has SSH available, Leassh should work out of the box.

The homelab angle

For parents who run homelabs (and many Linux parents do), Leassh has a bonus: it's essentially the same technology used for server monitoring. You can:

This is why Leassh's original design focused on fleet monitoring — the same SSH-based approach that works for monitoring 50 servers also works for monitoring 5 family machines.

Alternative approaches (and why they fail)

Screen capture

Tools like xvfb or screen capture scripts can take screenshots, but:

Network monitoring

Tools like Wireshark can monitor network traffic, but:

Parental control packages

Open-source options like parental or timekpr exist, but:

What I'd actually recommend

If you're a Linux parent:

  1. Enable SSH on all machines you want to monitor (usually already enabled on Ubuntu/Fedora)
  2. Use Leassh for process monitoring and behavioral insights
  3. Discuss the monitoring openly with your child — SSH-based monitoring is transparent and can be part of a conversation about digital responsibility
  4. Focus on understanding rather than restriction — the goal is to know what your child is learning and building, not just to limit time

The honest truth: Linux parental controls exist, but most are time-limit tools that don't tell you what your child was doing. If you want to understand rather than restrict, and you want a solution that doesn't require installing spyware, Leassh's SSH-based approach is the only practical option I've found.

Conclusion

Linux parents deserve better than "no monitoring" or "install this agent that your child can disable." SSH-based monitoring offers a third option: transparent, privacy-first, technically sound monitoring that respects both the parent's need for insight and the child's right to privacy.

The technology exists. It's been part of Linux since the 1990s. It just needed someone to build a user-friendly interface around it.

Further reading: How to Monitor Your Child's Computer Without Installing Spyware — the case for SSH-based monitoring. And Why SSH Monitoring Beats Consumer Apps for Family Technology — why the SSH approach is technically superior to agent-based monitoring.

Ivar Nielsen is a revenue strategist at Leassh with expertise in open-source technology and Linux systems. He helps technical families understand how to monitor their children's computer use without compromising privacy or installing spyware.