Operately is an open-source company operating system for coordinating goals, projects, and teams. It provides a full collaboration suite including spaces (groups), goals with OKRs, project management with milestones and tasks, check-in cadence, retrospectives, discussions, document and file management (Resource Hubs), KPI tracking, and people management. The system is built as a monolith with a Phoenix (Elixir) backend serving a custom TurboConnect API (mutation/query protocol) and a React/TypeScript single-page application frontend with a reusable component library (turboui). It also offers a CLI tool, Model Context Protocol (MCP) integration for AI agents, and extensive background job processing via Oban for notifications, email delivery, search indexing, and billing operations. The architecture follows a clean domain-driven design with operations (Ecto.Multi transactions), activity logging (event sourcing with embedded schemas), an access control system with hierarchical groups and bindings, and a rich content editor with link enrichment and blob storage. The codebase is well-tested with both backend (ExUnit, Wallaby) and frontend (Jest, React Testing Library) tests, and includes a demo data builder for development. The enterprise edition (ee/) extends the core with SaaS admin capabilities, billing management via Polar, site messages, and feature flags. The system has evolved significantly with over 115 data migrations, indicating active development. While the core architecture is solid and many patterns are reusable, there are some incomplete features (e.g., stubbed notification handlers, missing email templates) and occasional code duplication between internal API and MCP tool layers. Overall, it demonstrates strong engineering craftsmanship with practical trade-offs for an open-source SaaS application.
This is a Terraform module, published on the Terraform Registry as `terraform-google-modules/project-factory/google`, that automates the creation and configuration of Google Cloud Platform (GCP) projects. It follows a modular architecture with a root module orchestrating several submodules such as `core_project_factory`, `project_services`, `shared_vpc_access`, `budget`, `quota_manager`, `essential_contacts`, `gsuite_enabled`, and `svpc_service_project`. The module handles project creation, billing association, IAM policy management, Shared VPC attachment, API enablement with service identities, budget alerts, consumer quota overrides, essential contacts, and G Suite group integration (via the third-party `DeviaVir/gsuite` provider). Entry points are the root `main.tf` and the submodule directories; usage is through standard Terraform workflow (`terraform init`, `plan`, `apply`). External dependencies include the `hashicorp/google`, `hashicorp/google-beta`, and optionally `DeviaVir/gsuite` Terraform providers. The repository also provides helper scripts for seed service account setup (`helpers/setup-sa.sh`), state migration (`helpers/migrate.py`, `helpers/migrate4.py`), and prerequisite validation (`helpers/preconditions/preconditions.py`). The codebase is well-structured with extensive use of locals, `for_each` loops, and separation of concerns, making individual submodules reusable across different projects. Despite being infrastructure-as-code, it exhibits strong software engineering practices including semantic versioning, automated testing (Go, InSpec, Python), and CI/CD pipelines.
This is a Terraform module for deploying a production-grade HashiCorp Vault cluster on Google Compute Engine (GCE). It provisions all necessary networking (VPC, subnets, NAT, firewalls), a GCS bucket for Vault's storage backend, a KMS key for auto-unseal and TLS encryption, and manages the full lifecycle of Vault nodes via a managed instance group with autoscaling and autohealing. The module supports both internal and external load balancers, and includes an optional submodule (`modules/cluster`) for organizations that need to separate concerns (e.g., shared VPC setups). The core logic resides in the `modules/cluster` submodule, which contains instance templates, load balancer configuration, health checks, IAM bindings, and self-signed TLS certificate generation. A startup script template handles Vault installation, configuration, mTLS setup, logging agents, and security hardening (core dumps disabled, swap disabled, unprivileged user). The module is highly parameterized with ~60 input variables, allowing customization of machine types, Vault versions, networking, and TLS management. It is designed for high availability (HA) with GCS backend and auto-unseal via Cloud KMS. The repository includes examples, integration tests using Kitchen/Terraform and Inspec, and CI/CD pipelines, indicating a mature, community-maintained module. The code is clean and follows Google's Cloud Foundation Toolkit conventions, but it is relatively conventional Terraform infrastructure code, not particularly novel or reusable beyond its intended purpose.