Infrahub is a full-stack infrastructure data management platform that provides a unified data model for network, cloud, and infrastructure resources. It features schema-first graph-based data modeling (using Neo4j), version control for data via branching and proposed changes, automation through generators and transforms, and integration capabilities via APIs, webhooks, and SDKs. The backend is built with Python/FastAPI, Prefect for workflow orchestration, and uses Neo4j as the primary graph database. The frontend is a React/TypeScript application with TanStack Query and Jotai for state management. The system supports IPAM, diff computation, artifact generation, and role-based access control, targeting infrastructure teams seeking repeatable, validated workflows for infrastructure as a service.
Sylve is an open-source FreeBSD infrastructure management platform written in Go. It provides a unified control plane for managing bhyve virtual machines, FreeBSD jails, ZFS storage, and networking (including VLANs, switches, DHCP, PF firewall, WireGuard, and mDNS). The system supports high-availability clustering via Hashicorp Raft consensus, with built-in backup/replication (Zelta) and live migration of workloads. It exposes a REST API (Gin), a CLI/REPL (Bubbletea TUI), and a SvelteKit web frontend. The architecture is modular with interface-based services, middleware for auth and request limiting, and a typed console protocol over Unix sockets. The codebase is heavily tested with unit, integration, and real-ZFS tests, and is licensed under BSD-2-Clause with sponsorship from the FreeBSD Foundation.
Pterodactyl Panel is a production game-server management control panel. It manages a fleet of game servers (Minecraft, Source Engine, Rust, voice servers, etc.) running in Docker on remote nodes, coordinated by the companion Wings daemon. The PHP/Laravel backend provides a session-based admin UI, a JSON:API-style application API for provisioning, a permission-scoped client API for end users, and a remote API used by Wings for server installation, transfer, backup status, and SFTP authentication. The React/TypeScript frontend handles the modern client experience—console, file manager, databases, backups, schedules, network allocations, account management, and 2FA—while the admin area remains classic Blade/jQuery views. Data flows from MySQL/MariaDB through Eloquent repositories and service classes, then to Wings over HTTP via Guzzle; Redis is used for queues, cache, and sessions, and optional anonymous telemetry is collected. Architecturally this is a Laravel monolith with a clean layered separation: FormRequest validation, service classes, Eloquent repositories behind interfaces, Fractal transformers, event/observer hooks, and a sophisticated activity-logging subsystem. The frontend is organized into reusable components, custom hooks, and pure utility functions, many of which are isolated enough to lift into other projects. The codebase is mature and actively maintained with CI, integration tests, and security patch releases, but it carries visible technical debt: a dual UI stack (Blade plus React), older React 16 tooling (easy-peasy v4, react-hot-loader), 190+ migrations spanning a decade, and a few deprecated models/fields. The repository is clearly an application, not a data/research project; although it stores substantial operational data, its purpose is real-time system control rather than analysis.