Best Self Hosted Alternatives to Toby for Tabs

Homer is a dead-simple static homepage dashboard designed to keep your self-hosted services and links in one place. It is configured using a single YAML file and served by any standard web server.

Key Features

• Fully static HTML/JS dashboard driven by a YAML configuration file
• Lightweight, fast UI with low ongoing maintenance
• Fuzzy search to quickly find services and links
• Multi-page layouts and item grouping for organizing large dashboards
• Theme customization and configurable appearance
• Smart cards for richer service tiles
• Keyboard shortcuts for fast navigation and search
• Installable as a Progressive Web App (PWA)

Use Cases

• Homelab start page to centralize links to self-hosted apps and infrastructure
• Simple internal tools launcher for small teams without a backend
• Lightweight dashboard for kiosks or shared admin screens

Limitations and Considerations

• Requires being served over HTTP(S); opening the file directly via file protocol will not work
• Dynamic features (users, permissions, server-side integrations) are out of scope by design

Homer is a strong fit when you want an attractive, minimal dashboard that is easy to deploy anywhere and maintain through a simple config file. Its static approach keeps complexity low while still providing useful navigation and organization features.

Heimdall is a self-hosted dashboard for organizing and launching web applications, services, and links from a single startpage. It provides a clean tile-based UI and optional integrations that can show live information from supported apps.

Key Features

• Tile-based application launcher for web apps, services, and arbitrary links
• “Foundation” app definitions that auto-fill icons and default tile styling
• “Enhanced” apps that can query supported app APIs to display live stats (when configured)
• Built-in configurable search (including tile search and multiple search providers)
• Customization options such as backgrounds and per-tile configuration
• Multi-architecture Docker images available for common homelab deployments

Use Cases

• Homelab startpage for quick access to self-hosted services (media servers, downloaders, admin UIs)
• Team or household “service directory” dashboard for frequently used internal tools
• Lightweight homepage to replace browser bookmarks with a curated, searchable launcher

Limitations and Considerations

• Enhanced app statistics require configuring access to each app’s API and may need network/DNS adjustments in containerized setups
• By default, internal/private IP requests are blocked to reduce SSRF risk and must be explicitly enabled if needed

Heimdall is a focused, lightweight launcher that prioritizes fast navigation and organization over being a full portal. It fits especially well in homelabs where many services are spread across different hosts and ports.

LinkAce is a self-hosted web application for building a long-term, searchable archive of your favorite links. It helps individuals and teams organize bookmarks beyond browser syncing, with monitoring and sharing features.

Key Features

• Save links with automatic title and description fetching
• Organize links using tags and curated lists/collections
• Advanced search with filtering and sorting
• Multi-user support with internal sharing of links, lists, and tags
• Single sign-on support via OAuth 2.0 and OpenID Connect
• Continuous link monitoring with notifications for moved or unavailable pages
• Optional automatic archiving of links via the Internet Archive
• Public/private visibility controls and guest access options
• RSS feeds for public and private lists
• REST API for automation and integrations

Use Cases

• Personal read-later and knowledge bookmarking with reliable organization
• Team link libraries for tools, documentation, and research sources
• Creating shareable public collections with RSS feeds for updates

Limitations and Considerations

• Automatic archiving relies on an external archiving service and may not work for all sites

LinkAce is well-suited for anyone who wants a maintainable, searchable bookmark database with sharing and monitoring capabilities. Its API, RSS, and SSO options also make it a strong fit for integrating bookmarks into existing workflows.

Briefkasten is an open-source, self-hosted bookmarking application that stores bookmarks in any Prisma-compatible database. It provides a modern web UI and tools to save, organize and search bookmarks while supporting OAuth and email magic-link authentication.

Key Features

• Save bookmarks via a browser extension, drag-and-drop, or REST API
• Automatic title and description extraction when saving URLs
• Organize bookmarks by categories and tags with multiple list/views
• Import and export bookmarks in standard HTML format
• Background job to fetch bookmark images and enrich metadata
• Keyboard shortcuts and multiple UI views for fast navigation
• Full-text search across saved bookmarks
• OAuth and email magic link authentication support
• Works with any Prisma-compatible database (Postgres, MySQL, SQLite)
• Docker and docker-compose support for easy local deployment

Use Cases

• Personal bookmark vault for managing links, articles and resources across devices
• Team or small-group shared collection of reference links and documentation
• Migrating and consolidating bookmarks from browser exports into a searchable database

Limitations and Considerations

• The project provides a v2 beta; the maintainer has warned that beta database instances may be reset during migration from v1 to v2
• Image storage is not built into the database; an external object store (S3-compatible or provider SDK) is recommended for bookmark images
• OAuth requires configuring provider credentials; initial setup requires a Prisma-compatible database and appropriate environment variables

Briefkasten is a straightforward, developer-friendly bookmarking solution focused on portability, searchability and extensibility. It is suitable for individuals and small teams who prefer a self-hosted bookmark manager with integrations for modern deployment workflows.

Fenrus is a self-hosted personal homepage/new tab dashboard designed to provide fast access to your apps, services, and links. It supports organizing content into dashboards and groups, and can enrich entries with additional app-specific information.

Key Features

• Custom dashboards with groups containing links, apps, and nested dashboards
• Multiple item types: simple links, basic apps, and “smart” apps with richer metadata and status details
• Built-in user system with registration and an admin role for user management
• Search engine shortcuts with configurable query templates and icons
• Automatic favicon fetching when an icon is not provided
• Designed to run via Docker or as a .NET application, with persisted configuration stored on disk

Use Cases

• Personal homelab startpage to centralize access to self-hosted services
• Household or small team dashboard with multiple user accounts
• Unified landing page with quick links plus lightweight status context for common apps

Limitations and Considerations

• Some advanced functionality (for example terminals/logs/SSH and uptime recording) may require additional permissions and careful security configuration, especially behind a reverse proxy

Fenrus is a practical choice for users who want a clean, customizable portal for their apps without depending on a third-party startpage service. It is flexible enough for simple link collections while also supporting richer, app-aware widgets where available.

NeonLink is a minimal, open-source self-hosted bookmark manager that provides a private dashboard for saving and organizing links. It combines a React frontend with a Node.js backend and stores data in SQLite to keep resource usage low and installation straightforward.

Key Features

• Tag-based bookmarking with a dashboard UI for quick access and organization
• Full-text search across saved links
• Automatic extraction of title, description and favicon for saved URLs
• Customizable background and lightweight, minimal-dependency design
• Docker and docker-compose support with multi-arch builds optimized for Raspberry Pi

Use Cases

• Personal bookmark collection and startpage on a Raspberry Pi or small VPS
• Private curated link dashboard for teams or individuals without external services
• Lightweight alternative to cloud bookmark managers where simplicity and privacy are priorities

Limitations and Considerations

• Uses SQLite as the primary datastore, which is suitable for single-user or small deployments but not ideal for high-concurrency or very large datasets
• Lacks built-in enterprise authentication or advanced multi-tenant features; additional integration is required for SSO or team management

NeonLink is well-suited for users who want a compact, easy-to-run bookmark service with basic organization and search features. It favors simplicity and low resource requirements over advanced scalability or enterprise functionality.

Dashwise is an all-in-one homelab dashboard that centralizes links, widgets and small integrations. It pairs a Next.js frontend with a PocketBase backend to provide per-user JSON configs, GUI editing and a modular dashboard layout.

Key Features

• GUI-based management for links, search engines, wallpapers and settings
• Built-in authentication via PocketBase with optional OIDC SSO support
• Link management with Link Groups and optional HTTP-based uptime monitoring and downtime logging
• Modular widgets and "glanceables" that can be moved and customized per user
• Spotlight-like quick search (Ctrl+K) with support for bangs and indexed search items
• Wallpaper upload and default wallpaper customization for new users
• Docker Compose deployment with an optional jobs container for background indexing and monitoring tasks
• Integration hooks for self-hosted apps (limited integrations available initially)

Use Cases

• A personal or homelab startpage to centralize service links, quick actions and system glanceables
• Lightweight uptime checks and quick visibility for frequently used self-hosted services
• Shared dashboard for small teams to store and organize links, search shortcuts and widgets

Limitations and Considerations

• Project is under active development; some planned integrations and widget types are not yet implemented
• Backend depends on PocketBase (SQLite) which may limit scalability for very large multi-user deployments
• Link monitoring is basic (HTTP GET checks) and not a full-featured monitoring/alerting system

Dashwise is focused on a clean, configurable startpage experience for self-hosters who want a GUI-managed dashboard with lightweight monitoring and integration points. It is suited for personal and small-team usage where simplicity and local control are priorities.

TraLa is a simple, modern dashboard that automatically discovers HTTP routers from a Traefik instance and presents them in a responsive service grid. It focuses on providing a clean landing page for self-hosted services with minimal configuration.

Key Features

• Auto-discovery of HTTP routers via the Traefik API and automatic population of the dashboard
• Icon auto-detection for services using an external icon repository and optional local icon overrides
• Smart grouping of services based on tags with configurable grouping thresholds and column layout
• Full configuration via a YAML file with environment variable overrides for runtime settings
• Manual service entries and service exclusion rules (wildcard support) for fine-grained control
• Live search and sorting of services, plus display overrides for custom names and priorities
• Lightweight, multi-architecture Docker image intended for simple deployment alongside Traefik
• Multi-language frontend and theming that follows OS light/dark preferences

Use Cases

• Provide a unified home/landing page for a home lab or self-hosted environment exposing services through Traefik
• Quickly access and organize running services discovered by a Traefik reverse proxy
• Create a curated service catalog for household or small-team deployments with custom icons and grouping

Limitations and Considerations

• Requires the Traefik API to be reachable and configured (may need API exposure or proper credentials)
• Only discovers HTTP routers; non-HTTP services or custom Traefik configurations may not appear
• Icon detection relies on an external icon source unless icons are provided locally via configuration
• Not a monitoring or alerting tool — it is intended as a navigational/overview dashboard, not for metrics or health checks

TraLa is a lightweight, practical dashboard for users running Traefik who want an organized, customizable service landing page. It emphasizes automation with easy overrides so you can keep default behavior or tailor the display to your needs.

Homarr iFrames is a small Go-based API that generates embeddable HTML iFrames for a variety of self-hosted applications so they can be displayed inside dashboards (not limited to Homarr). The API exposes per-source routes that produce HTML iFrames and accepts query parameters to control output and reload behavior. (github.com)

Key Features

• Generates embeddable iFrame endpoints for many sources (examples: Linkwarden, Vikunja).
• Per-source query parameters (limit, collectionId, theme, auto-reload) to customize the returned HTML.
• Built-in API documentation served via Swagger at /v1/swagger/index.html.
• Distributed as a Docker image and includes a Dockerfile and docker-compose example; default container port is 8080.
• Simple, dependency-light Go implementation suitable for running behind a reverse proxy. (github.com)

Use Cases

• Embed bookmarks, task lists or other self-hosted app views inside a Homarr or custom dashboard.
• Provide lightweight, customizable HTML widgets for private dashboards without modifying the upstream apps.
• Combine multiple service-specific iFrames into a single dashboard page for consolidated monitoring. (github.com)

Limitations and Considerations

• No built-in authentication or access control: any client that can reach the API can request iFrame content; run behind an auth/reverse-proxy (e.g., Authelia/Authentik) or restrict network access. (github.com)
• iFrame behavior depends on the browser and the target app (mixed HTTP/HTTPS contexts or apps sending X-Frame-Options may block embedding).
• Feature set is focused on producing and customizing HTML iFrames rather than acting as a full integration layer (some sources may require specific environment variables). (github.com)

Homarr iFrames is a compact, practical solution for exposing many self-hosted app views as embeddable iFrames for dashboards. It is implemented in Go and intended to be run in containers or directly with minimal dependencies. (github.com)

gobookmarks is a self-hosted personal landing page / start page that renders bookmarks stored in a simple plaintext file you control. It provides both a visual editor and a full-text editor, maintains history using Git-like providers, and supports multiple authentication methods.

Key Features

• Renders a multi-tab, multi-page start page from a human-editable plaintext bookmark file with columns, pages, tabs, and categories
• Visual drag-and-drop editor plus a full-text editor for bulk updates and versioned changes
• Git-backed history and providers (local Git, GitHub, GitLab) as well as an SQL provider for persistent storage
• Search with keyboard navigation and configurable search widgets; keyboard shortcuts for fast navigation
• Multiple authentication options including database, local Git, and OAuth providers (GitHub, GitLab)
• Docker image, precompiled binaries, and service files for system integration; configurable via environment variables or JSON config
• Favicon caching and configurable cache/storage paths

Use Cases

• Personal start page for quickly accessing regularly used sites, developer tools, and dashboards
• Shared team curated bookmark repository where changes are tracked and can be rolled back
• Lightweight home portal for homelabs or small teams that prefer plaintext data with Git-backed history

Limitations and Considerations

• Bookmarks are stored in a custom plaintext format which has a small learning curve for advanced layouts and widgets
• Search scope is limited to the current tab context by design (not a global site-wide index)
• OAuth providers require appropriate client credentials and configuration for third-party login

gobookmarks is focused on simplicity, history and portability: your bookmarks remain plain text and can be edited directly or via the provided UI, with storage and history handled by Git or SQL providers.

SyncMarks is a web application that acts as the backend for the SyncMarks browser extension, providing a central hub to manage and sync bookmarks across multiple browsers. It can also be used independently as a standalone website to manage bookmarks without installing any extension.

Key Features

• Central backend for cross-browser bookmark synchronization using the SyncMarks extension
• Web interface to add, edit, delete, move, and reorganize bookmarks
• Works with browsers that support WebExtensions and the Bookmark API
• Can be used as a standalone bookmark manager in a browser, independent of the extension
• Supports community translation workflows (e.g., via Weblate) for multi-language UI

Use Cases

• Synchronize bookmarks between different browsers (for example, Firefox and Edge)
• Run a personal or family bookmark hub across multiple devices
• Manage and reorganize bookmarks through a web UI even when an extension is not available

SyncMarks is well-suited for users who want control over their bookmark data and need a practical way to keep bookmarks consistent across browsers. By combining an extension-based sync workflow with a standalone web app, it supports both automated syncing and manual bookmark management.