Self Improving AI Company Converting Tokens to Work and Dollars.
Actively maintained rebrand of MachinaOS — strong engineering signals but no CI badge, thin config/limits docs, no open issues triage.
Rebrand of MachinaOS — drag-and-drop AI workflow platform with 16 agent types and 11 LLM providers.
Auto-migrates legacy ~/.machina state into .opencompany, preserving deployments across the rebrand from MachinaOS.
| Rating | Summary | |
|---|---|---|
| Quality | solid (19/24) | Actively maintained, well-adopted platform with strong engineering discipline but gaps in config docs and issue triage. |
| PAI Relevance | integrate (0.50) | Meets the integrate threshold, but overlaps with existing Delegation/Agents/Browser skills and requires moderate Python-to-Bun glue. |
This entry is functionally a rename/rebrand of the already-appraised zeenie-ai/MachinaOS repository — scores and reasoning track closely with that prior appraisal.
19/24 — maintained / adequately-documented / high-discipline
Failed:
Passed:
Failed:
Passed:
npm install -g opencompany, company start) under Quick Start headingFailed:
Passed:
test, test:backend, test:frontend, test:nodes scripts| Dimension | Score | Assessment |
|---|---|---|
| Harvest Value | 1 | The "AI Employee" delegation model, 16 specialized agent types, and multi-provider LLM routing are worth studying for PAI's Agents/Delegation subsystems, though not a wholesale novel algorithm. |
| Integration Readiness | 1 | Ships an npm-installable CLI (company start) but the backend is a full Python/FastAPI/Temporal/Vite stack — a heavy service to subprocess-wrap rather than a lightweight drop-in. |
| Overlap Risk | 1 | Significant functional overlap with PAI's Delegation, Agents, Browser, Apify, and BrightData skills for orchestration, web automation, and multi-channel messaging. |
| Gap Fill | 1 | Visual workflow builder, Android phone control, and Stripe billing integration address areas where PAI's current capability manifest has limited or no coverage. |
Composite: 0.50
Petites Fugues advisory: Run npx opencompany init and wire the email + calendar connectors to a single drag-and-drop workflow that triages customer order inquiries and restocks the CD/DVD/Vinyl catalog — replaces manual email triage for the store owner with a persistent, memory-backed agent that runs on their own hardware and keys, no subscription cost.
Capture-to-Knowledge Pipeline: Install OpenCompany's email/calendar connector nodes as the ingestion trigger layer feeding the pipeline's clean-room Haiku validation step — captures now arrive as structured workflow events instead of manual drops, closing the gap between "design + manual validation" and an automated intake path.
Fabric Recommender (fab): Extract OpenCompany's 50+ service connector registry pattern from its integration layer and benchmark it against fab's current single-pattern execution model in the CLI — if the connector abstraction generalizes cleanly, use it to let fab dispatch pattern output directly to messaging/phone channels instead of stdout only.
Category: AI Agent Frameworks
In this category: zeenie-ai--MachinaOS (solid 19/24, integrate), sipyourdrink-ltd--bernstein (excellent 22/24, integrate), lobehub--lobehub (excellent 21/24, integrate), VoltAgent--voltagent (excellent 21/24, integrate), microsoft--TinyTroupe (excellent 20/24, integrate), bmad-code-org--BMAD-METHOD (solid 19/24, integrate), tkellogg--open-strix (solid 19/24, integrate), gastownhall--gastown (solid 17/24, integrate)
Standing: Ties exactly with the prior zeenie-ai--MachinaOS appraisal (same score, same verdict) since this is the rebranded continuation of that codebase rather than a distinct new entrant.
Density: 10/10 — README (first 8KB), package.json dependency manifest, GitHub topics, stars/forks/issues/release metadata, and landscape context (including a prior appraisal of the same codebase under its former name) were all available; full source tree, CI configuration, and test suite contents were not inspected directly.
This repo (zeenie-ai/OpenCompany) and zeenie-ai/MachinaOS appear to be the same underlying project — the README explicitly documents a migration path from ~/.machina to ~/.opencompany and retains machina as a deprecated CLI alias. Landscape trackers should treat these as one entity to avoid double-counting stars, forks, and PAI-fit scoring across two slugs.