Host Homepage without installing anything
One address to remember for all your services, with tiles that show their real status instead of a plain link.
Starting at €4.99/month
Introduction
Homepage installed, updated and backed up by us, on a machine in France. A custom start page gathering all your services, with widgets, weather, search and live indicators. The front door to your self-hosted world. You install nothing and configure no server: the application is online a few minutes after you order, under your own name.
The plan that suits it is App Essentiel at €4.99/month incl. VAT — 2 GB of memory. Homepage hosts no data: it is a page, and all its work consists of asking the others. On every display it calls the programming interface of each declared service to read its status — free disk space, queue length, number of alerts — then caches the result for a few seconds. With twenty live tiles that means twenty regular outbound requests, and that is most of its consumption. The 2 GB are comfortable for a well-stocked dashboard.
There is no proprietary service to replace here, but a habit: twelve bookmarked tabs, six addresses noted in a text file, and nobody but you knowing where anything lives. Homepage gathers it all on one page, and differs from a plain list of links in one respect: its tiles display figures coming from the services themselves. Configuration happens in YAML files rather than in an interface — more austere, but a dashboard described that way can be read, version-controlled and copied to a colleague in two minutes.
What managed hosting changes
Configuration in files, not in clicks
Services, bookmarks, widgets and settings live in a few YAML files. It is text: you read it back, comment it, put it in a Git repository, and rebuild exactly the same page elsewhere. A page assembled with a mouse cannot be copied.
Tiles that read the real status
More than a hundred integrations know how to query a service and display its figures: free space on a storage service, documents processed, checks in error, what a media server is currently playing. So you see whether a service is healthy before clicking it.
The useful information around it
Clock and date, local weather, a search bar pointed at the engine of your choice, system indicators, RSS feeds. The page becomes the browser start page, the one that replaces a search engine's own.
A layout that looks like you
Groups, columns, free ordering, more than a thousand recognised service icons, light or dark theme, a custom stylesheet. A page for the family and one for the technical team look nothing alike, and that is exactly right.
Why hand it over rather than install it
Ten applications and one front door
When you host a wiki, a password manager, a photo library and three work tools, nobody remembers the addresses. A start page gathers them, and that is the link you set as the browser home page on every machine.
A page for the household
The family services, the weather, the time and the search bar. Children and grandparents have one address to know, and the tiles say at a glance whether last night's backup went well.
A team intranet front page
The useful links, the business tools, the project tracker and the documentation, arranged by group. When a new colleague arrives you hand over one address instead of writing a welcome email with twelve links.
The state of everything, on one screen
An administrator sees the checks in alert, the servers' disk space and the queues without opening each tool. This is the screen you leave up on a second monitor.
The end of scattered bookmarks
Browser bookmarks do not follow you from one machine to another and get lost with every replacement. Here they are in a file, on a server, and the same for everybody.
Hosted in France
This page lists your tools and holds the keys that talk to them: it is a map of your setup. It stays in our own datacentre in Nouvelle-Aquitaine, which we operate ourselves.
Frequently asked questions
Yes, and we may as well say so plainly: there is no graphical editor. You add a service by writing four lines in a file — a name, an address, an icon, possibly a widget. The format is simple and the project documentation gives an example for every integration, but one indentation mistake makes a whole group vanish. If you have never touched that kind of file, allow an hour the first time, then two minutes per service added.
Through their programming interface: you give the service address and a key, and Homepage asks it for its figures. That assumes the service is reachable from this instance — so available on the internet, or on the same machine. One detail worth knowing: on a managed instance, Homepage cannot discover local containers the way it would on a server of your own; you declare services one by one, which is more readable anyway.
The most important point: Homepage has no sign-in screen. It is designed to be protected upstream, and that has to be planned for, all the more so because its configuration files hold the access keys to your other services. Then, it only displays what exists elsewhere: it stores nothing, backs up nothing and controls nothing. And the widgets depend on the services' interfaces: when one of them changes its format, the tile stays silent until the next update.
App Essentiel, at €4.99/month incl. VAT. It provides 2 GB of memory where the application asks for 512 MB at minimum: the headroom serves the system, not the decor. You can change plan later without reinstalling.
Yes, they are part of the service. They matter here for a precise reason: the widgets follow the interfaces of the services they query, and staying current is what keeps the tiles showing the right figures.