TiloBox
Back to directory
Homer project preview
ProductivityAlternative to FlameAlternative to HeimdallAlternative to Dashy

Homer

A very simple static HOMepage for your servER to keep your services on hand.

View on GitHub
LicenseApache-2.0
GitHub stars9.5k
Last commit1 weeks ago
Tags6 topics
Yaml ConfigDashboardStatic SiteSelf HostedVuejsHomelab
Overview

Why consider Homer?

Homer is a dead-simple static homepage dashboard for homelab servers. Configured via a single YAML file, it serves offline with search filters, category tags, dark mode, and zero backend databases.

Guided learning

Learn Homer by building

Practical setup notes, real use cases, and copy-ready examples in one focused guide.

1 min read 2 sections
In this guide2 sections

Overview of Homer

Homer offers instant loading times by serving a pre-rendered Vue.js single-page application directly from Nginx.

Running with Docker

bash
1docker run -d \
2 --name homer \
3 -p 8080:8080 \
4 -v $(pwd)/assets:/www/assets \
5 b4bz/homer:latest

Homer is licensed under the Apache License Version 2.0.

Related tools

More options with a similar category or technology profile.

McFly logo

McFly

Fly through your shell history with an intelligent neural network search engine.

cheat logo

cheat

Interactive command-line cheatsheets for system administrators and software engineers.

Pipenv logo

Pipenv

Python development workflow for humans uniting Pipfile, pip, and virtualenv.

Rye logo

Rye

Comprehensive Python package and workspace management tool written in Rust.

Homer FAQs

Homer is listed as a Productivity tool on TiloBox. Review the overview, features, and official documentation on this page to decide whether it solves your specific workflow.

Start with the project's GitHub repository for supported installation and deployment instructions. Test the setup with representative data or a small project before rolling it out more widely.

Homer is listed under the Apache-2.0 license. Read the complete license text and the project's notices before using, modifying, or distributing the software.

Production readiness depends on your requirements. Review maintenance activity, security practices, documentation, backup and upgrade procedures, and compatibility with your stack; then validate it in a non-production environment.

Homer is listed as an alternative to Flame. Compare the core workflow, deployment model, integrations, and licensing against your must-have requirements before switching.