01 / hero

A light panel
that reaches
anything you run

Star on GitHub [ Scroll ]

02 / one binary, live

  • system-statscore
  • disk-spaceoptional
  • hello-widgetexample
  • dashboard.jsonflat file
  • go · python · node · rust · bashany language
  • no database0

03 / who we are

Star Panel is a lightweight, open source panel for Linux servers — lightning fast by default, able to reach whatever you need.

Plugin backends are language-agnostic: Go, Python, Node, Rust, Bash — if it runs on your machine, it can be a widget. One Go binary serves it all over plain REST, with no database to slow it down.

04 / the problem

Panels
shouldn't be your
server's heaviest
process

Panels make your server visible, but they're often heavier than what they monitor. Databases, auth servers, workers and a Node runtime in prod — just to show CPU and disk.

They're not the essence of what you run, but they're necessary to see it. Star Panel stays a single process so the instrument never outweighs the machine.

05 / star panel's impact

We sit between your server and everything it has to report

Part of your setup's value is knowing CPU, memory, disks and containers at a glance. Star Panel builds that layer, serves it, and stays out of the way.

Your serverlinux
CPUpoll 10s
Memorypoll 10s
Diskdry-run clean
Themescss file
  1. 01

    Lightweight,
    lightning fast

    One Go binary serves dashboard + API. Flat JSON, plain REST polling, no database — the instrument never outweighs the machine.

  2. 02

    Language-agnostic
    plugins

    A plugin is a folder with a manifest. Its backend can be written in whatever you need — supervised locally, proxied safely.

  3. 03

    Reach whatever
    you need

    CPU today, containers tomorrow. Drop a folder, get widgets. A plugin that lacks something says so instead of demanding root.

06 / why owners install it

Reason 1

Heavy panels on small machines

A homelab box asks whether it can show CPU without running a database. The answer slows down while Docker pulls images nobody planned for.

Reason 2

Config scattered everywhere

Constant context shifting across exporters, sidecars and YAML — on top of running the services only you can run. Shift the view to one file.

Reason 3

One more disk to watch

Serving more of your lab means saying yes to the next mount, then the one after it. Drop a folder, get a widget, keep it running.

07 / who it's for

We primarily work for homelabs and small teams running Linux. One dashboard file so your setup stays yours.

homelab · self-hosters · small teams · bare metal · vps · raspberry pi

08 / what the repo says

No claims.
Just files.

"If it reports the wrong disk, we'd rather report none."

— disk-space plugin readme

"Every plan answers as a dry run first."

— adr-0010

"A plugin that fails never breaks the dashboard."

— plugin contract tests

09 / quickstart

Running in
two minutes.

requires — go 1.27+ · node + pnpm for front dev only

10 / talk to us

Let's see
your server.

Star the repo Open an issue