Metabase is an open-source business intelligence platform that enables users to query, visualize, and share data through an intuitive interface. The system is built as a full-stack application with a Clojure backend and React/TypeScript frontend, supporting both self-hosted and cloud deployments. The architecture follows a modular monolith pattern with clear separation between the core application, enterprise features, and embedding SDK components. The codebase demonstrates sophisticated engineering practices including a comprehensive plugin system that allows enterprise features to extend core functionality, a custom query builder with both GUI and SQL interfaces, and a robust embedding SDK for integrating Metabase components into external applications. The frontend utilizes modern React patterns with Redux for state management, while the backend employs Clojure's functional programming strengths for data processing and API handling. Key architectural highlights include the metabase-lib library for query construction and metadata management, a sophisticated visualization system with ECharts integration, and a multi-tenant embedding solution with JWT/SAML authentication. The codebase shows strong attention to internationalization, accessibility, and performance optimization through features like query caching, lazy loading, and bundle splitting.
Grafana is an open-source observability platform for querying, visualizing, and alerting on metrics, logs, and traces. It is a full-stack application with a Go backend and React/TypeScript frontend, featuring a plugin system for datasources, panels, and apps. The architecture is a monolith with Kubernetes-style API extensions, supporting multiple database backends (MySQL, PostgreSQL, SQLite). It includes built-in alerting, dashboard management, provisioning, and RBAC. The codebase is large and well-maintained, with high-quality UI components and data abstractions, but has some technical debt from dual build systems and generated code.
Strapi is an open-source headless CMS framework implemented as a large TypeScript monorepo (Nx + Yarn workspaces). In production it runs a Koa-based Node.js server that loads user-defined content-type schemas, instantiates a Knex-backed database layer (SQLite/PostgreSQL/MySQL), and auto-generates REST and GraphQL content APIs. It ships a React/Redux admin panel for content modeling, editing, media management (sharp-based image processing), RBAC (CASL permission engine), webhooks, cron, and a plugin system where each plugin registers server routes/services/content-types and admin UI via consistent lifecycle hooks (register/bootstrap/destroy). Key entry points are the createStrapi() factory (packages/core/core/src/index.ts), the strapi CLI (packages/core/strapi/bin/strapi.js), renderAdmin() (packages/core/strapi/src/admin.ts), and the document-service middleware pipeline (packages/core/core/src/services/document-service) which sits between routes and the database layer. Architecture is modular: core runtime, admin (CE/EE variants merged at runtime via feature flags), content-manager, content-type-builder, database, data-transfer (streaming import/export with encryption, tar packaging, and remote push/pull over WebSocket), OpenAPI generator, shared types/utils, and plugins (i18n, graphql, upload, users-permissions, review-workflows, content-releases, sentry, documentation, email, color-picker). The primary data flow is HTTP (REST/GraphQL) → controllers → document service middleware → entity service → database layer with subscriber-based lifecycle hooks; a parallel flow handles data-transfer streaming of entities, links, and assets between instances or to files. Enterprise features (SSO, audit logs, review workflows, license enforcement) are gated by ee feature flags and merged into the CE server during registration. Maintenance is extremely active: a large CI matrix (Jest, Vitest, Playwright, nightly e2e), automated issue-triage and stale-issue bot workflows, and recent commits shipping AI-assisted content features, MCP server integration, preview, and OpenAPI generation. Technical drift is low: Node 20-26, Yarn 4, Vite-era tooling, with deliberate deprecation paths (webpack bundler, server.globalProxy, admin.autoOpen) rather than abandoned code. Internal debts include the global global.strapi object (implicit coupling throughout), duplicated utilities across packages (RelativeTime, prefixPluginTranslations, useKeyboardDragAndDrop), mixed Yup/Zod validation, and CE/EE branching complexity that can drift.
AdminLTE is a professional, open-source admin dashboard template and UI framework built on Bootstrap 5.3. It provides a comprehensive set of responsive layout components, widgets, and vanilla TypeScript plugins (sidebar push menu, treeview, card widget, direct chat, fullscreen toggling, color mode, sidebar search, accessibility manager) activated via data-lte-* attributes. The architecture is modular: SCSS sources are compiled into a production-ready CSS bundle, and TypeScript sources are bundled into UMD and ESM builds. The project includes an extensive demo site with over 50 pages (dashboard, tables, forms, charts, mailbox, etc.) and a documentation site built with Astro and MDX. It ships with an optional extended color palette (14 WCAG AA-compliant colors) and a runtime primary color switcher, as well as a legacy v3 color compatibility sheet. The repository is the HTML/JS/CSS core; framework-specific editions exist for React, Vue, Angular, Laravel, and others.
Dashy is a self-hosted dashboard application that serves as a customizable startpage and service monitor for homelabs and server infrastructure. In production, it aggregates links to internal and external services, displays live widgets (weather, system metrics, crypto prices, news, etc.), and performs HTTP/ICMP status checks to indicate service health. The application is configured entirely via a YAML file (conf.yml) that defines pages, sections, items, widgets, authentication providers, themes, and layout options. Users can interact through multiple views: a default grid, a workspace with sidebar and iframe content, and a minimal tabbed view. The system also includes an interactive configuration editor, cloud backup/restore with AES encryption, and full REST API for programmatic management. Architecturally, Dashy is a full-stack web application with a Vue 3 frontend (built with Vite) and a Node.js Express backend. The frontend handles rendering, theming, localization (30+ languages), and client-side authentication flows (OIDC, Keycloak, header auth, built-in users). The backend provides endpoints for config saving, CORS proxying (with SSRF protection), status/ping checks, and optional REST API. Deployment is Docker-first, but bare-metal, cloud (Netlify, Render), and static hosting are also supported. The codebase is organized into reusable mixins (WidgetMixin, ThemingMixin, HomeMixin), custom Vue directives (DragSort, Tooltip, LongPress), and a schema-driven configuration system that powers both validation and the CodeMirror-based YAML editor. Key data flows include: (1) configuration loading from file and localStorage, merged by the ConfigAccumulator; (2) widget data fetching via the CORS proxy or direct API calls, with standardized error handling and update intervals; (3) authentication token exchange and session management across client and server; (4) status checks that update item indicators in real-time. External dependencies are limited to Node.js, Vue 3, Express, and a handful of widget-specific APIs (OpenWeatherMap, CoinGecko, etc.), all of which are optional and configurable. The project is purely an application with no data research or analytics components.
Reflex is a full-stack Python web framework that compiles Python code into a React frontend, enabling developers to build interactive web applications entirely in Python. In production, it serves as a stateful, event-driven framework with a component system, reactive state management, and a compiler that generates JavaScript/React from Python. The architecture is a multi-package monorepo: core types and compiler (reflex-base), UI component libraries (reflex-components-* wrapping Radix UI, Recharts, Plotly, etc.), a build SDK for cloud deployment (reflex-build-sdk), a hosting CLI (reflex-hosting-cli), a durable workflow engine (reflex-workflow), observability via OpenTelemetry (reflex-otel), documentation generation (reflex-docgen), and benchmarking infrastructure (reflex-bench). Key entry points include the CLI (reflex run, reflex deploy), the Python API (rx.App, rx.State, rx.Component), and the compiler that transforms Python component trees into React code. Data flows involve user-defined state classes with computed vars and event handlers, which the compiler serializes into JavaScript state management; the server uses Starlette with Socket.IO for real-time event propagation, and state can be persisted in memory, disk, or Redis. External dependencies include Node.js, Bun, React, Radix UI, Recharts, Plotly, SQLAlchemy, Redis, Postgres, and numerous npm packages. The framework is actively maintained with extensive unit, integration, and performance tests, and it dogfoods its own documentation site.
This repository hosts a curated collection of over 1800 dashboard icons for self-hosted services and applications, accompanied by a full-stack web application for browsing, searching, downloading, and submitting icons. The frontend is built with Next.js 16, React 19, Tailwind CSS 4, and shadcn/ui components, and it uses PocketBase as the backend for authentication, icon submissions, and external icon source management. The application provides an MCP (Model Context Protocol) server endpoint that allows AI assistants to search icons and resolve CDN URLs. It also includes an SVG color customizer for inline theme adjustments, a community submission workflow with admin approval, and automated syncs from third-party sources (Simple Icons, selfh.st, LobeHub). The codebase is well-structured with modern tooling, CI/CD pipelines, and both unit and end-to-end tests. While the repository is primarily an icon asset collection, the accompanying web application delivers significant value through its search, customization, and community features.
A well-crafted, self-contained application for analyzing and visualizing Claude Code usage logs. The system reads local JSONL transcript files (written by Claude Code regardless of subscription plan), parses them into a local SQLite database, and surfaces token counts, cost estimates, session histories, and subagent attribution through both a terminal CLI (`python cli.py today` / `stats` / `week`) and a rich single-page web dashboard (`python cli.py dashboard`). The dashboard is served by a stdlib-only Python HTTP server and bundles all HTML/JS/CSS inline, using Chart.js from CDN for visualizations. A companion VS Code extension embeds the same dashboard as a sidebar webview, auto-discovering the Python runtime via a flexible install-mode resolution chain (bundled `.py` sources, Homebrew shim, workspace clone, or explicit path). Architecturally, the code is split into three top-level Python modules—`scanner.py` (JSONL parsing, SQLite schema management, incremental scanning with deduplication by message ID), `cli.py` (CLI dispatch with per-turn cost calculation using a tiered pricing lookup), and `dashboard.py` (HTTP server with an embedded SPA). There are no third-party Python runtime dependencies; the VS Code extension uses TypeScript with minimal Node.js dependencies (only `@vscode/vsce` for packaging). The test suite is comprehensive, covering unit, integration, and HTTP-level scenarios across all three Python modules plus the entire TypeScript extension. A strict version parity test (`test_version.py`) enforces lockstep between the Python constant, the CHANGELOG heading, and the extension's `package.json`. Notable craftsmanship includes: the incremental scan engine that tracks file mtimes and line counts, processes only new/changed lines, and deduplicates streaming events via a conditional unique index on `message_id`; the one-time topic backfill mechanism for schema upgrades that re-reads only title records without touching token totals; and the VS Code extension's server-manager with configurable readiness probes that distinguishes the dashboard's JSON response shape from arbitrary HTTP 200s. The project is actively maintained with frequent releases, a weekly triage automation, and a detailed AGENTS.md that documents non-obvious invariants (streaming dedup, session model priority, cost calculation per-turn).
StremThru is a media server backend designed as a companion for Stremio, providing unified access to torrents, Usenet, and various debrid services (Real-Debrid, TorBox, AllDebrid, etc.) through Stremio addons. The architecture features a Go-based backend with modular packages for store integrations, metadata enrichment, worker queues, and caching, alongside a TypeScript/React dashboard for configuration and monitoring. Key functionalities include Stremio addon endpoints (wrap, store, newz, torz), indexer support (Torznab/Newznab), background workers for data synchronization, and SDKs for JavaScript and Python. Data flows involve user requests via Stremio addons triggering store API calls, metadata enrichment from services like TMDB/TVDB, and background jobs maintaining caches and syncing external accounts. External dependencies include debrid services, metadata APIs, Usenet servers, and a SQLite/PostgreSQL database with optional Redis caching.
Tabler is a comprehensive, open-source UI kit and dashboard template built on top of Bootstrap 5. It functions as a frontend library and design system, providing a complete set of HTML, SCSS, and JavaScript components for building admin panels, SaaS applications, and marketing sites. The repository is structured as a monorepo containing the core library (`@tabler/core`), a preview/demo site (`@tabler/preview`), and documentation (`@tabler/docs`). It relies heavily on client-side technologies, utilizing TypeScript, Vite, and SCSS for development, with a build process that compiles assets for distribution. The architecture is primarily static site generation for documentation and demos, using Eleventy (11ty) and Liquid templating to render component examples from reusable includes. The core JavaScript logic is modular, with components like Modals, Dropdowns, and Tooltips implemented as vanilla JS classes that extend Bootstrap's native functionality. The project maintains a high degree of separation between the core library code and the documentation/demo content, allowing the library to be consumed as a package while the preview site serves as a living style guide. Key entry points include `core/js/tabler.ts` for the main JavaScript bundle and `core/scss/tabler.scss` for the CSS. The system relies on external dependencies like Bootstrap 5, ApexCharts, and various form plugins. Data flows are minimal, primarily involving static JSON files used to populate demo content in the preview and documentation sites, rather than dynamic backend processing. The project is actively maintained with recent commits and a robust CI/CD pipeline for testing and publishing.
This repository hosts Homepage, a self-hosted dashboard application for homelab and server enthusiasts. Built with Next.js and React, it aggregates data from over 100 external services (media servers, download clients, network tools, system monitors) via a centralized proxy architecture. The system is configuration-driven: users define services, bookmarks, widgets, and settings in YAML files, optionally extended via Docker labels or Kubernetes ingress annotations. A key architectural pattern is the widget system, where each integration consists of a React component, a proxy handler (handling authentication, session management, and data transformation), and a widget metadata file. The backend API routes handle proxying, caching, authentication (NextAuth with OIDC/password), Docker/Proxmox stats, weather, stocks, and an MCP endpoint for AI-assisted configuration. The frontend uses SWR for client-side data fetching, Tailwind CSS for theming, and i18next for internationalization (20+ languages). The codebase exhibits solid engineering practices: comprehensive test coverage (Vitest), CI/CD pipelines (GitHub Actions), Docker multi-arch builds, and extensive documentation. However, the large widget surface introduces duplication in authentication and proxy logic, and some patterns (in-memory caching, version-specific endpoints) represent maintenance risks. Overall, this is a well-crafted application for its domain, offering high customizability and a clean plugin-style architecture.
Neko Master is a production-grade traffic analytics platform for Clash/Mihomo and Surge proxy gateways. It collects real-time connection data via WebSocket or HTTP polling, aggregates it in SQLite (always) and optionally ClickHouse, and serves a rich dashboard built with Next.js 16, React 19, and Tailwind CSS. The system supports both direct collector-to-gateway mode and a Go-based agent mode for remote or isolated networks. The backend is a Fastify 5 server with WebSocket push, repository-patterned database access, in-memory realtime store, and health-aware dual-write routing. The frontend provides per-domain, per-IP, per-proxy, per-rule, per-country, and per-device statistics with time-range filtering, pagination, charts, and interactive visualizations including a DAG rule-chain flow. The project is a monorepo with pnpm and Turborepo, including a shared TypeScript types package and extensive CI/CD. While primarily an application, it has strong data-engineering aspects: batch buffering, time-series aggregation, GeoIP enrichment, and ClickHouse integration for large-scale deployments.
Apache Superset is a production-grade business intelligence web application for data exploration and visualization. It provides a full-stack platform (Python Flask backend, React/TypeScript frontend) that connects to over 50 SQL databases, allowing users to create interactive dashboards, design charts via a plugin architecture, execute ad-hoc SQL queries in SQL Lab, and schedule email/slack reports with screenshots. The system manages metadata in a relational database (PostgreSQL/MySQL), uses Celery for background tasks (dashboard thumbnails, report execution), Redis for caching and async events, and exposes a REST API for programmatic access. Key architectural patterns include a command pattern for CRUD operations, DAO layer for data access, a rich chart plugin system with lazy-loaded rendering, and an embedded SDK for external dashboards. The codebase is actively maintained with frequent schema migrations, extensive tests, and an experimental MCP service for AI integration. While primarily an application, it includes data-research-adjacent features like semantic layers and pandas-based post-processing for chart data.
This is a production Laravel application that powers the real-time office dashboard at Spatie (dashboard.spatie.be). It displays a rotating set of screens on a wall-mounted TV, showing team member statuses, GitHub/Packagist statistics, climate data, cookie club ratings, now-playing music, Officient calendar attendance, Oh Dear uptime alerts, and product analytics from Fathom. The architecture is a monolith built on Laravel 12 with Livewire 4 for reactive components, Tailwind CSS 4 for styling, and Pusher/WebSockets for real-time updates. Key entry points are the main dashboard route (/) and webhook endpoints for now-playing songs and Oh Dear alerts. Data flows from external APIs (Fathom, GitHub, Packagist, Slack, Officient, Apple Music, Last.fm, climate sensors, Cookie Club) into database-backed tile stores, which are polled by Livewire components. The system includes a screen scheduler with conditional visibility, a weekplanning overlay, and a deploy-status endpoint for automatic page reloads. The codebase is well-structured, follows Laravel conventions, and includes comprehensive tests. While the dashboard is tailored to Spatie's internal use, many components (Fathom analytics service, forecast calculator, path normalizer, screen availability checker, weekplanning logic) are cleanly abstracted and could be reused in other dashboard or analytics projects.
Hermes Studio is a self-hosted AI agent orchestration platform providing a unified interface for multiple AI agents (Hermes, Ekko, Claude Code, Codex, Pi) with chat, workflow automation, agent management, and skill-based extensibility. The architecture features a Vue 3 frontend, Node.js/Koa backend, Electron desktop client, and hybrid TypeScript/Python agent runtime. Key capabilities include real-time collaboration via Socket.IO, voice processing with multiple STT/TTS providers, file management with preview capabilities, usage analytics, and Model Context Protocol (MCP) integration for extending agent tools. The platform supports social messaging integrations (Feishu, Telegram, Weixin) and MCU device support for embedded voice processing.
GridStack.js is a production-grade TypeScript library for building responsive, drag-and-drop dashboard layouts. The core GridStack class manages widget lifecycle, DOM placement, responsive column switching, nested grids, serialization, and eventing, while GridStackEngine performs collision and positioning math without touching the DOM. The library ships its own drag-and-drop subsystem rather than depending on HTML5 drag-and-drop or jQuery, and it has zero runtime dependencies. Architecturally, the repository is a multi-package collection: a framework-agnostic core, a SCSS styling layer, and official Angular, React, and Vue wrappers. The wrappers integrate through callback hooks such as addRemoveCB, saveCB, and updateCB, plus DOM-stamped host APIs, allowing each framework to dynamically create and destroy widgets while keeping item content mounted during cross-grid drags. Demo applications under demo/, angular/projects/demo, react/src, and vue/src exercise the public API and serve as integration references. The project is actively maintained with a comprehensive Vitest and Playwright test suite, issue-numbered regression tests, and frequent releases. Its main technical debt is the large monolithic gridstack.ts (roughly 3100 lines) and the need to keep three framework wrappers synchronized with core API changes. The Angular wrapper is intentionally pinned to an older Angular major and some legacy build artifacts remain, but the core engine/UI separation, clean utility layer, and callback-based framework integration make many parts genuinely reusable.
Pi-hole is a network-wide ad blocking application that operates as a DNS sinkhole. The repository contains the core shell scripts for installation, configuration, and management of the Pi-hole system. The primary entry points are the `pihole` CLI command and `gravity.sh`, which downloads and compiles blocklists into a SQLite database. The architecture is a collection of bash scripts that orchestrate the FTLDNS daemon (a separate binary) and provide a command-line interface for allow/deny lists, querying, debugging, and updates. The code is well-structured with modular functions, error handling, and extensive test coverage across multiple Linux distributions. It is a mature, actively maintained project with a large community.
Dynacat is a self-hosted, configurable personal dashboard application forked from Glance. It aggregates content from dozens of external services — RSS/Atom feeds, Reddit, Hacker News, Twitch, YouTube, weather (Open-Meteo), financial markets (Yahoo Finance), Docker containers, media servers (Plex/Jellyfin/Emby/Navidrome), torrent clients, and DNS servers — into a single YAML-configured page layout. The backend is a Go HTTP server built on the standard library, serving server-rendered HTML templates with progressive enhancement via vanilla JavaScript, htmx, and SSE for live widget updates. It supports password-based and OIDC authentication, per-page access control, a CSS-variable theme system, and PWA/installability features. Architecturally, the codebase centers on a widget plugin system: each widget type implements a common lifecycle (initialize, update, render, optional request handling) registered in a factory. Shared infrastructure includes a disk-based image cache with proxy fallback, a singleflight-based shared HTTP request layer that deduplicates concurrent external fetches, a generic worker pool for parallel requests, and an SSE update loop. Configuration supports YAML includes, environment variable and Docker secret substitution, and hot-reload via fsnotify. The code is well-organized for a fork of this size: shared patterns are extracted into reusable helpers (generic singleflight, worker pool, custom YAML unmarshalers, and a standalone sysinfo package under pkg/), and focused unit tests cover auth and several widgets. Main caveats are large monolithic widget files (700–900 lines mixing HTTP, parsing, and rendering), duplicated fetch logic across the 'latest-media' and 'playing' widgets, and heavy reliance on many external APIs whose availability or rate limits can affect the dashboard. The project is actively maintained with frequent releases, GitHub Actions CI/CD, and a goreleaser setup for multi-arch Docker images.
WorldMonitor is a full-stack, open-source global intelligence platform providing real-time monitoring of geopolitical, economic, military, supply chain, and natural events. The codebase is overwhelmingly an application (single-page web dashboard, Vercel Edge API, Convex backend, Tauri desktop app, CLI, and SDKs) with a secondary data pipeline character (consumer price scraping, external API seeding). It powers a commercial SaaS with free and Pro tiers, featuring a map-based dashboard with 100+ configurable panels, an MCP (Model Context Protocol) server for AI agents, and extensive multi-language support (28 locales). The architecture follows a seed-cache pattern where Railway cron jobs fetch external data into Redis, and serverless Edge functions read cached JSON for low-latency responses. The frontend uses vanilla TypeScript with Vite, deck.gl/MapLibre for mapping, and a panel system for modular UI composition. The system is actively maintained, with daily commits, comprehensive test coverage (unit, integration, E2E with Playwright), and a well-documented API surface with 298 protobuf definitions across 36 domain services. While the codebase is large and occasionally duplicates shared constants across modules, it demonstrates strong software engineering practices including circuit breakers, idempotency keys, rate limiting, and a consistent handler pattern.
Ant Design Pro is an enterprise-grade React admin dashboard starter/template, not a data research repository. It provides a production-oriented SPA scaffold built on Umi Max 4, React 19, Ant Design 6, and ProComponents, with pre-built pages for authentication, dashboards, forms, lists, profiles, results, exceptions, account management, and an AI chatbot. The code is organized as a classic frontend application: `src/app.tsx` composes runtime configuration, `config/routes.ts` declares routing, pages are co-located with services, mock data, styles, and tests, and `src/services/` contains generated API client code. There is no real persistence; all data flows through mock handlers during development or through the bundled Cloudflare Worker backend in deployed demos.