Dashy

Created By
Lissy9310 months ago
Overview

What is Dashy?

Dashy is a self-hosted dashboard that helps you organize and access your self-hosted services from a single interface.

How to use Dashy?

To use Dashy, you can deploy it using Docker or from source. After setting it up, you can configure your services through a YAML file or the UI.

Key features of Dashy?

  • Support for multiple pages and sections
  • Real-time status monitoring for apps/links
  • Customizable widgets for dynamic content
  • Instant search with customizable shortcuts
  • Multi-language support
  • Optional authentication and user management
  • Cloud backup and restore feature
  • Theming options with custom CSS support

Use cases of Dashy?

  1. Creating a centralized dashboard for all your self-hosted applications.
  2. Monitoring the status of various services in real-time.
  3. Customizing the dashboard layout and appearance to fit personal preferences.
  4. Sharing access to the dashboard with multiple users with different permission levels.

FAQ from Dashy?

  • Can I deploy Dashy on any server?

Yes! Dashy can be deployed on any server that supports Docker or Node.js.

  • Is Dashy free to use?

Yes! Dashy is completely free and open-source.

  • How do I back up my configuration?

Dashy offers an optional cloud backup feature that securely stores your configuration.

Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
Lissy93
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago