Cal.diy is a fully open-source, MIT-licensed fork of Cal.com, providing a self-hostable scheduling platform. It is a large monorepo containing a Next.js web application (apps/web) for booking pages, settings, and admin, a NestJS API (apps/api/v2) for platform REST endpoints, and extensive packages for business logic (packages/features), integrations (packages/app-store with 50+ apps), embeddable booking widgets (packages/embeds), and reusable React atoms (packages/platform/atoms). The architecture uses tRPC for client-server communication, Prisma ORM with PostgreSQL, Redis caching, and a custom dependency injection system (ioctopus) alongside NestJS DI. Key patterns include a tasker abstraction for async/sync background jobs (webhooks, emails, calendar sync), a versioned webhook payload builder factory, repository pattern over Prisma, and a consistent app-store integration structure. The platform exposes a public API with OAuth2, webhooks, and embeddable components for third-party developers. The codebase is actively maintained with frequent schema migrations and CI/CD pipelines, but exhibits some technical drift due to dual API surfaces (tRPC vs REST), stub implementations for enterprise features, and generated files that require regeneration.
Neo-Store is a modern, feature-rich F-Droid client for Android built with Kotlin and Jetpack Compose. It provides a full-featured app store experience for browsing, searching, installing, and updating free and open-source Android applications from multiple repositories. The app emphasizes privacy and security, integrating with Exodus Privacy to display tracker information, providing privacy scoring, and supporting reproducible builds verification. Architecture follows MVVM with Room database for persistence, Koin for dependency injection, and WorkManager for background sync, download, and installation tasks. The UI is fully composed with Material Design 3 and adaptive navigation. It supports multiple installation methods (root, Shizuku, session, system) and provides advanced features like download stats, mirror rotation, batch updates, and QR code repository scanning. The codebase is well-structured with clear separation of concerns: data layer (Room entities, DAOs, repositories), index parsing (v0/v1/v2), installer management, and a rich Compose component library. It demonstrates strong Kotlin idioms with extensive use of sealed classes, flows, and coroutines. While the code is largely modern, some areas (e.g., BLOB storage, LegacyInstaller) show technical debt. The project is actively maintained with frequent releases and community contributions.
Runtipi is a self-hosted homeserver orchestrator: a web-based control plane for installing, updating, backing up, and managing Docker Compose applications on a single server. In production it runs as a NestJS backend, a React frontend, and a shared TypeScript schema package, with PostgreSQL as the primary datastore, RabbitMQ for asynchronous job queues, Dockerode for container control, and Traefik as the reverse proxy and TLS/forward-auth gateway. The app-store model clones external git repositories containing app manifests and compose definitions, then validates and renders them through a dynamic form system. The architecture is a monolithic backend organized around modules for app lifecycle, marketplace, app stores, backups, auth, links, settings, and i18n; long-running operations are executed through a command/handler pattern with per-app async mutexes and schema-validated RabbitMQ event queues.