English
Flame Hosting
Organize applications and bookmarks on a fast, minimal home page for your server.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Official links
Flame’s official links and original website
Flame Website
More
Tech
- Docker image
- pawelmalak/flame:latest
- Default port
- 5005
How Flame works
Flame displays applications and bookmarks on a configurable start page. Users can group entries, assign icons and descriptions, select a search provider, change appearance, and edit the page through the application interface rather than maintaining a separate YAML repository. The persistent /app/data volume retains Flame’s configured entries and settings.
The catalogue generates one password and passes it to Flame. Upstream authentication separates editing from viewing: the password unlocks settings and management, while public applications and bookmarks can still be visible to visitors who open the page. Hidden items can be reserved for an authenticated session, but operators need to classify entries correctly before sharing the hostname.
Key Flame features
Built-in editors make Flame approachable for a small collection without a code-based configuration workflow. Search, themes, custom CSS, icons, categories, and link ordering help shape the page. Docker integration exists upstream, but the catalogue does not provide a Docker socket or access to the underlying hosting environment, so automatic discovery should not be expected from this package.
The edit password is not single sign-on for destination services and does not make a visible bookmark private. Every linked system must protect itself, and any sensitive administrative URL should be marked hidden or omitted. Flame is also not a monitoring system, password vault, inventory, secrets store, or permission broker.
Who uses Flame
Individuals create a browser home page, households share links to common services, and small teams group approved tools by category. Flame is especially useful when the owner wants to edit entries through a web interface instead of changing configuration files.
Flame works best as a launch page rather than a governance platform. Organisations needing per-user roles, approval workflows, identity-provider integration, usage auditing, service ownership records, or a fully private portal should assess a system designed for those controls.
Self-hosting Flame: requirements and cost
Flame resource use is driven by visitor count, entry count, icons, themes, search use, and configuration changes. PostgreSQL and MariaDB are Not required; /app/data stores the persistent start-page state. The software adds no separate application fee, and a small dashboard normally consumes few resources compared with the services to which it links.
On AvaHost, Flame uses Plan 1 at €2. The hosted Flame package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The package generates a password for editing and persists application data. Visitors can still view public entries without that password. Docker discovery, single sign-on, linked-service accounts, per-user roles, service monitoring, and a private network boundary are not bundled.
F.A.Q
Flame starts at €2 on Plan 1. The starting plan is appropriate for a small launch page with light traffic. Visitor count, icons, custom assets, entry count, search requests, and frequent configuration changes influence usage. The external applications opened from Flame and their accounts are not included in this price.
A custom domain can be connected to Flame, with automated HTTPS supplied after DNS is configured. Update browser home-page settings and shared bookmarks to the final hostname. Before distributing it, test public and hidden entries, the settings password, search, icons, and every destination to ensure the page exposes only the links intended for that audience.
The catalogue-generated password unlocks editing and settings. It does not automatically hide the entire start page: visitors may view entries marked public without signing in. Use hidden entries for material intended only for the authenticated editor, avoid displaying sensitive administrative URLs, and keep separate authentication enabled on every linked service.
Flame supports Docker-related features upstream, but this catalogue deployment does not provide a Docker socket or access to the underlying hosting environment. Add applications and bookmarks through the built-in editor instead. Automatic updates and scheduled backups cover Flame’s persistent data, not the availability, configuration, or credentials of the services listed on the page.