Wavefront is an enterprise AI middleware platform, open-source alternative to tools like UnifyApps and n8n. It provides a full-stack system for building, managing, and deploying AI agents, chatbots, voice agents, knowledge bases (RAG), and AI-powered workflows. The monorepo includes a Python FastAPI backend with a modular, domain-driven architecture (agents, tools, knowledge base, voice, triggers, auth, API proxy), a React/TypeScript management console, background workers (Celery, stream processors), and the `flo_ai` Python agent framework (LLM wrappers, Arium graph engine, tool system). The platform supports multi-tenancy, RBAC, cloud storage abstractions (GCP/AWS/Azure), and pluggable datasource and authenticator modules. While primarily an application, it incorporates RAG pipelines, image embedding services, and model inference, giving it a hybrid character with strong data engineering elements.
Solace Agent Mesh is a production-grade, full-stack platform for building, deploying, and managing event-driven multi-agent AI systems. It comprises a Python backend (FastAPI, Google ADK, SAC), a React/TypeScript web UI (chat, projects, workflows, prompts, scheduled tasks), a Click-based CLI, and a Docusaurus documentation site. The system uses a microservices-like architecture with separate gateway (HTTP/SSE), platform service (model configuration, storage), and agent components, all communicating via the Solace event broker and the A2A (Agent-to-Agent) protocol. Key entry points include the CLI (`solace-agent-mesh`), the web UI (`/chat`, `/projects`, `/workflows`), and the REST API (`/api/v1`). Data flows involve user requests via SSE, agent orchestration with workflow DAGs, tool execution (built-in, MCP, OpenAPI), artifact storage (S3/GCS/Azure/filesystem), and session persistence in SQL databases (SQLite/PostgreSQL/MySQL). External dependencies include a Solace broker, LLM endpoints (LiteLLM), optional databases, and cloud storage services. The repository is marked as deprecated (Development Status 7 – Inactive), with the new version being a desktop application.
Voquill is a cross-platform voice dictation and AI transcription application that allows users to dictate into any application with real-time speech recognition, AI post-processing, and an agent mode for automated tasks. The desktop app (Tauri + Rust + React) provides a native overlay, global hotkeys, and multiple transcription backends (local Whisper, cloud providers, enterprise). The enterprise edition includes a gateway service with PostgreSQL, admin panel, OIDC SSO, and custom STT/LLM providers. Mobile apps (Flutter) with keyboard extensions provide dictation on iOS and Android. The CLI tool offers headless dictation and agent functionality. The architecture is a monorepo with shared packages for types, utilities, voice AI integrations, and agent loop, demonstrating a well-structured, multi-platform application with significant hybrid characteristics due to extensive data pipelines for transcription and model management.
This repository is the documentation site for Factory, an AI-native software development platform centered on the Droid CLI. It contains bilingual (English and Japanese) documentation covering CLI usage, enterprise deployment, integrations, skills, hooks, and benchmarks. The repository also includes CI/CD workflows, changelog automation scripts, and a translation pipeline. While no application source code is present, the documentation is highly structured and includes reusable patterns for skill definitions, hooks, and plugin packaging. The codebase is actively maintained with frequent updates, but exhibits moderate technical drift due to rapid version churn, model name instability, and bilingual documentation divergence.
The Pentaho Platform is the core backend for the Pentaho Business Analytics server. In production, it serves as a content repository (JCR/Jackrabbit), authentication/authorization system, scheduler (Quartz), and a plugin-based execution engine for BI actions (reports, OLAP, data integration). The system is a monolithic Java EE application deployed on Tomcat, using Spring for dependency injection, Hibernate for persistence, and GWT for the legacy user console. It provides REST and SOAP APIs for repository management, security administration, and job scheduling. The codebase is organized into modules (api, core, extensions, repository, scheduler, user-console) and relies on external libraries such as Apache Jackrabbit, Quartz, Mondrian, Kettle, and Spring Security. Architecturally, the platform is built around a central static service locator (PentahoSystem) and a large set of interfaces for actions, components, and services. It supports multi-tenant repository paths, pluggable authentication (LDAP, JDBC, memory), and a rule-based authorization system. The platform is functionally comprehensive but carries significant technical debt: deprecated interfaces, mixed JUnit versions, outdated front-end technologies (Dojo, GWT), and over-engineered exception hierarchies. Some modules (e.g., authorization decisions, cache expiration, file content decoration) are well-designed and potentially reusable.
TACTIC is an open-source enterprise workflow and digital asset management (DAM) platform, primarily targeting media and entertainment production pipelines. It provides a full-stack web application built on CherryPy/Cheroot, featuring a custom widget framework, a client-server API (XML-RPC/REST), and a database abstraction layer supporting PostgreSQL, MySQL, Oracle, SQLite, and SQL Server. The system manages assets, shots, tasks, pipelines, check-ins, and user permissions, with integrations for DCC tools like Maya, Houdini, and Nuke. The architecture is monolithic, with a Python backend serving a JavaScript-heavy frontend (MooTools-based, with some React components). Key entry points include the web server (CherryPy adapter), the client library (`TacticServerStub`), and command/trigger systems for business logic. The codebase is large and feature-rich but carries significant technical debt: bundled third-party libraries for multiple Python versions (2, 3.6, 3.x), deprecated modules, hardcoded paths, and inconsistent coding styles. Despite active development (recent commits), the drift from modern Python and library ecosystems is high, making long-term maintenance challenging.