English
Homarr Hosting
Create an application dashboard with service integrations, widgets, and customizable layouts.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Official links
Homarr’s official links and original website
Homarr Website
More
Tech
- Docker image
- ghcr.io/homarr-labs/homarr:latest
- Default port
- 7575
How Homarr works
Homarr calls each dashboard a board. Administrators arrange links, text, icons, dynamic sections, and supported widgets on responsive layouts, then decide which users or groups may view or modify each board. A home board can be selected for individuals, groups, mobile devices, or anonymous visitors when the board is explicitly public.
Integrations connect Homarr to third-party applications so widgets can display service information. Each integration needs its own address, credentials, certificate trust, and permissions. The hosted Homarr instance does not discover or include other applications automatically; it provides the dashboard surface into which authorised external services can be connected.
Key Homarr features
On first launch, Homarr presents onboarding and asks the operator to create the first administrator. That account has full control and cannot be deleted, so the onboarding step must be completed by the intended owner promptly. The catalogue persists /appdata, including the server state needed for boards, users, groups, integrations, and encrypted configuration.
User groups can govern board visibility and modification rights, and boards can be duplicated, assigned as home views, or published deliberately. Some integrations need host-level sockets, agents, API keys, or access to private services. The catalogue does not mount a Docker control socket or bundle third-party credentials, which limits widgets that depend on those connections.
Who uses Homarr
Home-lab operators create a launch page for storage, media, monitoring, and automation services. Support or operations teams build role-specific boards for common systems, while families can publish a simplified board with selected links and information.
Homarr is not a monitoring backend, identity provider, service discovery system, or replacement for the applications shown on a board. A widget can only display what its integration and credentials allow, and a public board should be reviewed for sensitive URLs, names, or status data.
Self-hosting Homarr: requirements and cost
Homarr resource use grows with board count, widgets, refresh intervals, integrations, users, groups, concurrent viewers, icons, and imported dashboard data. PostgreSQL and MariaDB are Not required by the catalogue template; Homarr persists its own state in /appdata. Homarr itself does not add a separate software subscription, while high-frequency widgets and many concurrent boards can generate more application and third-party API activity.
On AvaHost, Homarr uses Plan 1 at €2. The hosted Homarr package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The intended owner must create the first administrator through onboarding. Docker sockets, remote service credentials, integration agents, external identity providers, third-party applications, and permission design for public boards are not bundled with the standard deployment.
F.A.Q
Homarr starts at €2 on Plan 1. A small set of boards, links, and moderate-refresh widgets fits that entry plan. Board count, integration volume, refresh frequency, concurrent viewers, imported assets, users, and groups are the main indicators for deciding whether more application capacity is appropriate.
The first visitor receives Homarr’s onboarding flow and must create the initial administrator account. That user has full control and cannot be deleted, so the intended owner should complete onboarding promptly through the final HTTPS address. Do not share the fresh deployment publicly before this account and basic board permissions have been reviewed.
A custom domain can point to Homarr, with automated HTTPS protecting browser sessions. Board visibility remains an application setting: a public board can be viewed without login, while restricted boards depend on users and groups. Review every widget, link, service name, and integration before publishing a board to anonymous visitors.
No. AvaHost applies Homarr updates automatically and includes scheduled backups for its persistent state, but each external service integration still needs its own address, credentials, trust settings, and permissions. Docker control sockets, agents, API keys, and third-party applications are not supplied. Re-test important widgets after Homarr or a connected service changes.