# FiestaBoard v10: a self-hosted dashboard for Vestaboard and Pixoo 64 — retained record

> Retained reddit record from reddit:selfhosted.

Canonical: https://highsignal.app/data/records/e45c7dd062eb8866

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:selfhosted)  published 2026-10-28 17:41 ingested 2026-10-29 02:39

[original source ↗](https://www.reddit.com/r/selfhosted/comments/1xhuyqm/fiestaboard_v10_a_selfhosted_dashboard_for/)

## retained text



```
I maintain [FiestaBoard](http://www.fiestaboard.app), a free, MIT-licensed app for putting information from your services onto a physical display. It runs in Docker on your own host, or on a separate Raspberry Pi using the FiestaPi image. Nothing gets installed inside the display.

It supports Vestaboard Flagship, Note and Note arrays, plus Divoom Pixoo 64. You use a browser to connect a display, build pages and schedule what appears. Calendar events, now-playing information and Home Assistant entities are a few of the things it can show.

v10 adds pixel canvases and an output-plugin architecture for different display hardware. Recent work also adds authorization flows for services including Spotify, Plex, Home Assistant, GitHub, Todoist and Google Calendar and Tasks. Some integrations still require your own developer app. Spotify requires Premium and your own Spotify app.

The UI now does less unnecessary work while idle, and heavy editor components load only when needed. Plugin installation and updates also run off the main event loop. These are software changes, not a claim that the physical display moves faster.

If you run a physical display from your self-hosted setup, where does configuring it get awkward?

Source and setup: [https://github.com/Fiestaboard/FiestaBoard](https://github.com/Fiestaboard/FiestaBoard)
```



document fetched 2026-10-29 00:30 · canonical https://reddit.com/r/selfhosted/comments/1xhuyqm/fiestaboard_v10_a_selfhosted_dashboard_for
