Creator, content, consent, attribution, ledger, training and access truth
Stable identities, state machines, server authorization, provenance, approvals, statements, audit and export.
generated from canonical reports
OnlyFans management agency · operating-system research
Run the agency as one accountable system.
HALO is not one CRM screen and not one fan inbox. It is the control plane joining creator trust, 24/7 chatter revenue operations, content supply, money truth, training, and owner decisions—while Buzz and specialist rails keep bounded authority.
6OFM operating domains
154recovered GitHub repos
95useful-or-better signals
12explicit rejects
1,781unique discovery results reported
Coverage receipt: the original Web search reported 1,781 unique repositories but retained names for only its promoted set. This page recovers every unique GitHub repository now cited across the canonical research files. The remaining 1627 identities are an explicit re-search backlog—not silently discarded evidence.
Authority map
One operating system, bounded components.
The architecture is defined by who is allowed to be true about each thing—not by whichever product has the nicest dashboard.
Channels, messages, workflows and agent sessions
Communication and coordination. No unrestricted mutation of money, credentials, contracts or rights.
KYC, e-sign, vault, payment and tax providers
Verify, sign or execute at regulated boundaries while HALO preserves status, evidence and liabilities.
CRM, ERP, content, knowledge and automation systems
Adopt only a bounded journey or pattern unless a deliberate re-platform decision gives one system full authority.
Operating model
Six domains, one agency loop.
Each deep dive starts with personas and authority, traces the end-to-end journey, audits current HALO coverage, ranks donors, and asks what the previous research missed.
Creator lifecycle
Recruit, qualify, verify, contract, onboard, support, renew and exit creators without losing consent, access, rights or history.
InfluenceXNexoraAgencyOSCreator Marketplace
91 recovered reposOpen deep dive →
Chatter revenue ops
Turn live fan conversations into assigned, resumable, policy-bound work with playbooks, handoffs, QA evidence and attribution.
BuzzwacrmDeskcommCRMZavu Inbox
49 recovered reposOpen deep dive →
Content studio + AI
Connect brief, asset, version, feedback, approval, rights, customs, publishing and reuse into one evidence-backed state machine.
Kitsu/ZouOrbitMixpostFrame.io
65 recovered reposOpen deep dive →
Money, ledger + payouts
Preserve every source event through double-entry liabilities, creator statements, reversals, disputes, reconciliation and legal payout rails.
MelonpgledgerFormanceERPNext
43 recovered reposOpen deep dive →
Training + gamification
Practice creator-specific scenarios, score against versioned rubrics, calibrate QA, coach, certify and reward without creating a shadow pay system.
Second NatureMaestroQAQuestifyHALO Tasks & Rewards
18 recovered reposOpen deep dive →
Owner intelligence
Show what changed, why it matters, who owns the response, when it is due and what source proves closure across the whole agency.
Open MercatoOperatelyComp AI CRMAFFiNE
114 recovered reposOpen deep dive →
How it compounds
From creator trust to owner control.
The wider goal is continuity: the agency should survive handoffs, turnover, disputes, platform outages and creator exits without losing what happened or who is accountable.
01Creator trust passportTerms, consent, rights, access and readiness
→02Chatter executionQueues, playbooks, handoffs and promises
→03Content supplyBriefs, versions, approval and provenance
→04Revenue truthSource events, liabilities and statements
→05Learning loopQA, coaching, certification and fair rewards
→06Exception controlOwner, due date, decision and closure evidence
Repository intelligence
Every recoverable repo, rated in context.
A 5/5 is a priority HALO experiment. A 1/5 is an explicit reject. Scores describe fit and evidence for this agency—not general software quality, popularity or permission to copy code.
154 repositories visible
28 mentions
block/buzz ↗
Selected collaboration and agent sidecar
Research evidence
- Camron explicitly liked block/buzz and wants it
- Client anchor: block/buzz is selected for the
- Camron's choice of block/buzz is directionally strong.
- Repository · block/buzz
14 mentions
open-mercato/open-mercato ↗
Priority system-class architecture spike
Research evidence
- G2 · open-mercato/open-mercato · README describes an MIT AI-engineering foundation with ready-made CRM/ERP modules, custom entities/dynamic forms, multi-tenancy, hierarchical organizations, feature-based RBAC, events, self-service portals, workflows, production, and a live demo. · Highest-priority build-substrate experiment. Compare its tenant/organization/entity/workflow contracts against HALO, but do not make it authoritative until identity, migration, audit, and Convex integration are proven. · High for stated primitives; Medium for production fit
- open-mercato/open-mercato · https://github.com/open-mercato/open-mercato · 1,690 · MIT · 2026-08-28T23:25:44Z · false · main
- 1 · Open Mercato · MIT modular/API platform with CRM, custom entities and dynamic forms, self-service portals, workflows, tenant/organization scoping and feature-based RBAC in its README. · Highest-priority architecture spike, not adoption. Compare its tenant/entity/workflow contracts to HALO with synthetic data. A second datastore, auth system and migration path are the main risks.
- 9 · Open Mercato · MIT modular multi-tenant/custom entities, dynamic forms, org hierarchy/RBAC, event subscribers/workflows. · ARCHITECTURE SPIKE only · MIT per API metadata. General substrate could swallow scope and duplicate HALO; test one entity/event slice only if build pressure appears. · Medium-high
8 mentions
ArnasDon/wacrm ↗
Strongest chatter-plane code donor
Research evidence
- 3 · wacrm — ArnasDon/wacrm · Chatter-team shared inbox, conversation assignment, role-scoped operations, WhatsApp templates/broadcasts, automation; journeys 4 and 6 · integrate · MIT Next.js/Supabase CRM for WhatsApp. Source inspection found account roles (owner/admin/agent/viewer), server-side API-key scopes, account-membership RLS migration, typed message validation, Meta transport retries, encryption helpers, and per-key rate-limit hooks. · Integrate only at the messaging boundary; HALO remains creator/money/Drive authority. WhatsApp Business API, Supabase, and account identity must not silently become HALO’s second auth system. · High
- ArnasDon/wacrm · https://github.com/ArnasDon/wacrm · 2,143 · MIT · 2026-08-27T08:49:39Z · false · main · —
- 2 · WACRM; handoff, auto-reply guard, webhook, send path · Self-hostable shared inbox, contact/fan-like memory, pipelines, idempotent webhook, human assignment pause, handoff summary, send persistence, RLS/API/MCP boundary. · STUDY/adapt connector mechanics · MIT per API metadata. WhatsApp implementation is not an OF connector; optional auto-reply is disallowed for HALO sensitive sends. Avoid importing its channel authority wholesale. · High for cited source behavior
- ArnasDon/wacrm · https://github.com/ArnasDon/wacrm · 2,143 · MIT · 2026-08-27T08:49:39Z · false · main · MIT SPDX from API; README and webhook/send/handoff source inspected.
8 mentions
oratis/influencex ↗
Strongest creator-specific workflow donor
Research evidence
- InfluenceX · Creator/KOL discovery, outreach approval flow, inbound replies, campaign management, ROI metrics, and a contract → content → payment lifecycle in one self-hostable app. It even exposes OpenAPI and has tests, making it unusually readable as a workflow donor. · Pattern donor for creator acquisition and campaign provenance. It is influencer marketing, not subscription-fan operations; keep HALO’s creator and money authority.
- oratis/influencex · https://github.com/oratis/influencex · 4 · MIT · 2026-08-09T15:23:13Z · false · main
- G23 · oratis/influencex · README describes a self-hostable MIT KOL marketing app: multi-platform discovery, email discovery, draft→review→approve→send outreach, inbound replies, ROI, contract→content→payment campaign state, background jobs, RBAC, OpenAPI, rate limits, export, and webhooks. · Highest-value creator-specific codebase found. Study or run a synthetic-data fork; do not import its scraping, outreach, or payment assumptions into production without platform terms, consent, rate-limit, and ledger review. · High for README-visible workflow; Medium for maturity
- 1 · oratis/influencex · Creator discovery, outreach draft → review → approve → send, inbound replies, campaign ROI, contract → content → payment state, OpenAPI and tests. · Best creator-specific pattern donor. Synthetic fork/read-only study only; scraping, outreach, rate limits and payment assumptions cannot bypass consent, platform terms or HALO money truth.
8 mentions
triggerdotdev/trigger.dev ↗
11 · Trigger.dev — triggerdotdev/trigger.dev · Durable background jobs, retries, AI extraction, approvals, Drive/voice/payment orchestration; journey 8 and supporting 2/3/5 · integrate · Apache-2.0 TypeScript SDK/platfor
Research evidence
- 11 · Trigger.dev — triggerdotdev/trigger.dev · Durable background jobs, retries, AI extraction, approvals, Drive/voice/payment orchestration; journey 8 and supporting 2/3/5 · integrate · Apache-2.0 TypeScript SDK/platform for long-running jobs and workflows. Use it only for work Convex cannot safely own; persist job IDs/statuses in Convex and make every external call idempotent. · Adds a workflow runtime beside Convex, which already has first-party workflow/workpool/action-retrier options in the prior lane. Run a probe before adding operational weight. · High
- triggerdotdev/trigger.dev · https://github.com/triggerdotdev/trigger.dev · 16,155 · Apache-2.0 · 2026-08-28T21:28:15Z · false · main · —
- 2 · triggerdotdev/trigger.dev · TypeScript AI workflows with retries, queues, idempotency, observability, checkpointing, schedules and human-in-the-loop waitpoints. · Strongest TypeScript proof candidate. Run synthetic approval/retry/outage tests; do not let a task worker become a money/permission authority. Buzz receives read-only run links or proposed actions. Apache-2.0. · README, license.
- triggerdotdev/trigger.dev · 16,155 · Apache-2.0 · 2026-08-29T08:29:41Z · false · main · README, LICENSE. TypeScript/HITL workflow spike.
7 mentions
devennn/senqo ↗
Senqo · Shared inbox, WhatsApp AI agents, reusable knowledge bases, scheduled messaging, CRM, and explicit manual takeover/human handoff in a self-hosted Docker product. · Study the agent/inbox boundary. Channel-specific
Research evidence
- Senqo · Shared inbox, WhatsApp AI agents, reusable knowledge bases, scheduled messaging, CRM, and explicit manual takeover/human handoff in a self-hosted Docker product. · Study the agent/inbox boundary. Channel-specific and very small; Buzz remains the selected collaboration plane and HALO controls sensitive actions.
- devennn/senqo · https://github.com/devennn/senqo · 9 · MIT · 2026-08-14T05:19:08Z · false · main
- 4 · Senqo; features, manual send, handoff notify · Explicit AI/human mode, manual takeover, verified teammate handoff notification, eval replay without send, knowledge/response templates and skills. · STUDY, synthetic eval donor · MIT per API metadata. WhatsApp credentials and transport are out of scope; fire-and-forget notification is not a proof of handoff acknowledgement. · High
- devennn/senqo · https://github.com/devennn/senqo · 9 · MIT · 2026-08-14T05:19:08Z · false · main · MIT SPDX from API; FEATURES.md and manual/handoff source inspected.
2 mentions
FLEXORA-Phegasis/Nexora-CRM-V2 ↗
Best Convex auth and RBAC donor
Research evidence
- 1 · Nexora CRM V2 — FLEXORA-Phegasis/Nexora-CRM-V2 · Multi-tenant creator/team CRM, role-scoped modules, organization membership, deals, tasks, calendar, audit; journeys 1, 2, 4, 7 · study · Closest project-specific Convex donor found. convex/lib/security.ts requires an opaque session and checks active user/org/domain; convex/lib/permissions.ts resolves server-side role/custom permissions and fails closed for unknown modules; scripts/smoke-permissions.mjs tests denied writes, not just UI hiding. · MIT. It still has its own users/session/schema and is only 421 files/1 star, so use it to harden HALO’s Convex auth/RBAC and smoke-test shape, not as a wholesale replacement. · High
- FLEXORA-Phegasis/Nexora-CRM-V2 · https://github.com/FLEXORA-Phegasis/Nexora-CRM-V2 · 1 · MIT · 2026-08-28T20:30:10Z · false · main · —
2 mentions
meisterfy/meisterfy ↗
Meisterfy · Agency-oriented multi-tenancy, social scheduling, paid-traffic management, AI content generation, reports, alerts, role management and an MCP endpoint. · Concept donor for an agency control plane. Early/low-s
Research evidence
- Meisterfy · Agency-oriented multi-tenancy, social scheduling, paid-traffic management, AI content generation, reports, alerts, role management and an MCP endpoint. · Concept donor for an agency control plane. Early/low-star and AGPL; do not adopt until its production maturity is proven.
- meisterfy/meisterfy · https://github.com/meisterfy/meisterfy · 1 · AGPL-3.0 · 2026-06-12T16:55:48Z · false · main
2 mentions
RocketChat/Rocket.Chat ↗
8 · Rocket.Chat (benchmark/fallback) · Discord-like realtime workspace with integrations, apps, federation and optional AI · Self-managed Docker/Kubernetes/Podman and cloud; REST, webhooks, Apps-Engine TypeScript apps, r
Research evidence
- 8 · Rocket.Chat (benchmark/fallback) · Discord-like realtime workspace with integrations, apps, federation and optional AI · Self-managed Docker/Kubernetes/Podman and cloud; REST, webhooks, Apps-Engine TypeScript apps, rooms and federation. MIT outside enterprise areas; separate enterprise licence. docs · integrations · deployment · licence · Benchmark/fallback only; Buzz is selected · High
- RocketChat/Rocket.Chat · https://github.com/RocketChat/Rocket.Chat · 46,041 · NOASSERTION · 2026-08-29T04:37:29Z · false · develop
1 mention
NationalSecurityAgency/skills-service ↗
1 · NationalSecurityAgency/skills-service · SkillTree-style micro-learning/gamification service: skills, progress, achievements and learning mechanics. · Study/rebuild the event and progression ideas; Apache-2.0 makes a
Research evidence
- 1 · NationalSecurityAgency/skills-service · SkillTree-style micro-learning/gamification service: skills, progress, achievements and learning mechanics. · Study/rebuild the event and progression ideas; Apache-2.0 makes a bounded adapter possible, but Java/service topology is too large to adopt wholesale.
19 mentions
twentyhq/twenty ↗
Strong CRM model; sidecar or study only
Research evidence
- 1 · Twenty · Salesforce-like relationship objects, timelines, workflows, roles, APIs and AI-oriented CRM · Study and run one bounded creator-relationship pilot · Strongest practical open AI/Salesforce-shaped system and closest TypeScript/React fit. It must not silently become a second creator authority; source is mostly AGPL with exceptions and enterprise-marked files.
- 3 · Twenty · Creator/contact relationship model, timelines, custom objects, workflows, dashboards · Standalone CRM with custom objects/fields, workflows, API/webhooks, permissions and AI concepts. Source is mostly AGPLv3 with application exception, enterprise-marked commercial files and MIT packages. capabilities · licence · Study; pilot as CRM sidecar only if relationship pain dominates · High
- twentyhq/twenty · https://github.com/twentyhq/twenty · 55,817 · NOASSERTION · 2026-08-29T07:27:29Z · false · main
- 1 · Twenty — twentyhq/twenty · Creator discovery, qualification, outreach, contact timeline, renewals; journeys 1, 2, 6 · integrate / sidecar · Customizable CRM objects and views, APIs, relationship history, and an AI-oriented CRM shell. Put creator/contact data behind a HALO-owned identity mapping; sync only explicit records/events over REST/GraphQL. · Mostly AGPLv3, with enterprise-marked commercial files and an application exception; its database/auth become a second source of truth if adopted wholesale. · High
16 mentions
nocobase/nocobase ↗
7 · NocoBase · Rapid internal tables, forms, workflows, permissions and admin surfaces · Plugin/data-source/workflow platform. Root source is a NocoBase License Agreement, not an OSI SPDX licence; commercial plugins/term
Research evidence
- 7 · NocoBase · Rapid internal tables, forms, workflows, permissions and admin surfaces · Plugin/data-source/workflow platform. Root source is a NocoBase License Agreement, not an OSI SPDX licence; commercial plugins/terms require legal review. Separate database/auth/UI create a second OS. licence · product · Bounded prototype/pattern donor; reject as central foundation · High on conflict; medium on fit
- nocobase/nocobase · https://github.com/nocobase/nocobase · 23,921 · NOASSERTION · 2026-08-29T01:20:59Z · false · main
- 15 · NocoBase — nocobase/nocobase · Multi-role portal forms, custom operational tables, approvals, lightweight CRM/ERP modules; journeys 2, 4, 5, 7 · study · TypeScript no-code/WYSIWYG business-system builder with plugin/data-source orientation. It is a useful test of whether HALO’s CRUD-heavy screens should become configurable modules. · The inspected LICENSE is a NocoBase License Agreement, not an SPDX open-source license; commercial/community/plugin boundaries and unilateral term changes require legal review. Never embed it by assumption. · Medium-high
- nocobase/nocobase · https://github.com/nocobase/nocobase · 23,921 · NOASSERTION · 2026-08-29T01:20:59Z · false · main · LICENSE: NocoBase License Agreement with community/commercial/plugin distinctions; not an SPDX open-source license.
14 mentions
activepieces/activepieces ↗
Guarded automation sidecar candidate
Research evidence
- Automation · Activepieces · Integrate/probe · Use for retryable onboarding, Drive, notification and approval plumbing. HALO validates and records all consequential commands. Core/enterprise license boundary must be respected.
- 3 · Activepieces — activepieces/activepieces · Onboarding triggers, Drive reconciliation notifications, approval gates, payment/CRM sync, exception routing; journeys 2, 3, 5, 8 · integrate · TypeScript visual workflows, reusable “pieces,” schedules/webhooks, and agent/MCP-oriented automation. Keep Convex mutations authoritative; use signed webhooks and idempotency keys at the boundary. · Core is MIT per the inspected LICENSE, but packages/ee and the EE server path have separate terms. Do not blindly copy EE code. · High
- activepieces/activepieces · https://github.com/activepieces/activepieces · 24,082 · NOASSERTION · 2026-08-28T22:40:53Z · false · main · LICENSE: non-EE content MIT Expat; packages/ee and EE server path have separate license.
- G15 · activepieces/activepieces · README presents a self-hosted MIT-core Zapier alternative with a TypeScript pieces ecosystem, AI pieces/MCP exposure, human-in-the-loop approvals, forms/chat interfaces, and technical/non-technical builder paths. · Integrate as a guarded automation sidecar. Its piece/event model can connect HALO and Buzz after idempotency and approval contracts exist; never let it become authorization or ledger truth. · High for stated features; High for core/EE license split
13 mentions
frappe/erpnext ↗
Strong finance and HR reference; bounded authority only
Research evidence
- 2 · ERPNext / Frappe · Accounting, invoicing, expenses, HR, attendance, payroll, CRM and projects · Back-office reference; isolated pilot only · Deepest coherent OSS back office. It earns financial authority only after synthetic/read-only reconciliation; its Python/Frappe datastore and ERP semantics are not HALO's creator-facing shell.
- frappe/erpnext · https://github.com/frappe/erpnext · 38,621 · GPL-3.0 · 2026-08-29T07:39:16Z · false · develop
- 9 · ERPNext — frappe/erpnext · Accounting, invoices, expenses, liabilities, procurement, HR, projects; journeys 4 and 5, with supporting 2 · study / sidecar · Mature integrated ERP modules and financial-reporting concepts. Use it to pressure-test HALO’s ledger, payout, and audit requirements; a narrowly scoped finance sidecar is conceivable. · GPL-3.0, Python/Frappe/MariaDB stack, broad schema ownership, and a second auth/data model. Wholesale adoption would erase HALO’s creator-specific workflows. · High
- frappe/erpnext · https://github.com/frappe/erpnext · 38,621 · GPL-3.0 · 2026-08-29T07:39:16Z · false · develop · —
9 mentions
Vexa-ai/vexa ↗
Meeting evidence capture sidecar
Research evidence
- Meeting capture · Vexa · Integrate/probe · Capture Google Meet/Teams/Zoom transcripts and speaker evidence after consent; a human-approved summary becomes a HALO decision/action. Buzz receives the discussion link, not an unrestricted transcript dump.
- 2 · Vexa — Vexa-ai/vexa · Meeting capture, transcription, speaker attribution, follow-up evidence; journeys 1, 6, 8 · integrate · Bots join Google Meet, Teams, and Zoom; real-time WebSocket transcripts; API and MCP surface; self-hostable. Store transcript/decision artifacts in HALO after consent and retention checks. · Separate Python service and browser-automation/provider failure modes; consent and meeting access must be first-class. · High
- Vexa-ai/vexa · https://github.com/Vexa-ai/vexa · 2,726 · Apache-2.0 · 2026-08-28T15:53:32Z · false · main · —
- 3 · Vexa-ai/vexa · Meeting bots, speaker-attributed transcription, API/self-hosting, and a file-owned knowledge path. · Optional consented meeting-capture adapter. Raw recording/transcript belongs to the approved capture/retention boundary; only human-confirmed decisions/actions enter HALO and Buzz gets a typed link. Apache-2.0. · README, license.
9 mentions
windmill-labs/windmill ↗
G16 · windmill-labs/windmill · README presents an AGPL developer platform for APIs, background jobs, workflows, and autogenerated/custom UIs, with scripts in multiple languages, self-hosting, and SSO/SMTP/security sectio
Research evidence
- G16 · windmill-labs/windmill · README presents an AGPL developer platform for APIs, background jobs, workflows, and autogenerated/custom UIs, with scripts in multiple languages, self-hosting, and SSO/SMTP/security sections. · Automation/internal-tool sidecar. It is a powerful execution substrate for approved back-office jobs, not a creator record or business system; retain server-side authority in HALO. · High for execution model
- windmill-labs/windmill · https://github.com/windmill-labs/windmill · 17,713 · NOASSERTION · 2026-08-29T07:54:29Z · false · main
- - Windmill LICENSE-AGPL
- 7 · windmill-labs/windmill · Scripts, flows, jobs, triggers and operational automation. · Reject as the default public/commercial workflow base. Root source mixes Apache/AGPL/commercial terms and prohibits selling/reselling/managed/wrapped community use without agreement. Study concepts only. · README, license boundary.
8 mentions
lightdash/lightdash ↗
1 · lightdash/lightdash · Governed metrics/dimensions/joins, permissions, caching, Git/CI, data apps, AI agents and MCP over a semantic layer. · BI sidecar/proof candidate. Metric definitions remain versioned owner artif
Research evidence
- 1 · lightdash/lightdash · Governed metrics/dimensions/joins, permissions, caching, Git/CI, data apps, AI agents and MCP over a semantic layer. · BI sidecar/proof candidate. Metric definitions remain versioned owner artifacts; Lightdash is a read model and query surface, never a ledger. Root non-EE code is MIT; EE production code requires an Enterprise Subscription. · README, root license, EE license, semantic-layer docs.
- lightdash/lightdash · 6,102 · NOASSERTION · 2026-08-28T23:24:17Z · false · main · README; actual root LICENSE says outside backend EE is MIT, while packages/backend/src/ee/LICENSE requires an Enterprise Subscription for production. BI sidecar only.
8 mentions
melgarafael/DeskcommCRM ↗
Strong AI-to-human conversation pattern
Research evidence
- DeskcommCRM · The closest open-source “sell by chat” operating model: multi-tenant CRM, AI agents with per-tenant RAG, first-class AI/human handoff, audited assignment/transfer, queue position, role visibility, event-log automations, MCP direction, and a self-hosted stack. Its current channel is WhatsApp, not OnlyFans. · Study and selectively lift patterns. Borrow the assignment/queue, event-log, handoff, audit, tenant isolation and agent-tool concepts; do not merge its channel or datastore into HALO/Buzz.
- melgarafael/DeskcommCRM · https://github.com/melgarafael/DeskcommCRM · 726 · MIT · 2026-08-29T01:11:16Z · false · main
- 1 · DeskcommCRM; claim route, transfer route, draft route, follow-up queue · Transactional claim/transfer, org scoping, audit/activity, bot silence, human-review draft, promise/follow-up queue, explicit escalation actions. · STUDY/adapt state machine · MIT per API metadata. Pattern only; do not copy a whole CRM or assume its auth/tenant model fits HALO. No Buzz duplication. · High for cited source behavior
- melgarafael/DeskcommCRM · https://github.com/melgarafael/DeskcommCRM · 726 · MIT · 2026-08-29T01:11:16Z · false · main · MIT SPDX from API; source routes cited above inspected for claim/transfer/draft/follow-up behavior.
8 mentions
openfga/openfga ↗
2 · OpenFGA · Apache-2.0 relationship-based authorization with authorization models, tuples and permission checks. · Comparable access-policy spike. Pick one authorization model for a bounded proof; never run both as com
Research evidence
- 2 · OpenFGA · Apache-2.0 relationship-based authorization with authorization models, tuples and permission checks. · Comparable access-policy spike. Pick one authorization model for a bounded proof; never run both as competing truth.
- openfga/openfga · https://github.com/openfga/openfga · 5,674 · Apache-2.0 · 2026-08-28T18:50:19Z · false · main
- 1 · openfga/openfga · Zanzibar-inspired fine-grained authorization engine with HTTP/gRPC APIs, storage backends and authorization-model testing. · Integrate/probe for resource and relationship authorization. It is a policy decision point, not an identity provider, audit ledger, or substitute for tenant/server identity. Apache-2.0. · README, license.
- openfga/openfga · 5,674 · Apache-2.0 · 2026-08-28T18:50:19Z · false · main · README, LICENSE. Authorization PDP spike.
7 mentions
chatwoot/chatwoot ↗
G20 · chatwoot/chatwoot · README describes a self-hosted omnichannel support platform with a shared inbox, contact profiles/history, segments, campaigns, teams, automation, capacity management, help-center portal, and an
Research evidence
- G20 · chatwoot/chatwoot · README describes a self-hosted omnichannel support platform with a shared inbox, contact profiles/history, segments, campaigns, teams, automation, capacity management, help-center portal, and an AI support agent. · External conversation sidecar only. It is a strong inbox/relationship pattern for lawful support workflows, but not creator identity, consent, contract, or OFM revenue truth; core MIT and enterprise separation still require review. · High for feature/boundary
- chatwoot/chatwoot · https://github.com/chatwoot/chatwoot · 36,287 · NOASSERTION · 2026-08-29T07:34:40Z · false · develop
- - Chatwoot LICENSE makes
- 6 · Chatwoot · Mature omnichannel support, contacts/history, teams, labels, automation, AI agent and shared inbox patterns. · STUDY; conditional integrate · NOASSERTION API value; actual root LICENSE is MIT Expat outside enterprise/, while enterprise/LICENSE applies separate production subscription/enterprise terms. Do not assume the enterprise tree is MIT. · High for license boundary
7 mentions
mattermost/mattermost ↗
9 · Mattermost (benchmark/fallback) · Secure team chat, channels, playbooks/boards and workflow integrations · Self-hostable, but source licensing splits MIT compiled versions, AGPLv3 or commercial source, and Apache-2.0
Research evidence
- 9 · Mattermost (benchmark/fallback) · Secure team chat, channels, playbooks/boards and workflow integrations · Self-hostable, but source licensing splits MIT compiled versions, AGPLv3 or commercial source, and Apache-2.0 admin/config areas. channels · licence · Benchmark/fallback only; do not replace Buzz · High
- mattermost/mattermost · https://github.com/mattermost/mattermost · 38,937 · NOASSERTION · 2026-08-29T06:43:15Z · false · master
- 14 · Mattermost — mattermost/mattermost · Secure team chat, handoffs, incident/exception threads, workflow notifications; journeys 1, 4, 6, 7, 8 · buy / integrate · Single-binary Go + React + PostgreSQL collaboration platform with chat, workflow automation, calls, screen sharing, and AI integration. Hosted/commercial deployment may be cheaper than building messaging. · Open-core licensing: compiled versions MIT, source generally AGPLv3 or commercial, with Apache-covered admin/config paths. It is a second product with its own identity/search/retention model. · High
- mattermost/mattermost · https://github.com/mattermost/mattermost · 38,937 · NOASSERTION · 2026-08-29T06:43:15Z · false · master · LICENSE: compiled platform MIT; source generally AGPLv3 or commercial; admin/config paths Apache-2.0.
7 mentions
operately/operately ↗
G4 · operately/operately · README describes an open-source company OS with goals/OKRs, projects, team spaces, message boards, documents/files, team management/permissions, check-ins, CLI/API, and agent skills. · Study or
Research evidence
- G4 · operately/operately · README describes an open-source company OS with goals/OKRs, projects, team spaces, message boards, documents/files, team management/permissions, check-ins, CLI/API, and agent skills. · Study or bounded team-ops sidecar. Its cadence/check-in model is useful for owner and manager operating rhythms; it does not supply creator, contract, consent, or money truth. · High for stated workflow; Medium for HALO fit
- operately/operately · https://github.com/operately/operately · 545 · NOASSERTION · 2026-08-29T01:31:42Z · false · main
- - Operately LICENSE: the
- 11 · Operately · Goals, projects, team spaces, check-ins, messages/docs and manager cadence patterns. · STUDY manager-cadence pattern · NOASSERTION; actual root LICENSE is Apache-2.0 while ee/LICENSE is paid/enterprise-restricted. Not chatter-specific; no inbox duplication. · High for license caution
6 mentions
alongot/creator-crm ↗
creator-crm and CreatorReach AI · Small, focused examples of creator discovery, AI fit scoring, campaign/outreach tracking, Gmail draft automation, reply classification and follow-up. · Study only. Useful for discovery v
Research evidence
- creator-crm and CreatorReach AI · Small, focused examples of creator discovery, AI fit scoring, campaign/outreach tracking, Gmail draft automation, reply classification and follow-up. · Study only. Useful for discovery vocabulary and human-reviewed outreach, not a multi-persona foundation.
- alongot/creator-crm · https://github.com/alongot/creator-crm · 7 · MIT · 2026-06-25T18:01:23Z · false · main
- G25 · alongot/creator-crm · README calls it a self-hostable creator/influencer CRM template with a 10-stage pipeline, roster, candidate queue, heuristic/AI fit scoring, outreach drafts, activity timeline, stage-generated tasks, and optional Resend/Apify/Claude integrations. · Small pattern donor. The stage transition→task rule and candidate review queue are useful; the README itself calls it a template with fictional data, so it is not a production replacement. · High for pattern; Low/Medium for maturity
- 2 · alongot/creator-crm · Ten-stage creator pipeline, roster, candidate review queue, fit scoring, outreach drafts, activity timeline and stage-created tasks; README calls it a template with fictional seed data. · Small pattern donor. Reuse vocabulary and stage→task behavior conceptually, not as a production replacement.
6 mentions
getzep/graphiti ↗
1 · getzep/graphiti · Temporal context graph with validity windows, structured/unstructured ingestion, hybrid retrieval and graph traversal. · Integrate/probe after ACL and retention tests. Use for decision/action/entity
Research evidence
- 1 · getzep/graphiti · Temporal context graph with validity windows, structured/unstructured ingestion, hybrid retrieval and graph traversal. · Integrate/probe after ACL and retention tests. Use for decision/action/entity context and historical “what was true then,” with source IDs and permission filters; never authorize or overwrite domain truth. Apache-2.0. · README, license.
- getzep/graphiti · 30,393 · Apache-2.0 · 2026-08-29T06:15:05Z · false · main · README, LICENSE. Temporal knowledge-graph spike.
6 mentions
javers/javers ↗
3 · javers/javers · Java object change auditing with commit metadata, author, timestamps and repository integration. · Pattern donor, not a HALO runtime dependency. It shows field/object diff and commit metadata; HALO ne
Research evidence
- 3 · javers/javers · Java object change auditing with commit metadata, author, timestamps and repository integration. · Pattern donor, not a HALO runtime dependency. It shows field/object diff and commit metadata; HALO needs a cross-service append-only audit contract and retention/export, not a second Java service. Apache-2.0. · README, license.
- javers/javers · 1,573 · Apache-2.0 · 2026-08-17T11:37:50Z · false · master · README, LICENSE. Audit-diff pattern.
6 mentions
kestra-io/kestra ↗
4 · kestra-io/kestra · Event/schedule orchestration, declarative YAML, plugins, retries, branching, backfills and UI/API. · Study/sidecar only if non-developer workflow authoring proves valuable. Its own workflow/UI/data
Research evidence
- 4 · kestra-io/kestra · Event/schedule orchestration, declarative YAML, plugins, retries, branching, backfills and UI/API. · Study/sidecar only if non-developer workflow authoring proves valuable. Its own workflow/UI/datastore would be extra operational surface; HALO commands still own business truth. Apache-2.0. · README, license.
- kestra-io/kestra · 27,946 · Apache-2.0 · 2026-08-28T16:05:52Z · false · develop · README, LICENSE. Declarative orchestration study.
6 mentions
mem0ai/mem0 ↗
2 · mem0ai/mem0 · User/session/agent memory, semantic/BM25/entity retrieval, temporal reasoning and self-hosted server options. · Integrate only for least-copy summaries. Memory must be scoped by tenant/persona/retention
Research evidence
- 2 · mem0ai/mem0 · User/session/agent memory, semantic/BM25/entity retrieval, temporal reasoning and self-hosted server options. · Integrate only for least-copy summaries. Memory must be scoped by tenant/persona/retention and must cite the source record; no sensitive credential, contract, or raw fan-history dump. Apache-2.0. · README, license.
- mem0ai/mem0 · 64,293 · Apache-2.0 · 2026-08-28T18:02:50Z · false · main · README, LICENSE. Permission-filtered memory spike.
6 mentions
metabase/metabase ↗
3 · metabase/metabase · Dashboards, permissions, API, transforms and canonical metric concepts. · Buy/sidecar or study; do not make it the owner control plane. Root source splits AGPL open-source paths from commercial en
Research evidence
- 3 · metabase/metabase · Dashboards, permissions, API, transforms and canonical metric concepts. · Buy/sidecar or study; do not make it the owner control plane. Root source splits AGPL open-source paths from commercial enterprise paths, and it is dashboard/query first rather than exception/action first. · README, license boundary.
- metabase/metabase · 48,983 · NOASSERTION · 2026-08-29T07:58:04Z · false · master · README; actual LICENSE.txt says non-enterprise source is AGPL and enterprise paths/commercial binaries use the Metabase Commercial License. Buy/sidecar or study.
6 mentions
temporalio/temporal ↗
1 · temporalio/temporal · Durable workflow execution, retries, resilient state and a workflow UI; broadest correctness reference. · Integrate/probe after the trust gate. Temporal may own workflow execution state, timers,
Research evidence
- 1 · temporalio/temporal · Durable workflow execution, retries, resilient state and a workflow UI; broadest correctness reference. · Integrate/probe after the trust gate. Temporal may own workflow execution state, timers, retries and resume; HALO domain services remain authoritative for business mutations. Buzz can surface status and approvals through the adapter. MIT. · README, license, official docs.
- temporalio/temporal · 22,591 · MIT · 2026-08-28T23:45:54Z · false · main · README, LICENSE. Durable execution spike.
5 mentions
zulip/zulip ↗
zulip/zulip · https://github.com/zulip/zulip · 25,786 · Apache-2.0 · 2026-08-28T03:24:40Z · false · main
Research evidence
- zulip/zulip · https://github.com/zulip/zulip · 25,786 · Apache-2.0 · 2026-08-28T03:24:40Z · false · main
- 4 · Zulip — zulip/zulip · Chatter-team handoffs, topic-scoped creator/team conversations, async follow-ups; journey 6 and parts of 1/4 · integrate / buy · Topic-based threading is a strong fit for creator, campaign, and handoff context; it supports live and asynchronous communication. Use HALO IDs in message metadata and keep money/permissions in Convex. · Full Python/PostgreSQL chat product; duplicated users, search, retention, and notification policy. Only pursue if unified inbox/chat earns product approval. · High
- zulip/zulip · https://github.com/zulip/zulip · 25,786 · Apache-2.0 · 2026-08-28T03:24:40Z · false · main · —
- G14 · zulip/zulip · README describes Apache-2.0, self-hostable organized team chat with topic-based threading for live and asynchronous conversations, public cloud, and a large contributor base. · Study topic-thread/handoff patterns; reject as a second core chat. Buzz remains fixed; only stable event/link patterns are worth borrowing. · High for communication pattern
4 mentions
directus-labs/agency-os ↗
2 · AgencyOS — directus-labs/agency-os · Client-facing project portal, projects/tasks/files/invoices, project templates, client accountability; journeys 1, 2, 3, 5 · study · Actual Nuxt 3 + Directus project with CRM/proj
Research evidence
- 2 · AgencyOS — directus-labs/agency-os · Client-facing project portal, projects/tasks/files/invoices, project templates, client accountability; journeys 1, 2, 3, 5 · study · Actual Nuxt 3 + Directus project with CRM/project tracker and private authenticated portal. README/source paths include portal project/task/file/billing pages and invoice calculation scripts. This is the most direct client-portal donor in the API pass. · MIT, but GitHub API says last push 2026-03-06 and the README retains older clone/deploy references. Directus/PostgreSQL becomes a second datastore; use the portal contract and task/invoice relationships as patterns. · High
- directus-labs/agency-os · https://github.com/directus-labs/agency-os · 971 · MIT · 2026-03-06T00:04:00Z · false · main · —
- G10 · directus-labs/agency-os · Directus/NuxtLabs' README calls it an open-source AgencyOS: a hackable digital-agency operating-system example with a website/CMS and agency tooling, plus a public demo. · Strong agency-pattern donor; prototype only. It is one of the rare repositories named for the actual agency job, but it is far less mature than the platform it demonstrates and should not become a second HALO authority. · High for intended pattern; Medium for freshness
- directus-labs/agency-os · https://github.com/directus-labs/agency-os · 971 · MIT · 2026-03-06T00:04:00Z · false · main
4 mentions
documenso/documenso ↗
G27 · documenso/documenso · README describes a self-hostable AGPL open-source DocuSign alternative with digital signatures, audit-minded trust positioning, APIs, Stripe integration, and separate enterprise services. · Co
Research evidence
- G27 · documenso/documenso · README describes a self-hostable AGPL open-source DocuSign alternative with digital signatures, audit-minded trust positioning, APIs, Stripe integration, and separate enterprise services. · Contract-signing sidecar/pattern donor. Keep signed-document identity, consent evidence, version, signer, and revocation/export links in HALO; do not make a signature provider the contract authority. · High for stated scope
- documenso/documenso · https://github.com/documenso/documenso · 14,797 · AGPL-3.0 · 2026-08-29T06:12:11Z · false · main
- 2 · Documenso · AGPL self-hostable signing platform with API/webhook/embed and separate enterprise paths. · Pattern/sidecar candidate, not embedded HALO code. Verify signing certificate, webhook replay, retention and export before any pilot.
- documenso/documenso · https://github.com/documenso/documenso · 14,797 · AGPL-3.0 · 2026-08-29T08:09:26Z · false · main
4 mentions
itflow-org/itflow ↗
G11 · itflow-org/itflow · README presents a self-hostable documentation, ticketing, and accounting system for service businesses, with client documentation/assets/contacts/domains/files/passwords, quotes/invoices/expense
Research evidence
- G11 · itflow-org/itflow · README presents a self-hostable documentation, ticketing, and accounting system for service businesses, with client documentation/assets/contacts/domains/files/passwords, quotes/invoices/expenses, and a client portal. · Best adjacent PSA model. Study its client record, documentation, billing, and portal boundaries; integrate only a narrow pattern because its MSP orientation and GPL-3.0 license do not map directly to HALO. · High for scope; Medium for OFM fit
- itflow-org/itflow · https://github.com/itflow-org/itflow · 991 · GPL-3.0 · 2026-08-29T04:59:57Z · false · master
- 4 · ITFlow · GPL-3.0 service-business documentation, contacts, files, passwords, billing and client self-service portal. · Portal/offboarding pattern study; reject as a drop-in. MSP orientation, GPL boundary and password semantics do not map to creator authority.
4 mentions
makeplane/plane ↗
10 · Plane · Projects, issues, cycles, pages and content execution views · Standalone app with API/self-hosting; AGPL-3.0 repo. Useful for production coordination, but not creator relationships, money, chat or compliance
Research evidence
- 10 · Plane · Projects, issues, cycles, pages and content execution views · Standalone app with API/self-hosting; AGPL-3.0 repo. Useful for production coordination, but not creator relationships, money, chat or compliance. docs · repo · Bounded pattern donor; integrate only if content execution outgrows HALO · Medium-high
- makeplane/plane · https://github.com/makeplane/plane · 58,488 · AGPL-3.0 · 2026-08-28T14:23:41Z · false · preview
- G12 · makeplane/plane · README exposes project work items, cycles, modules, views, rich pages with AI, and analytics, with cloud and self-host options. · Content/team-ops sidecar or pattern study. Good for production boards and reusable pages; it cannot own creators, consent, money, or external portal identity. · High for project primitives
- makeplane/plane · https://github.com/makeplane/plane · 58,491 · AGPL-3.0 · 2026-08-28T14:23:41Z · false · preview
4 mentions
zavudev/zavu-inbox ↗
Strong source-of-truth boundary pattern
Research evidence
- Zavu Inbox · A precise source-of-truth pattern: the channel provider owns messages, contacts, senders, delivery, compliance and AI; the inbox owns assignment, open/done state, notes, tasks, snippets and user actions. It uses webhooks plus a rebuildable local mirror. · Use as an integration pattern, not a product dependency. This is especially relevant to Buzz/HALO: mirror operational state without pretending the collaboration layer owns platform truth.
- zavudev/zavu-inbox · https://github.com/zavudev/zavu-inbox · 0 · Apache-2.0 · 2026-08-20T16:18:22Z · false · main
- 3 · Zavu Inbox · Clean provider/app split: Zavu owns messages, contacts, senders, delivery, compliance and AI; local app owns users/workspace state and rebuildable mirror; HMAC/freshness and no privileged path. · STUDY/adapt authority boundary · Apache-2.0 per API metadata and root README. Its provider is not HALO; use the rebuildable-mirror contract and webhook discipline. Buzz should remain separate. · High
- zavudev/zavu-inbox · https://github.com/zavudev/zavu-inbox · 0 · Apache-2.0 · 2026-08-20T16:18:22Z · false · main · Apache-2.0 SPDX and root README boundary inspected.
3 mentions
cgwire/kitsu ↗
Strong content-production pattern donor
Research evidence
- Content production · Kitsu + Zou · Study or API-level sidecar · Best adjacent production model for briefs, versions, status, deliveries and approvals. Keep HALO's Drive provenance and creator model authoritative.
- 6 · Kitsu + Zou — cgwire/kitsu, cgwire/zou · Briefs, assets, versions, production status, deliveries, approvals, and stakeholder communication; journey 3 · study / sidecar · Kitsu is a collaboration platform for animation/VFX/video-game productions; Zou supplies its production-data API. The delivery/version/status model is a better donor for creator content operations than a generic task board. · AGPLv3 and a separate Vue/Python production stack. Use API-level sidecar experiments or copy domain ideas, not a direct Convex embed. · High
- cgwire/kitsu · https://github.com/cgwire/kitsu · 702 · AGPL-3.0 · 2026-08-28T09:03:27Z · false · main · —
3 mentions
cgwire/zou ↗
Strong content-production API donor
Research evidence
- Content production · Kitsu + Zou · Study or API-level sidecar · Best adjacent production model for briefs, versions, status, deliveries and approvals. Keep HALO's Drive provenance and creator model authoritative.
- 6 · Kitsu + Zou — cgwire/kitsu, cgwire/zou · Briefs, assets, versions, production status, deliveries, approvals, and stakeholder communication; journey 3 · study / sidecar · Kitsu is a collaboration platform for animation/VFX/video-game productions; Zou supplies its production-data API. The delivery/version/status model is a better donor for creator content operations than a generic task board. · AGPLv3 and a separate Vue/Python production stack. Use API-level sidecar experiments or copy domain ideas, not a direct Convex embed. · High
- cgwire/zou · https://github.com/cgwire/zou · 198 · AGPL-3.0 · 2026-08-28T09:02:04Z · false · main · —
3 mentions
frappe/hrms ↗
10 · Frappe HR — frappe/hrms · Employee records, onboarding, leave, attendance, payroll, and HR reporting; journey 4 · study / sidecar · Concrete HRMS coverage, including the exact operations currently split between Supa
Research evidence
- 10 · Frappe HR — frappe/hrms · Employee records, onboarding, leave, attendance, payroll, and HR reporting; journey 4 · study / sidecar · Concrete HRMS coverage, including the exact operations currently split between Supabase payroll components and the orphaned Convex payroll module. Compare its approval and payroll data model before continuing bespoke work. · GPL-3.0 and Frappe dependency; not a TypeScript/Convex module. A sidecar requires identity, payroll-period, and worker-record reconciliation. · High
- frappe/hrms · https://github.com/frappe/hrms · 8,695 · GPL-3.0 · 2026-08-28T11:27:56Z · false · develop · —
- frappe/hrms · https://github.com/frappe/hrms · 8,695 · GPL-3.0 · 2026-08-28T11:27:56Z · false · develop · Re-platform decision only
3 mentions
inovector/mixpost ↗
Publishing · Mixpost · Bounded sidecar if required · Own provider tokens, schedules and retries only; HALO owns brief, approval, asset, creator and provenance. Verify provider freshness first.
Research evidence
- Publishing · Mixpost · Bounded sidecar if required · Own provider tokens, schedules and retries only; HALO owns brief, approval, asset, creator and provenance. Verify provider freshness first.
- 8 · Mixpost — inovector/mixpost · Content calendar, scheduled publishing, channel operations, publishing status; journey 3 · integrate · MIT social-media management platform with scheduling and publishing. A sidecar can own platform-specific tokens and publishing retries while HALO owns briefs, approvals, creator relationships, and provenance. · Laravel/Vue application; last verified push was 2026-03-16, materially older than the other finalists. Verify provider API compatibility before committing. · Medium-high
- inovector/mixpost · https://github.com/inovector/mixpost · 3,554 · MIT · 2026-03-16T10:06:38Z · false · main · —
3 mentions
langgenius/dify ↗
G18 · langgenius/dify · README describes an AI app-development platform with visual workflows, model management, RAG pipelines, agent capabilities, observability, self-hosting, and many model/tool integrations. · AI work
Research evidence
- G18 · langgenius/dify · README describes an AI app-development platform with visual workflows, model management, RAG pipelines, agent capabilities, observability, self-hosting, and many model/tool integrations. · AI workflow sidecar/pattern study. Its actual modified Apache license prohibits operating a multi-tenant environment without authorization and imposes frontend/logo conditions, which directly conflicts with treating it as HALO's SaaS core. · High for capability and restriction
- langgenius/dify · https://github.com/langgenius/dify · 153,794 · NOASSERTION · 2026-08-29T07:31:42Z · false · main
- - Dify LICENSE is a modified
3 mentions
Leon-bo-He/Orbit ↗
Strong planned-versus-published content donor
Research evidence
- 6 · Orbit — Leon-bo-He/Orbit · Ideas → brief → production → review → publish, multi-vertical workspaces, scheduling gaps, per-platform publication records, metrics; journey 3 · study · MIT TypeScript app with 316 files, explicit stage-history migration, workspace isolation, brief sections, per-platform records, gap alerts, JSON import/export, BullMQ, and integration/unit tests. It models planned content separately from platform publication records. · API says last push 2026-05-13 and collaboration/RBAC is planned, so it is not a ready multi-user sidecar. Excellent content-state/provenance donor. · High
- Leon-bo-He/Orbit · https://github.com/Leon-bo-He/Orbit · 61 · MIT · 2026-05-13T21:32:23Z · false · master · —
- 1 · Leon-bo-He/Orbit · Creator content operations: ideas, AI briefs, Kanban lifecycle, calendar, publishing records, analytics, JSON portability. · STUDY; build the rights-aware subset · MIT; 61 stars; pushed 2026-05-13T21:32:23Z; not archived; default master. · Closest public workflow shape, but README says collaboration/RBAC is planned and it is not adult-rights aware. Do not duplicate its whole app; extract state vocabulary. Buzz may link work-item IDs only.
3 mentions
mautic/mautic ↗
G21 · mautic/mautic · README describes GPLv3 open-source marketing automation with self-hosting, database ownership, multichannel campaigns, segmentation, and automation. · Outreach/campaign sidecar or study. Useful for
Research evidence
- G21 · mautic/mautic · README describes GPLv3 open-source marketing automation with self-hosting, database ownership, multichannel campaigns, segmentation, and automation. · Outreach/campaign sidecar or study. Useful for consented recruiting nurture and reactivation, not for sending as a creator or replacing HALO's communication authority. · High for stated scope
- mautic/mautic · https://github.com/mautic/mautic · 10,414 · NOASSERTION · 2026-08-28T14:37:48Z · false · 7.x
- - Mautic LICENSE.txt states GPLv3
3 mentions
odoo/odoo ↗
G7 · odoo/odoo · README lists open-source CRM, website/e-commerce, projects, billing/accounting, HR, marketing, manufacturing, and integrated apps. · Full ERP re-platform option only. It is too broad to be a casual sidec
Research evidence
- G7 · odoo/odoo · README lists open-source CRM, website/e-commerce, projects, billing/accounting, HR, marketing, manufacturing, and integrated apps. · Full ERP re-platform option only. It is too broad to be a casual sidecar and still lacks HALO-specific creator consent, rights, platform access, and referral semantics. · High for breadth; Medium for fit
- odoo/odoo · https://github.com/odoo/odoo · 54,021 · NOASSERTION · 2026-08-29T08:04:32Z · false · 19.0
- - Odoo LICENSE: Odoo is LGPLv3, with
3 mentions
OpenSignLabs/OpenSign ↗
3 · OpenSign · API, templates, multi-signer sequencing, expiring documents, rejection reason, audit trail and completion certificate in README. · Study/isolated sidecar only. Root source is AGPL despite the API's NOASSER
Research evidence
- 3 · OpenSign · API, templates, multi-signer sequencing, expiring documents, rejection reason, audit trail and completion certificate in README. · Study/isolated sidecar only. Root source is AGPL despite the API's NOASSERTION metadata; do not treat it as permissive.
- OpenSignLabs/OpenSign · https://github.com/OpenSignLabs/OpenSign · 6,931 · NOASSERTION · 2026-08-21T12:29:09Z · false · staging
- - OpenSign LICENSE:
3 mentions
qdrant/qdrant ↗
Search/RAG · Qdrant plus QMD patterns · Integrate only after ACL probe · Index redacted, authorized chunks with immutable source IDs and return citations. Retrieval never becomes authorization.
Research evidence
- Search/RAG · Qdrant plus QMD patterns · Integrate only after ACL probe · Index redacted, authorized chunks with immutable source IDs and return citations. Retrieval never becomes authorization.
- 7 · Qdrant — qdrant/qdrant · Semantic retrieval over creator history, meeting notes, contracts, briefs, and Drive provenance; journeys 1, 2, 3, 6, 8 · integrate · Apache-2.0 vector database with a clear service boundary. Index only redacted/authorized chunks, retain source IDs and ACL filters, and return citations to HALO records. · Rust service and a second index to operate; vector ACLs must never replace Convex authorization. · High
- qdrant/qdrant · https://github.com/qdrant/qdrant · 34,252 · Apache-2.0 · 2026-08-29T06:48:24Z · false · master · —
3 mentions
tobi/qmd ↗
Search/RAG · Qdrant plus QMD patterns · Integrate only after ACL probe · Index redacted, authorized chunks with immutable source IDs and return citations. Retrieval never becomes authorization.
Research evidence
- Search/RAG · Qdrant plus QMD patterns · Integrate only after ACL probe · Index redacted, authorized chunks with immutable source IDs and return citations. Retrieval never becomes authorization.
- 12 · QMD — tobi/qmd · Search meeting notes, SOPs, briefs, and exported Drive material; journeys 1, 3, 6, 8 · integrate / study · MIT local search engine combining BM25, vector search, query expansion, reciprocal-rank fusion, and LLM reranking. Start with an export/index worker and citations; do not expose its local index as an authorization layer. · CLI/local Node application rather than a multi-tenant Convex component; model/runtime footprint and per-user isolation need a proof. · High
- tobi/qmd · https://github.com/tobi/qmd · 29,335 · MIT · 2026-08-18T14:26:31Z · false · main · —
2 mentions
achref-soua/helio ↗
Helio · AI-native growth platform with segmentation, cross-channel journeys, analytics, encrypted credentials, audit/control-room ideas, backups/restore, scoped API keys and BYO models. · Security/automation pattern dono
Research evidence
- Helio · AI-native growth platform with segmentation, cross-channel journeys, analytics, encrypted credentials, audit/control-room ideas, backups/restore, scoped API keys and BYO models. · Security/automation pattern donor. Its broad README claims need adversarial verification; do not use it as a source of financial or creator truth.
- achref-soua/helio · https://github.com/achref-soua/helio · 4 · AGPL-3.0 · 2026-06-29T20:17:04Z · false · main
2 mentions
docmost/docmost ↗
G19 · docmost/docmost · README describes an AGPL collaborative wiki/documentation system with real-time collaboration, spaces, groups, permissions, comments, history, search, attachments, and diagrams; enterprise paths a
Research evidence
- G19 · docmost/docmost · README describes an AGPL collaborative wiki/documentation system with real-time collaboration, spaces, groups, permissions, comments, history, search, attachments, and diagrams; enterprise paths are separately licensed. · Knowledge/SOP sidecar or study. Better aligned than a generic wiki for scoped team knowledge, but HALO should retain source links, access policy, and export authority. · High for stated features
- docmost/docmost · https://github.com/docmost/docmost · 21,505 · AGPL-3.0 · 2026-08-28T22:05:39Z · false · main
2 mentions
gavinedwardbrooks-zjc/KOLConnect ↗
8 · KOLConnect — gavinedwardbrooks-zjc/KOLConnect · Creator/account normalization, campaign collaboration, planned vs actual publishing, import/export, dedup/merge/delete safety; journeys 2, 3, 5, 7 · study · MIT desktop
Research evidence
- 8 · KOLConnect — gavinedwardbrooks-zjc/KOLConnect · Creator/account normalization, campaign collaboration, planned vs actual publishing, import/export, dedup/merge/delete safety; journeys 2, 3, 5, 7 · study · MIT desktop app with 376 files. Source has normalized Creator → one-to-many CreatorAccount, manual merge with preview fingerprint/lock, mutation-free delete planning, and explicit separation of planned collaboration from actual publication evidence. · Local SQLite/Windows desktop and Feishu integration; not a web sidecar. Its data-authority and deletion-plan discipline is highly relevant to HALO’s Drive/creator integrity. · High
- gavinedwardbrooks-zjc/KOLConnect · https://github.com/gavinedwardbrooks-zjc/KOLConnect · 13 · MIT · 2026-08-28T03:07:27Z · false · main · —
1 mention
argilla-io/argilla ↗
4 · argilla-io/argilla · Human feedback, annotation, continuous evaluation and dataset review. · Integrate as a calibration/evaluator sidecar or study; Apache-2.0. HALO retains rubric and score truth.
Research evidence
- 4 · argilla-io/argilla · Human feedback, annotation, continuous evaluation and dataset review. · Integrate as a calibration/evaluator sidecar or study; Apache-2.0. HALO retains rubric and score truth.
1 mention
comet-ml/opik ↗
7 · comet-ml/opik · Tracing, datasets, LLM-as-judge/evaluation and production monitoring patterns. · Study/integrate only for redacted evaluator telemetry; Apache-2.0. Never use an LLM judge as the sole certification aut
Research evidence
- 7 · comet-ml/opik · Tracing, datasets, LLM-as-judge/evaluation and production monitoring patterns. · Study/integrate only for redacted evaluator telemetry; Apache-2.0. Never use an LLM judge as the sole certification authority.
1 mention
formancehq/ledger ↗
Ledger architecture donor
Research evidence
- formancehq/ledger · https://github.com/formancehq/ledger · 1,368 · MIT · 2026-08-28T22:56:56Z · false · main · Study/synthetic pilot
1 mention
frappe/lms ↗
10 · frappe/lms · Course hierarchy, batches, quizzes, assignments and certificates. · Study/possible later sidecar; AGPL-3.0. License and deployment boundary require legal/architecture review; not a direct chatter simula
Research evidence
- 10 · frappe/lms · Course hierarchy, batches, quizzes, assignments and certificates. · Study/possible later sidecar; AGPL-3.0. License and deployment boundary require legal/architecture review; not a direct chatter simulator.
1 mention
HumanSignal/label-studio ↗
5 · HumanSignal/label-studio · Multi-user labeling and review tied to accounts, with model/active-learning hooks. · Integrate/study for blinded transcript annotation and rubric calibration; Apache-2.0. Not an LMS or cert
Research evidence
- 5 · HumanSignal/label-studio · Multi-user labeling and review tied to accounts, with model/active-learning hooks. · Integrate/study for blinded transcript annotation and rubric calibration; Apache-2.0. Not an LMS or certification issuer.
1 mention
juspay/hyperswitch ↗
juspay/hyperswitch · https://github.com/juspay/hyperswitch · 43,538 · Apache-2.0 · 2026-08-29T01:01:27Z · false · main · Rail/reconciliation sidecar
Research evidence
- juspay/hyperswitch · https://github.com/juspay/hyperswitch · 43,538 · Apache-2.0 · 2026-08-29T01:01:27Z · false · main · Rail/reconciliation sidecar
1 mention
marmelab/atomic-crm ↗
Modern CRM UI · Atomic CRM and NextCRM · Pattern donors · React/shadcn-shaped donors for relationship, project, invoice and document UX; neither is the full operating system.
Research evidence
- Modern CRM UI · Atomic CRM and NextCRM · Pattern donors · React/shadcn-shaped donors for relationship, project, invoice and document UX; neither is the full operating system.
1 mention
pdovhomilja/nextcrm-app ↗
Modern CRM UI · Atomic CRM and NextCRM · Pattern donors · React/shadcn-shaped donors for relationship, project, invoice and document UX; neither is the full operating system.
Research evidence
- Modern CRM UI · Atomic CRM and NextCRM · Pattern donors · React/shadcn-shaped donors for relationship, project, invoice and document UX; neither is the full operating system.
1 mention
pgr0ss/pgledger ↗
Postgres ledger architecture donor
Research evidence
- pgr0ss/pgledger · https://github.com/pgr0ss/pgledger · 487 · MIT · 2026-08-28T08:22:26Z · false · main · Study first
1 mention
promptfoo/promptfoo ↗
6 · promptfoo/promptfoo · LLM evaluation, red-team cases, regression suites and CI checks. · Integrate into synthetic evaluator regression; MIT. It proves prompt/test behavior, not human competence or policy compliance.
Research evidence
- 6 · promptfoo/promptfoo · LLM evaluation, red-team cases, regression suites and CI checks. · Integrate into synthetic evaluator regression; MIT. It proves prompt/test behavior, not human competence or policy compliance.
1 mention
RasaHQ/rasa ↗
2 · RasaHQ/rasa · Conversation state/flows and testable dialogue behavior for a synthetic fan simulator. · Study or integrate a sandbox adapter; Apache-2.0. Never treat NLU confidence as a safety or certification decisio
Research evidence
- 2 · RasaHQ/rasa · Conversation state/flows and testable dialogue behavior for a synthetic fan simulator. · Study or integrate a sandbox adapter; Apache-2.0. Never treat NLU confidence as a safety or certification decision.
22 mentions
toeverything/AFFiNE ↗
Knowledge and linked-context donor; mixed licence
Research evidence
- 7 · AFFiNE · Meeting notes, briefs, SOPs, linked creator context, decisions and handoffs · Sanitized knowledge pilot / pattern donor · This is the important category the first hunt missed. It is not the CRM or ledger, and its backend has a mixed/commercial license boundary.
- 4 · AFFiNE · Meeting notes, briefs, SOPs, linked creator records, decisions and handoffs · Separate knowledge workspace/content store and identity boundary. Root licence splits MIT areas, separately licensed backend/common-native areas and third-party licences. licence · product · Study first; optional knowledge sidecar, never finance/system-of-record · Medium-high
- toeverything/AFFiNE · https://github.com/toeverything/AFFiNE · 71,986 · NOASSERTION · 2026-08-28T13:24:46Z · false · canary
- 5 · AFFiNE — toeverything/AFFiNE · Meeting notes, creator records, SOPs, briefs, cross-linked decisions, handoffs; journeys 1, 2, 3, 4, 6 · study · Local-first workspace combining documents, whiteboards, and planning. Its linked-document mental model is the clearest answer to the brief’s institutional-memory gap. Study block/editor, backlinks, permissions, and offline/sync patterns; do not make it HALO’s identity authority. · Mixed license: the inspected LICENSE says content outside backend/native paths is MIT, while backend server material is under an EE subscription license. Treat backend reuse as unavailable without legal/commercial agreement. · High
18 mentions
erxes/erxes ↗
Broad system reference; commercial SaaS licence conflict
Research evidence
- G1 · erxes/erxes · README calls it a source-available Experience Operating System unifying marketing, sales, operations, and support. Core modules include inbox, contacts, products, segments, automation, and documents; plugins add frontline conversations/tickets/tasks, operations projects/resources/cycles, sales, content, accounting, and team functions. · Study first; self-hosted spike only after license review. This is the closest open repository to a multi-module agency shell, but its AGPL/source-available boundary and explicit no-competing-SaaS clause prevent treating it as a drop-in HALO base. · High for module breadth; Medium for reusable boundary
- erxes/erxes · https://github.com/erxes/erxes · 4,074 · NOASSERTION · 2026-08-29T04:08:17Z · false · main
- - erxes LICENSE.md: content
- 4 · erxes · Self-hosted Experience Operating System with inbox, contacts, products, segments, automation and documents; broad agency/business module coverage. · Module-boundary study; reject as commercial SaaS foundation. Root license is AGPL with enterprise paths and an explicit no-competing-SaaS restriction.
9 mentions
trycompai/crm ↗
G5 · trycompai/crm · README presents an MIT, agent-first CRM in which the agent keeps notes, works a durable queue, schedules follow-ups, and records observed evidence rather than guessed facts. It is built with Bun/Post
Research evidence
- G5 · trycompai/crm · README presents an MIT, agent-first CRM in which the agent keeps notes, works a durable queue, schedules follow-ups, and records observed evidence rather than guessed facts. It is built with Bun/Postgres and has a dedicated agent deployment. · AI-native pattern study; not a whole OFM OS. The evidence ledger, work-queue semantics, and “observed fact vs suggestion” rule are unusually relevant to relationship memory and safe automation. · High for README-visible pattern; Medium for maturity
- trycompai/crm · https://github.com/trycompai/crm · 9,071 · MIT · 2026-08-21T14:25:00Z · false · release
- 5 · Comp AI CRM · MIT agent-first CRM where the agent keeps notes, owns a work queue, schedules follow-ups and distinguishes observed facts from suggestions. · AI safety/queue pattern study. It does not provide creator consent, rights, e-sign, portal or money truth; keep all consequential actions behind HALO gates.
- trycompai/crm · https://github.com/trycompai/crm · 9,072 · MIT · 2026-08-21T14:25:00Z · false · release
6 mentions
apache/casbin ↗
2 · apache/casbin · Configurable ACL/RBAC/ABAC/domain/tenant policy library with multiple language implementations. · Study or use through a suitable language SDK. Use only behind a server identity boundary and log every
Research evidence
- 2 · apache/casbin · Configurable ACL/RBAC/ABAC/domain/tenant policy library with multiple language implementations. · Study or use through a suitable language SDK. Use only behind a server identity boundary and log every allow/deny decision needed for audit; it does not solve resource data filtering by itself. Apache-2.0. · README, license.
- apache/casbin · 20,358 · Apache-2.0 · 2026-08-21T08:53:52Z · false · master · README, LICENSE. Policy-library study.
6 mentions
apache/superset ↗
5 · apache/superset · Mature BI/dashboard/query surface for comparative evaluation. · Benchmark only. Apache-2.0 is permissive, but a dashboard-first product does not solve event authority, approvals, audit, or owner act
Research evidence
- 5 · apache/superset · Mature BI/dashboard/query surface for comparative evaluation. · Benchmark only. Apache-2.0 is permissive, but a dashboard-first product does not solve event authority, approvals, audit, or owner action closure. · README, license.
- apache/superset · 74,526 · Apache-2.0 · 2026-08-29T07:34:25Z · false · master · README, LICENSE.txt. BI benchmark only.
6 mentions
cortezaproject/corteza ↗
2 · cortezaproject/corteza · API-centric low-code CRM/business-process/structured-data apps with workflows and automation; Apache-2.0 source. · Prototype/reference only. Good for testing configurable exception records an
Research evidence
- 2 · cortezaproject/corteza · API-centric low-code CRM/business-process/structured-data apps with workflows and automation; Apache-2.0 source. · Prototype/reference only. Good for testing configurable exception records and admin UX; separate auth/data/runtime makes it a candidate for a bounded app, not a central HALO authority. · README, license.
- cortezaproject/corteza · 2,140 · Apache-2.0 · 2026-08-27T14:31:07Z · false · 2024.9.x · README, LICENSE. Prototype/reference.
6 mentions
DhurimHalili/influenceflow-crm ↗
5 · InfluenceFlow CRM — DhurimHalili/influenceflow-crm · Creator discovery, roster pipeline, outreach/reach-backs, campaign tracking, brand contacts; journeys 1 and 2 · study · MIT React/Vite/Supabase app with live creat
Research evidence
- 5 · InfluenceFlow CRM — DhurimHalili/influenceflow-crm · Creator discovery, roster pipeline, outreach/reach-backs, campaign tracking, brand contacts; journeys 1 and 2 · study · MIT React/Vite/Supabase app with live creator table/board, bulk import, duplicate detection, 10-stage statuses, activity logging, campaign/brand types, daily send limits, delayed reach-backs, and Gmail OAuth discovery functions. · It is a small Supabase app and overlaps HALO’s creator/onboarding domain. Reuse the operator flow and data vocabulary; do not add a second creator authority. · High
- DhurimHalili/influenceflow-crm · https://github.com/DhurimHalili/influenceflow-crm · 1 · MIT · 2026-08-27T20:35:39Z · false · main · —
- G24 · DhurimHalili/influenceflow-crm · README links to a live free creator CRM with creators/brands/campaigns/calendar, YouTube discovery, pipeline states, agency-cut calculation, per-user isolation, CSV/JSON export, dedupe/merge/trash, and a note that Gmail sending is not yet enabled. · Live pattern/demo study, not core. It is valuable precisely because it shows a small end-to-end creator loop and is candid about the missing email mutation; its one-star scale and hosted maintainer Supabase are not enough for HALO authority. · High for visible scope; Medium for production readiness
- DhurimHalili/influenceflow-crm · https://github.com/DhurimHalili/influenceflow-crm · 1 · MIT · 2026-08-27T20:35:39Z · false · main
6 mentions
flowable/flowable-engine ↗
5 · flowable/flowable-engine · BPMN process, CMMN case and DMN rules for human/system activities. · Study for complex approval/case semantics; do not introduce for the first TypeScript slice. Java runtime and separate pr
Research evidence
- 5 · flowable/flowable-engine · BPMN process, CMMN case and DMN rules for human/system activities. · Study for complex approval/case semantics; do not introduce for the first TypeScript slice. Java runtime and separate process model add cost; useful if owner/GRC cases become process-heavy. Apache-2.0. · README, license.
- flowable/flowable-engine · 9,500 · Apache-2.0 · 2026-08-28T22:43:50Z · false · main · README, LICENSE. BPMN/CMMN/DMN study.
6 mentions
hcengineering/platform ↗
Whole-shell reference; hosted continuity warning
Research evidence
- G3 · hcengineering/platform · Huly's platform README lists Chat, Project Management, CRM, HRM, and ATS applications, a typed API client, production/development release tracks, and a self-host path. It also contains an important notice that hosted Huly is shutting down while self-hosted deployments are unaffected. · Self-host/pattern study; reject hosted adoption. It proves that one shell can span team chat, work, CRM, people, and recruiting, but the hosted shutdown is a direct continuity warning. · High for scope and shutdown caveat
- hcengineering/platform · https://github.com/hcengineering/platform · 27,486 · EPL-2.0 · 2026-08-27T13:24:38Z · false · develop
- 2 · Huly platform · One shell includes Chat, Project Management, CRM, HRM and ATS, with typed API-client and self-host references. README has a prominent hosted-service shutdown/export warning. · Self-host/pattern study; reject hosted continuity. It is evidence that a broad shell is possible, not evidence that its creator or rights model fits.
- Huly platform for money authority:
6 mentions
opencats/OpenCATS ↗
G22 · opencats/OpenCATS · README describes a free/open candidate tracking system for recruiters from job posting and applications through selection and submission, with installation docs and a live project. · Talent-acqu
Research evidence
- G22 · opencats/OpenCATS · README describes a free/open candidate tracking system for recruiters from job posting and applications through selection and submission, with installation docs and a live project. · Talent-acquisition pattern study. Its candidate state machine is relevant before a creator becomes a roster member, but it is not a creator portal or consent/rights system. · High for scope; Medium for modernity
- opencats/OpenCATS · https://github.com/opencats/OpenCATS · 733 · NOASSERTION · 2026-08-28T10:44:03Z · false · master
- - OpenCATS LICENSE.md
- 4 · OpenCATS · Candidate/applicant tracking from job posting and application through selection and submission. · Acquisition-state study only. It can inform pre-roster candidate states; it is not a creator portal, consent ledger or adult-evidence system, and its license is mixed.
4 mentions
AppFlowy-IO/AppFlowy ↗
Knowledge rejects: Outline is not an open-source source-reuse candidate in the checked branch: its root LICENSE is Business Source License 1.1, with a limited grant excluding a commercial Document Service until the 2030-
Research evidence
- Knowledge rejects: Outline is not an open-source source-reuse candidate in the checked branch: its root LICENSE is Business Source License 1.1, with a limited grant excluding a commercial Document Service until the 2030-07-13 change date. AppFlowy is AGPL-3.0 and remains comparison prior art, not a reason to add a second knowledge runtime.
- AppFlowy-IO/AppFlowy · 76,050 · AGPL-3.0 · 2026-08-28T06:32:59Z · false · main · README, LICENSE. Comparison knowledge prior art; no direct reuse recommendation.
4 mentions
chaoyubai8-tech/creatorreach-ai ↗
creator-crm and CreatorReach AI · Small, focused examples of creator discovery, AI fit scoring, campaign/outreach tracking, Gmail draft automation, reply classification and follow-up. · Study only. Useful for discovery v
Research evidence
- creator-crm and CreatorReach AI · Small, focused examples of creator discovery, AI fit scoring, campaign/outreach tracking, Gmail draft automation, reply classification and follow-up. · Study only. Useful for discovery vocabulary and human-reviewed outreach, not a multi-persona foundation.
- chaoyubai8-tech/creatorreach-ai · https://github.com/chaoyubai8-tech/creatorreach-ai · 4 · MIT · 2026-06-23T11:28:21Z · false · main
- 7 · CreatorReach AI — chaoyubai8-tech/creatorreach-ai · Human-controlled creator outreach, Gmail drafts, reply classification, follow-up pipeline; journeys 1, 2, 6, 8 · study · MIT Python app with an explicit campaign → creator → AI draft → Gmail draft → human send → reply classification flow. README says it uses minimal gmail.compose scope, saves the original reply before AI processing, and never auto-sends. · Only 102 files and last push 2026-06-23; local SQLite rather than a shared agency backend. Borrow the human-in-the-loop boundary and original-before-LLM persistence rule. · High
- chaoyubai8-tech/creatorreach-ai · https://github.com/chaoyubai8-tech/creatorreach-ai · 4 · MIT · 2026-06-23T11:28:21Z · false · main · —
4 mentions
ofmtools/onlyfans-crm-comparison ↗
The exact-onlyfans repositories are useful as vocabulary, not as foundations: AirChatter is archived and only a Chrome assistant; of-crm describes admin/supervisor/chatter roles, clocking, sales, shifts and reports but h
Research evidence
- The exact-onlyfans repositories are useful as vocabulary, not as foundations: AirChatter is archived and only a Chrome assistant; of-crm describes admin/supervisor/chatter roles, clocking, sales, shifts and reports but has no declared licence and a placeholder middleware note; velvet-desktop is an unlicensed, empty/low-signal repository; and onlyfans-crm-comparison is a CC-BY comparison dataset, not an operating system. This is a confirmed market gap, not a reason to lower the quality bar.
- ofmtools/onlyfans-crm-comparison · https://github.com/ofmtools/onlyfans-crm-comparison · 1 · NOASSERTION · 2026-08-05T16:40:54Z · false · main
- ofmtools/onlyfans-crm-comparison · https://github.com/ofmtools/onlyfans-crm-comparison · 1 · NOASSERTION · 2026-08-05T16:40:54Z · false · main · Actual root LICENSE is CC BY 4.0: dataset/comparison material, not an operating system; attribution/link/change notice required. Study as market evidence only.
3 mentions
blindzero/IdentityLifecycleEngine ↗
3 · IdentityLifecycleEngine · Apache text in root license; PowerShell 7 headless JML engine with plan → execute, idempotent provider-agnostic steps and structured actor/correlation audit events. · JML mechanics study onl
Research evidence
- 3 · IdentityLifecycleEngine · Apache text in root license; PowerShell 7 headless JML engine with plan → execute, idempotent provider-agnostic steps and structured actor/correlation audit events. · JML mechanics study only. Seven stars and a PowerShell-specific deployment are not production evidence; the plan/preview/revoke receipt is the useful idea.
- blindzero/IdentityLifecycleEngine · https://github.com/blindzero/IdentityLifecycleEngine · 7 · NOASSERTION · 2026-07-20T04:14:14Z · false · main
- - IdentityLifecycleEngine LICENSE.md:
2 mentions
AOSSIE-Org/InPactAI ↗
9 · InPact — AOSSIE-Org/InPactAI · Creator/brand/agency matching, sponsorship pricing/deal optimization, collaboration chat, analytics; journeys 1, 2, 5, 6 · study · GPL-3.0 React/FastAPI/Supabase app with actual chat, c
Research evidence
- 9 · InPact — AOSSIE-Org/InPactAI · Creator/brand/agency matching, sponsorship pricing/deal optimization, collaboration chat, analytics; journeys 1, 2, 5, 6 · study · GPL-3.0 React/FastAPI/Supabase app with actual chat, collaboration-hub, creator matching, audience/revenue analytics, contract templates, onboarding, and auth source paths. · GPL-3.0 and last push 2026-03-26. Use as a feature/model comparison, not embedded code; its Supabase data model overlaps HALO. · Medium-high
- AOSSIE-Org/InPactAI · https://github.com/AOSSIE-Org/InPactAI · 100 · GPL-3.0 · 2026-03-26T11:57:10Z · false · main · —
2 mentions
apitable/apitable ↗
16 · APITable — apitable/apitable · Creator/campaign registries, operational views, lightweight portals and automations; journeys 2, 3, 4 · study · API-oriented collaborative low-code tables are a useful pattern for conf
Research evidence
- 16 · APITable — apitable/apitable · Creator/campaign registries, operational views, lightweight portals and automations; journeys 2, 3, 4 · study · API-oriented collaborative low-code tables are a useful pattern for configurable rosters, campaign trackers, and referral views. · AGPL-3.0 and last verified push 2025-10-30; this freshness gap is large relative to the other finalists. Use as a design donor unless current maintenance is revalidated. · Medium
- apitable/apitable · https://github.com/apitable/apitable · 15,578 · AGPL-3.0 · 2025-10-30T03:34:31Z · false · develop · —
2 mentions
axelfrache/questify ↗
The open-source hunt found no mature, OnlyFans-specific chatter-training suite. Questify is a small generic quest/progression system with XP, levels, achievements, streaks and admin/progression services; it is useful as
Research evidence
- The open-source hunt found no mature, OnlyFans-specific chatter-training suite. Questify is a small generic quest/progression system with XP, levels, achievements, streaks and admin/progression services; it is useful as mechanics prior art but not a replacement for HALO’s existing gamification domain. The practical design is: Buzz hosts or links the training conversation; HALO owns scenario versions, rubric definitions, completion/certification, coaching records, XP/reward ledger and manager overrides; training results can influence queue eligibility or coaching—not silently change pay. Keep XP and rewards append-only and separate from payout truth so gamification cannot become a shadow compensation system.
- axelfrache/questify · https://github.com/axelfrache/questify · 5 · NOASSERTION · 2026-08-19T14:03:41Z · false · main
2 mentions
docusealco/docuseal ↗
1 · DocuSeal · AGPL self-hostable signing, templates, multiple submitters, API/webhooks, embedded forms and signature verification. · Best isolated OSS e-sign experiment; buy/host only after legal and evidence review. HA
Research evidence
- 1 · DocuSeal · AGPL self-hostable signing, templates, multiple submitters, API/webhooks, embedded forms and signature verification. · Best isolated OSS e-sign experiment; buy/host only after legal and evidence review. HALO must pin document/version/signer/timestamp/certificate references and retain export links.
- docusealco/docuseal · https://github.com/docusealco/docuseal · 18,398 · AGPL-3.0 · 2026-08-25T11:33:36Z · false · master
2 mentions
getlago/lago ↗
G26 · getlago/lago · README presents AGPL monetization infrastructure for metered usage, pricing, credits, entitlements, invoices, payments, and revenue, including embedded monetization and an agentic-AI demo. · Money-ad
Research evidence
- G26 · getlago/lago · README presents AGPL monetization infrastructure for metered usage, pricing, credits, entitlements, invoices, payments, and revenue, including embedded monetization and an agentic-AI demo. · Money-adjacent study/integration only. Its billing primitives may inform agency charges or platform usage, but creator liabilities, split attribution, reversals, tax evidence, and statements remain HALO's ledger problem. · High for monetization scope; Medium for OFM fit
- getlago/lago · https://github.com/getlago/lago · 10,438 · AGPL-3.0 · 2026-08-28T21:31:21Z · false · main
2 mentions
illacloud/illa-builder ↗
ILLA Builder — illacloud/illa-builder · study only · Apache-2.0 low-code internal-tool builder with many data-source connectors and schedule/webhook automation, but last verified push was 2026-05-27 and it creates anothe
Research evidence
- ILLA Builder — illacloud/illa-builder · study only · Apache-2.0 low-code internal-tool builder with many data-source connectors and schedule/webhook automation, but last verified push was 2026-05-27 and it creates another app-builder surface rather than a creator operating model.
- illacloud/illa-builder · https://github.com/illacloud/illa-builder · 12,312 · Apache-2.0 · 2026-05-27T02:22:32Z · false · beta · —
2 mentions
lobehub/lobehub ↗
LobeHub — lobehub/lobehub · buy/study only · Its “chief agent operator” shell—hiring, scheduling, and reporting on agents—is relevant to journey 8, but the inspected Community License permits commercial use without modif
Research evidence
- LobeHub — lobehub/lobehub · buy/study only · Its “chief agent operator” shell—hiring, scheduling, and reporting on agents—is relevant to journey 8, but the inspected Community License permits commercial use without modification and requires a commercial license for derivative distribution. It is not a clean embed donor.
- lobehub/lobehub · https://github.com/lobehub/lobehub · 82,078 · NOASSERTION · 2026-08-29T07:43:04Z · false · canary · LICENSE: LobeHub Community License; commercial derivative distribution requires a commercial license.
2 mentions
silverstein/minutes ↗
13 · minutes — silverstein/minutes · “What did we promise?” memory from meetings and voice memos; journeys 1 and 6 · study · MIT, local-first conversation memory written as Markdown, with policy-aware source exposure and
Research evidence
- 13 · minutes — silverstein/minutes · “What did we promise?” memory from meetings and voice memos; journeys 1 and 6 · study · MIT, local-first conversation memory written as Markdown, with policy-aware source exposure and explicit authorization. Its consent/restricted-meeting defaults are useful for HALO’s governance model. · Desktop/Rust/plain-file workflow, not a shared agency database. Borrow provenance and consent patterns; do not treat local Markdown as the canonical record. · High
- silverstein/minutes · https://github.com/silverstein/minutes · 1,456 · MIT · 2026-08-29T07:30:25Z · false · main · —
2 mentions
Sydekse/creator-marketplace ↗
Excellent workflow evidence, but unlicensed
Research evidence
- 4 · Creator Marketplace — Sydekse/creator-marketplace · Brand/creator multi-role portal, campaign brief → creator selection → deliverable review → approved payout, disputes/audit; journeys 2, 3, 5, 7 · study · Very concrete workflow model: role/ownership guard, creator onboarding, campaign/deal state machine, usage-rights terms, deliverable approval, budget/escrow, admin worklist, campaign ledger and reconciliation. Tree contains 26 focused tests including escrow-ledger, authz coverage, creator onboarding, deal state, and campaign funding. · No license file (API NOASSERTION, license endpoint and root license-file check both empty). Do not lift code. Its current branch is dev; treat the implementation as unlicensed pattern evidence only. · High
- Sydekse/creator-marketplace · https://github.com/Sydekse/creator-marketplace · 2 · NOASSERTION · 2026-08-29T08:04:41Z · false · dev · No license endpoint result; root has no license-like file.
2 mentions
Zackriya-Solutions/meetily ↗
17 · Meetily — Zackriya-Solutions/meetily · Private meeting capture for owners/managers, especially when cloud recording is unacceptable; journeys 1, 6, 7 · study / buy · MIT local desktop meeting assistant with live tra
Research evidence
- 17 · Meetily — Zackriya-Solutions/meetily · Private meeting capture for owners/managers, especially when cloud recording is unacceptable; journeys 1, 6, 7 · study / buy · MIT local desktop meeting assistant with live transcription, diarization, and local Ollama summarization. It is a privacy benchmark and possible operator tool, not the shared HALO backend. · Pre-release desktop/Rust workflow; no multi-user agency timeline or Convex integration. · Medium-high
- Zackriya-Solutions/meetily · https://github.com/Zackriya-Solutions/meetily · 30,035 · MIT · 2026-08-29T06:39:27Z · false · main · —
1 mention
ActiDoo/gamification-engine ↗
11 · ActiDoo/gamification-engine · MIT REST gamification service with achievements, goals, progress, leaderboards, rules, triggers and rewards. · Study/rebuild the minimal event contract; stale relative to other candidat
Research evidence
- 11 · ActiDoo/gamification-engine · MIT REST gamification service with achievements, goals, progress, leaderboards, rules, triggers and rewards. · Study/rebuild the minimal event contract; stale relative to other candidates (last push 2023-02-15). Do not delegate reward authority.
1 mention
cjmellor/level-up ↗
12 · cjmellor/level-up · XP, levels, achievements, streaks, multipliers and experience audit concepts. · Study small patterns; MIT, PHP/Laravel. Use audit/provenance ideas only; streaks must be opt-out and wellbeing-safe
Research evidence
- 12 · cjmellor/level-up · XP, levels, achievements, streaks, multipliers and experience audit concepts. · Study small patterns; MIT, PHP/Laravel. Use audit/provenance ideas only; streaks must be opt-out and wellbeing-safe.
1 mention
flash-oss/medici ↗
flash-oss/medici · https://github.com/flash-oss/medici · 358 · MIT · 2026-07-29T10:09:00Z · false · master · Study only
Research evidence
- flash-oss/medici · https://github.com/flash-oss/medici · 358 · MIT · 2026-07-29T10:09:00Z · false · master · Study only
1 mention
LerianStudio/midaz ↗
LerianStudio/midaz · https://github.com/LerianStudio/midaz · 435 · NOASSERTION · 2026-08-29T00:20:50Z · false · develop · Legal review/study only
Research evidence
- LerianStudio/midaz · https://github.com/LerianStudio/midaz · 435 · NOASSERTION · 2026-08-29T00:20:50Z · false · develop · Legal review/study only
1 mention
NationalSecurityAgency/skills-client ↗
8 · NationalSecurityAgency/skills-client · Companion client pattern for SkillTree-style skill/progress presentation. · Study with skills-service; Apache-2.0. Do not copy its client-side progression as authoritative rewar
Research evidence
- 8 · NationalSecurityAgency/skills-client · Companion client pattern for SkillTree-style skill/progress presentation. · Study with skills-service; Apache-2.0. Do not copy its client-side progression as authoritative reward state.
1 mention
ngageoint/gamification-server ↗
14 · ngageoint/gamification-server · Rules/signals, team awards, badges and Open Badges export concepts. · Study only; MIT and stale (last push 2023-07-09). The reward surface is not sufficient evidence for HALO use.
Research evidence
- 14 · ngageoint/gamification-server · Rules/signals, team awards, badges and Open Badges export concepts. · Study only; MIT and stale (last push 2023-07-09). The reward surface is not sufficient evidence for HALO use.
1 mention
qcod/laravel-gamify ↗
13 · qcod/laravel-gamify · Minimal reputation points, badges and user-badge migrations/traits. · Study only; MIT, PHP/Laravel. Too primitive for training evidence, appeal, fairness, or certification.
Research evidence
- 13 · qcod/laravel-gamify · Minimal reputation points, badges and user-badge migrations/traits. · Study only; MIT, PHP/Laravel. Too primitive for training evidence, appeal, fairness, or certification.
1 mention
saeloun/miru-web ↗
Agency money/time pattern · Miru · Study · Useful small-agency reference for time, invoices, expenses, payments and benefits; not a creator-liability ledger.
Research evidence
- Agency money/time pattern · Miru · Study · Useful small-agency reference for time, invoices, expenses, payments and benefits; not a creator-liability ledger.
1 mention
spatie/laravel-event-sourcing ↗
spatie/laravel-event-sourcing · https://github.com/spatie/laravel-event-sourcing · 915 · MIT · 2026-08-10T08:44:23Z · false · main · Study pattern
Research evidence
- spatie/laravel-event-sourcing · https://github.com/spatie/laravel-event-sourcing · 915 · MIT · 2026-08-10T08:44:23Z · false · main · Study pattern
1 mention
THU-MAIC/OpenMAIC ↗
3 · THU-MAIC/OpenMAIC · Course/session workbench, quizzes, interactives, simulations and reusable learning materials. · Study/prototype; MIT. Fresh release and broad agent surface require security, provenance and persist
Research evidence
- 3 · THU-MAIC/OpenMAIC · Course/session workbench, quizzes, interactives, simulations and reusable learning materials. · Study/prototype; MIT. Fresh release and broad agent surface require security, provenance and persistence review before any use.
1 mention
tigerbeetle/tigerbeetle ↗
tigerbeetle/tigerbeetle · https://github.com/tigerbeetle/tigerbeetle · 16,924 · Apache-2.0 · 2026-08-25T09:21:57Z · false · main · Study primitives
Research evidence
- tigerbeetle/tigerbeetle · https://github.com/tigerbeetle/tigerbeetle · 16,924 · Apache-2.0 · 2026-08-25T09:21:57Z · false · main · Study primitives
9 mentions
outline/outline ↗
Useful UX reference; BSL service restriction
Research evidence
- Outline — outline/outline · reject for adoption; study UX · Excellent React/Node collaborative knowledge base, but the inspected LICENSE is Business Source License 1.1 with a “Document Service” restriction until 2030-07-13. A multi-tenant HALO offering that gives external parties controlled teams/documents is close to the prohibited shape.
- outline/outline · https://github.com/outline/outline · 40,368 · NOASSERTION · 2026-08-29T02:59:37Z · false · main · LICENSE: Business Source License 1.1; Document Service restriction; change date 2030-07-13 to Apache-2.0.
- G30 · outline/outline · README describes a collaborative knowledge base with hosted and self-host options. Its current license is BSL 1.1, prohibits a commercial “Document Service,” and changes to Apache only on the stated future date. · Study or buy; reject as a client-portal/document authority under the public source terms. The information architecture is useful, but the license boundary conflicts with white-label multi-tenant customer work. · High for license/boundary
- outline/outline · https://github.com/outline/outline · 40,368 · NOASSERTION · 2026-08-29T02:59:37Z · false · main
6 mentions
dbt-labs/dbt-core ↗
2 · dbt-labs/dbt-core · Versioned transformations and metric/data-model build foundation for a governed read model. · Use as a pattern/integration option, not an owner UI or authority. Definitions, lineage and tests can
Research evidence
- 2 · dbt-labs/dbt-core · Versioned transformations and metric/data-model build foundation for a governed read model. · Use as a pattern/integration option, not an owner UI or authority. Definitions, lineage and tests can support the KPI registry; source data and domain events still own truth. Apache-2.0. · README, license.
- dbt-labs/dbt-core · 13,716 · Apache-2.0 · 2026-08-29T03:08:00Z · false · main · README, LICENSE. Metric/lineage build pattern.
6 mentions
directus/directus ↗
G9 · directus/directus · README describes a SQL-backed REST/GraphQL API, visual Studio, AI assistant, native MCP server, field-level policy access, extensibility, self-host/cloud, and multiple SQL databases. · Data/contr
Research evidence
- G9 · directus/directus · README describes a SQL-backed REST/GraphQL API, visual Studio, AI assistant, native MCP server, field-level policy access, extensibility, self-host/cloud, and multiple SQL databases. · Data/control-plane experiment, not the whole agency OS. It could back a bounded portal or operational module if HALO accepts its current Monospace Sustainable Core License and keeps domain authority explicit. · High for stated primitives; High for license boundary
- directus/directus · https://github.com/directus/directus · 37,678 · NOASSERTION · 2026-08-28T21:02:34Z · false · main
- - Directus license is the
- 5 · Directus · SQL-backed REST/GraphQL, visual Studio, field-level policies, extensibility and self-host/cloud. · Bounded data/portal experiment only. The MSCL-1.0-GPL source terms and competing-use limitation require legal review; do not make it a second HALO ledger.
6 mentions
evidence-dev/evidence ↗
4 · evidence-dev/evidence · Code-based SQL/Markdown reports, agent-ready authoring, and self-hostable published reports. · Use for periodic owner packs if useful; not live command state. MIT; generated reports must displ
Research evidence
- 4 · evidence-dev/evidence · Code-based SQL/Markdown reports, agent-ready authoring, and self-hostable published reports. · Use for periodic owner packs if useful; not live command state. MIT; generated reports must display freshness and source lineage. · README, license.
- evidence-dev/evidence · 6,891 · MIT · 2026-08-26T20:45:13Z · false · main · README, LICENSE. Periodic report pattern.
6 mentions
hatchet-dev/hatchet ↗
3 · hatchet-dev/hatchet · Postgres-backed durable tasks, retries, event waits, pause/resume, queues, logs, monitoring and multi-tenant operation. · Alternative spike to Trigger/Temporal, not a third runtime. Choose one e
Research evidence
- 3 · hatchet-dev/hatchet · Postgres-backed durable tasks, retries, event waits, pause/resume, queues, logs, monitoring and multi-tenant operation. · Alternative spike to Trigger/Temporal, not a third runtime. Choose one engine after proving idempotency, approval resume, migration and operator ergonomics. Buzz remains communication/agent context. MIT. · README, license.
- hatchet-dev/hatchet · 7,808 · MIT · 2026-08-29T07:08:46Z · false · main · README, LICENSE. Alternative durable-task spike.
6 mentions
n8n-io/n8n ↗
Useful product; source reuse licence conflict
Research evidence
- n8n — n8n-io/n8n · buy or reject; do not embed code · Strong integrations and human approvals, but the inspected LICENSE is Sustainable Use License, not open source: internal-business/noncommercial limits plus separately licensed .ee code. A hosted n8n plan could be a procurement decision; source reuse is not the default.
- n8n-io/n8n · https://github.com/n8n-io/n8n · 202,749 · NOASSERTION · 2026-08-29T07:04:57Z · false · master · LICENSE.md: Sustainable Use License; noncommercial/internal-use limitations; .ee paths separately licensed.
- G17 · n8n-io/n8n · README/product is a mature workflow automation platform with a large integration ecosystem and AI workflow use cases. The repository's license explicitly uses a Sustainable Use License and separates EE files; non-main branches are not licensed. · Buy/integrate only after legal review; do not treat as open-source code. Useful as an external automation engine, but the license and mutable third-party workflow state make it unsuitable as the domain authority. · High for license; Medium for integration fit
- n8n-io/n8n · https://github.com/n8n-io/n8n · 202,749 · NOASSERTION · 2026-08-29T07:04:57Z · false · master
3 mentions
akaunting/akaunting ↗
G28 · Akaunting/Akaunting · README describes Laravel/Vue accounting software with REST API, modular apps, and small-business/freelancer accounting. Its BSL license limits production use to two users/one company/1,000 inv
Research evidence
- G28 · Akaunting/Akaunting · README describes Laravel/Vue accounting software with REST API, modular apps, and small-business/freelancer accounting. Its BSL license limits production use to two users/one company/1,000 invoices and bars rebranding or accounting services without the applicable rights. · Reject for HALO's multi-persona core unless a commercial license is purchased. The accounting model is worth studying, but the public license terms are incompatible with an agency SaaS used by multiple staff/clients. · High for license boundary
- Akaunting/Akaunting · https://github.com/akaunting/akaunting · 10,100 · NOASSERTION · 2026-08-29T07:57:33Z · false · master
- - Akaunting LICENSE.txt
3 mentions
authzed/spicedb ↗
1 · SpiceDB · Apache-2.0 fine-grained authorization using schemas and relationships; authentication-agnostic. · Best access-policy pattern. Model creator, staff, team, asset, capability and purpose relationships only aft
Research evidence
- 1 · SpiceDB · Apache-2.0 fine-grained authorization using schemas and relationships; authentication-agnostic. · Best access-policy pattern. Model creator, staff, team, asset, capability and purpose relationships only after HALO stable IDs and server-side auth exist. It does not provision accounts or verify identity.
- Staff JML / grants · WorkOS Directory Provisioning, Okta LCM, SpiceDB · Plan/approve/apply/revoke receipts, resource-scoped grants, expiry, owner, least privilege, inactive-not-deleted identity, re-provision event, failure queue and proof that credentials/Drive/Buzz access were rotated or removed.
- authzed/spicedb · https://github.com/authzed/spicedb · 6,999 · Apache-2.0 · 2026-08-28T19:07:06Z · false · main
2 mentions
Adityaada0/Youtube-editor-creator-bridge ↗
10 · YouTube Approval & Upload Middleware — Adityaada0/Youtube-editor-creator-bridge · Editor upload → creator approval → scheduled publication, workspace-specific channels, encrypted provider credentials; journey 3 and
Research evidence
- 10 · YouTube Approval & Upload Middleware — Adityaada0/Youtube-editor-creator-bridge · Editor upload → creator approval → scheduled publication, workspace-specific channels, encrypted provider credentials; journey 3 and parts of 7/8 · study · Source-backed Next.js/S3/Postgres/Prisma/BullMQ architecture: presigned uploads, role-scoped creator/editor workspaces, approval queue, AES-256-GCM OAuth credentials, resumable worker, status machine, retry upload, and YouTube privacy/schedule modes. · No license file. Pattern-only. The approval/worker split is directly useful for Drive/voice/content publishing, but HALO should preserve its own provenance and auth. · High
- Adityaada0/Youtube-editor-creator-bridge · https://github.com/Adityaada0/Youtube-editor-creator-bridge · 2 · NOASSERTION · 2026-05-07T01:04:57Z · false · main · No license endpoint result; root has no license-like file.
2 mentions
Ads-Bazaar/ads-bazaar ↗
13 · AdsBazaar — Ads-Bazaar/ads-bazaar · Multi-currency creator campaign funding, escrow, proof of work, approval, and payout; journey 5 with support for 2/3 · study · README describes business funds → Soroban escrow → c
Research evidence
- 13 · AdsBazaar — Ads-Bazaar/ads-bazaar · Multi-currency creator campaign funding, escrow, proof of work, approval, and payout; journey 5 with support for 2/3 · study · README describes business funds → Soroban escrow → creators submit proof → approval releases payout, with multi-currency emerging-market rails. It is a useful challenge to HALO’s creator/referral liability and FX assumptions. · No license file. README says identity verification, disputes, and indexed feeds are still roadmap/scaffold; do not treat it as production finance. · Medium
- Ads-Bazaar/ads-bazaar · https://github.com/Ads-Bazaar/ads-bazaar · 3 · NOASSERTION · 2026-08-24T02:14:04Z · false · main · No license endpoint result; root has no license-like file.
2 mentions
anysearch-ai/anysearch-skill ↗
The user-supplied anysearch-ai/anysearch-skill repository
Research evidence
- The user-supplied anysearch-ai/anysearch-skill repository
- anysearch-ai/anysearch-skill · https://github.com/anysearch-ai/anysearch-skill · 5,975 · Apache-2.0 · 2026-08-28T03:28:32Z · false · main
2 mentions
calcom/cal.diy ↗
G29 · calcom/cal.diy · README describes a 100% MIT community scheduling fork with teams, organizations, workflows, SSO/SAML, and other enterprise features removed; it explicitly warns that it is for self-hosted personal/
Research evidence
- G29 · calcom/cal.diy · README describes a 100% MIT community scheduling fork with teams, organizations, workflows, SSO/SAML, and other enterprise features removed; it explicitly warns that it is for self-hosted personal/non-production use and has no hosted version. · Scheduling utility/pattern only. It can inform creator availability and booking, but the warning makes it unsuitable as production scheduling authority without independent hardening. · High for caveat
- calcom/cal.diy · https://github.com/calcom/cal.diy · 47,997 · MIT · 2026-08-08T17:13:42Z · false · main
2 mentions
carlosmmora26/creatorops ↗
11 · CreatorOps — carlosmmora26/creatorops · Governed content/commerce loop with policy gate, publish evidence, audit ledger, and next decision; journeys 3, 5, 7, 8 · study · README and repository structure show a local-
Research evidence
- 11 · CreatorOps — carlosmmora26/creatorops · Governed content/commerce loop with policy gate, publish evidence, audit ledger, and next decision; journeys 3, 5, 7, 8 · study · README and repository structure show a local-first scaffold with brand configs, ports/adapters, review/judge panel, human/policy gate, publish/commerce adapter, evidence ledger, redacted runs, and tests. It explicitly frames the workflow as an auditable loop rather than an autoposter. · No license file; hackathon/demo provenance and 0 stars. Valuable for an approval/evidence state machine, not a dependency. · Medium-high
- carlosmmora26/creatorops · https://github.com/carlosmmora26/creatorops · 0 · NOASSERTION · 2026-06-29T13:05:52Z · false · main · No license endpoint result; root has no license-like file.
2 mentions
element-hq/element-web ↗
Element Web — element-hq/element-web · reject as HALO chat core · AGPL-3.0 Matrix web client only; adopting it also commits HALO to Matrix homeserver/federation/identity/retention choices. Consider only if the team expli
Research evidence
- Element Web — element-hq/element-web · reject as HALO chat core · AGPL-3.0 Matrix web client only; adopting it also commits HALO to Matrix homeserver/federation/identity/retention choices. Consider only if the team explicitly chooses Matrix.
- element-hq/element-web · https://github.com/element-hq/element-web · 13,408 · AGPL-3.0 · 2026-08-28T18:05:31Z · false · develop · —
2 mentions
ethyca/fides ↗
Fides · Privacy-as-code platform with privacy requests, Privacy Center and data-access fulfillment; Apache-2.0 metadata, but ethyca/fides is currently archived. · Reject as a fresh dependency; study DSR/export concepts.
Research evidence
- Fides · Privacy-as-code platform with privacy requests, Privacy Center and data-access fulfillment; Apache-2.0 metadata, but ethyca/fides is currently archived. · Reject as a fresh dependency; study DSR/export concepts. A rights/consent record still needs OFM-specific purpose, likeness/content scope, platform, geography, expiry, withdrawal and human owner.
- ethyca/fides · https://github.com/ethyca/fides · 482 · Apache-2.0 · 2026-08-06T17:50:27Z · true · main
2 mentions
f1nnix/magplan ↗
Magplan — f1nnix/magplan · study only · Good editorial model—idea → article stages, assignees, attachments, discussions, team action logs, async S3/WordPress publish—but no license and last push 2025-12-04. Keep the work
Research evidence
- Magplan — f1nnix/magplan · study only · Good editorial model—idea → article stages, assignees, attachments, discussions, team action logs, async S3/WordPress publish—but no license and last push 2025-12-04. Keep the workflow idea, not the code.
- f1nnix/magplan · https://github.com/f1nnix/magplan · 31 · NOASSERTION · 2025-12-04T12:46:09Z · false · master · No license endpoint result; root has no license-like file.
2 mentions
Fahim047/gritcms ↗
GritCMS — Fahim047/gritcms · reject as reuse; study concept · The product concept is broad—contacts CRM, affiliate management, booking, commerce, community, workflows, and media—but no license file and API last push 2026
Research evidence
- GritCMS — Fahim047/gritcms · reject as reuse; study concept · The product concept is broad—contacts CRM, affiliate management, booking, commerce, community, workflows, and media—but no license file and API last push 2026-02-27. Do not assume “open source” in its README grants reuse.
- Fahim047/gritcms · https://github.com/Fahim047/gritcms · 1 · NOASSERTION · 2026-02-27T03:10:34Z · false · main · No license endpoint result; root has no license-like file.
2 mentions
iraettae/Telegram-Services-CRM ↗
12 · Telegram Services CRM — iraettae/Telegram-Services-CRM · Telegram-first recruiting, AI-assisted conversation, operator takeover, candidate handoff; journeys 2, 4, 6, 8 · study · Real Python/FastAPI/Aiogram/Pyrogram
Research evidence
- 12 · Telegram Services CRM — iraettae/Telegram-Services-CRM · Telegram-first recruiting, AI-assisted conversation, operator takeover, candidate handoff; journeys 2, 4, 6, 8 · study · Real Python/FastAPI/Aiogram/Pyrogram project with Business API → webhook → dispatcher → AI/master group → WebApp architecture, lead-ready tagging, human override pause, anti-ban rate/delay handling, and 25+ API endpoints. Although its domain is courier recruiting, its chatter/recruiting handoff mechanics map closely to creator acquisition. · No license file and different legal/domain context. Never reuse scraping/device-spoofing patterns; borrow only the explicit human takeover, queue, and handoff boundaries. · Medium-high
- iraettae/Telegram-Services-CRM · https://github.com/iraettae/Telegram-Services-CRM · 0 · NOASSERTION · 2026-07-20T19:56:21Z · false · main · No license endpoint result; root has no license-like file.
2 mentions
leamsigc/MagicSync ↗
MagicSync — leamsigc/MagicSync · reject as embed · Social scheduling/content management is adjacent, but README advertises AGPL while API returns NOASSERTION and no license endpoint/root license file exists. Its platform
Research evidence
- MagicSync — leamsigc/MagicSync · reject as embed · Social scheduling/content management is adjacent, but README advertises AGPL while API returns NOASSERTION and no license endpoint/root license file exists. Its platform/provider boundary is not clear enough for HALO.
- leamsigc/MagicSync · https://github.com/leamsigc/MagicSync · 57 · NOASSERTION · 2026-08-28T08:01:45Z · false · main · README says AGPL; no license endpoint/root license file.
2 mentions
Leantime/leantime ↗
Leantime — Leantime/leantime · study; reject wholesale replacement · Good owner-facing goals/planning model and accessible UX, but AGPL-3.0 PHP application and still a second operational system. The “morning brief / goal
Research evidence
- Leantime — Leantime/leantime · study; reject wholesale replacement · Good owner-facing goals/planning model and accessible UX, but AGPL-3.0 PHP application and still a second operational system. The “morning brief / goals → execution” pattern is worth borrowing.
- Leantime/leantime · https://github.com/Leantime/leantime · 11,470 · AGPL-3.0 · 2026-08-15T04:20:40Z · false · master · —
2 mentions
opf/openproject ↗
OpenProject — opf/openproject · study; reject wholesale replacement · Broad project/portfolio, agile, roadmap, Gantt, time tracking, and collaboration product, but GPL-3.0 Ruby system with a large independent data model.
Research evidence
- OpenProject — opf/openproject · study; reject wholesale replacement · Broad project/portfolio, agile, roadmap, Gantt, time tracking, and collaboration product, but GPL-3.0 Ruby system with a large independent data model. Its project/portfolio concepts are useful; it would not preserve HALO’s creator, payout, Drive, or referral semantics.
- opf/openproject · https://github.com/opf/openproject · 15,965 · GPL-3.0 · 2026-08-29T06:06:31Z · false · dev · —
2 mentions
Parisha-15/SponsorForge ↗
SponsorForge — Parisha-15/SponsorForge · study only · The README describes semantic matching, escrow points, deadlines, and payouts, but API reports no license and the project is 0 stars/9.6 MB. Treat as an unlicensed pr
Research evidence
- SponsorForge — Parisha-15/SponsorForge · study only · The README describes semantic matching, escrow points, deadlines, and payouts, but API reports no license and the project is 0 stars/9.6 MB. Treat as an unlicensed prototype concept, not a source.
- Parisha-15/SponsorForge · https://github.com/Parisha-15/SponsorForge · 0 · NOASSERTION · 2026-08-13T11:18:30Z · false · master · No license endpoint result; root has no license-like file.
2 mentions
projectsend/projectsend ↗
ProjectSend — projectsend/projectsend · reject as embed; study portal boundary · Strong private client file areas, client groups, roles, 2FA, filters, and detailed logs, but GPL-2.0 plus a separate PHP application. It du
Research evidence
- ProjectSend — projectsend/projectsend · reject as embed; study portal boundary · Strong private client file areas, client groups, roles, 2FA, filters, and detailed logs, but GPL-2.0 plus a separate PHP application. It duplicates HALO’s Drive/content identity and is not a Convex module.
- projectsend/projectsend · https://github.com/projectsend/projectsend · 1,986 · GPL-2.0 · 2026-08-29T05:37:13Z · false · main · —
2 mentions
zqch/influencer-crm ↗
Influencer CRM — zqch/influencer-crm · reject as dependency; study only · README’s feature map is relevant—creator library, outreach, content review, calendar, analytics, roles—but API tree contains 28,846 files includin
Research evidence
- Influencer CRM — zqch/influencer-crm · reject as dependency; study only · README’s feature map is relevant—creator library, outreach, content review, calendar, analytics, roles—but API tree contains 28,846 files including committed nodemodules, no license, and no evidence of a maintainable integration boundary.
- zqch/influencer-crm · https://github.com/zqch/influencer-crm · 0 · NOASSERTION · 2026-05-14T13:44:43Z · false · main · No license endpoint result; root has no license-like file.
1 mention
arita-yuto/video-review ↗
2 · arita-yuto/video-review · Timeline comments, frame drawing, Jira/Slack integration, self-hosted review hub. · STUDY/integrate narrow review pattern · MIT; 43 stars; pushed 2026-08-11T22:04:42Z; not archived; default
Research evidence
- 2 · arita-yuto/video-review · Timeline comments, frame drawing, Jira/Slack integration, self-hosted review hub. · STUDY/integrate narrow review pattern · MIT; 43 stars; pushed 2026-08-11T22:04:42Z; not archived; default main. · Direct review job; low evidence of rights/publish/asset authority. Keep review comments tied to HALO version IDs; Buzz announces decisions, not media mutation.
1 mention
awslabs/visual-asset-management-system ↗
4 · awslabs/visual-asset-management-system · AWS-native visual asset storage, search, versioning/lineage, REST/CLI, ABAC/RBAC, pipelines. · STUDY; integrate only if AWS sidecar is justified · Apache-2.0; 137 stars; pushe
Research evidence
- 4 · awslabs/visual-asset-management-system · AWS-native visual asset storage, search, versioning/lineage, REST/CLI, ABAC/RBAC, pipelines. · STUDY; integrate only if AWS sidecar is justified · Apache-2.0; 137 stars; pushed 2026-08-25T17:58:16Z; not archived; default main. · Good sovereignty/metadata/permissions reference, but specialized spatial/AWS architecture duplicates too much for HALO. No adult consent semantics.
1 mention
beancount/beancount ↗
beancount/beancount · https://github.com/beancount/beancount · 5,949 · GPL-2.0 · 2026-08-23T20:17:45Z · false · master · Reject as product base
Research evidence
- beancount/beancount · https://github.com/beancount/beancount · 5,949 · GPL-2.0 · 2026-08-23T20:17:45Z · false · master · Reject as product base
1 mention
brightbeanxyz/brightbean-studio ↗
8 · brightbeanxyz/brightbean-studio · Self-hostable creator/agency social management: workspaces, RBAC, version history, approvals, retries, audit log, media library, client portal. · STUDY; possible sidecar only · AGPL-
Research evidence
- 8 · brightbeanxyz/brightbean-studio · Self-hostable creator/agency social management: workspaces, RBAC, version history, approvals, retries, audit log, media library, client portal. · STUDY; possible sidecar only · AGPL-3.0; 2,214 stars; pushed 2026-08-13T09:13:17Z; not archived; default main. · Broadest publishing/approval comparator in the screened set; still generic social content and AGPL. Verify claims in code/trial before relying on them.
1 mention
c2pa-org/specifications ↗
17 · c2pa-org/specifications · Public C2PA provenance specification. · INTEGRATE standard, not app · CC-BY-4.0; 204 stars; pushed 2026-08-20T12:07:15Z; not archived; default main. · Use the standard/specification through
Research evidence
- 17 · c2pa-org/specifications · Public C2PA provenance specification. · INTEGRATE standard, not app · CC-BY-4.0; 204 stars; pushed 2026-08-20T12:07:15Z; not archived; default main. · Use the standard/specification through a maintained library or provider. Do not treat the repo as a rights system.
1 mention
Comfy-Org/ComfyUI ↗
20 · Comfy-Org/ComfyUI · Node/graph-based generative media workflow UI. · REJECT as control plane; study provider seam · GPL-3.0; 130,515 stars; pushed 2026-08-29T06:47:39Z; not archived; default master. · Powerful gener
Research evidence
- 20 · Comfy-Org/ComfyUI · Node/graph-based generative media workflow UI. · REJECT as control plane; study provider seam · GPL-3.0; 130,515 stars; pushed 2026-08-29T06:47:39Z; not archived; default master. · Powerful generation graph, but no creator consent, version approval, delivery receipt, or OFM rights semantics. Keep generation behind HALO's job/approval boundary.
1 mention
daminikhq/daminik ↗
5 · daminikhq/daminik · DAM/CDN “single source of truth,” S3-compatible storage, EXIF-capable PHP app, workers. · STUDY DAM primitives · MIT; 292 stars; pushed 2026-07-27T08:17:47Z; not archived; default main. · Useful b
Research evidence
- 5 · daminikhq/daminik · DAM/CDN “single source of truth,” S3-compatible storage, EXIF-capable PHP app, workers. · STUDY DAM primitives · MIT; 292 stars; pushed 2026-07-27T08:17:47Z; not archived; default main. · Useful byte/metadata pattern; PHP/MySQL/S3 stack and no visible approval/rights model make direct adoption duplicative.
1 mention
elonen/clapshot ↗
3 · elonen/clapshot · Self-hosted video/media review, ingestion, synchronized playback, frame annotations, threaded comments, FFmpeg/thumbnailing, auth integrations. · STUDY; sidecar only · GPL-2.0; 265 stars; pushed 202
Research evidence
- 3 · elonen/clapshot · Self-hosted video/media review, ingestion, synchronized playback, frame annotations, threaded comments, FFmpeg/thumbnailing, auth integrations. · STUDY; sidecar only · GPL-2.0; 265 stars; pushed 2026-08-12T03:46:46Z; not archived; default master. · Strong review/ingest pattern; GPL and Linux/network operation are material adoption friction. No creator consent/publish graph. Buzz gets typed review links only.
1 mention
eoyilmaz/stalker ↗
6 · eoyilmaz/stalker · Production asset management library, project/tasks/milestones, asset references, customizable object model, PostgreSQL/SQLite. · STUDY data model · LGPL-3.0; 207 stars; pushed 2025-06-09T13:15:45Z;
Research evidence
- 6 · eoyilmaz/stalker · Production asset management library, project/tasks/milestones, asset references, customizable object model, PostgreSQL/SQLite. · STUDY data model · LGPL-3.0; 207 stars; pushed 2025-06-09T13:15:45Z; not archived; default develop. · Valuable production lineage vocabulary; README explicitly says no graphical UI and points to other applications. Not a content studio or creator portal.
1 mention
firefly-iii/firefly-iii ↗
firefly-iii/firefly-iii · https://github.com/firefly-iii/firefly-iii · 24,449 · AGPL-3.0 · 2026-08-29T04:23:29Z · false · main · Reject as domain authority
Research evidence
- firefly-iii/firefly-iii · https://github.com/firefly-iii/firefly-iii · 24,449 · AGPL-3.0 · 2026-08-29T04:23:29Z · false · main · Reject as domain authority
1 mention
gitroomhq/postiz-app ↗
7 · gitroomhq/postiz-app · Agentic social scheduling, multi-platform publishing, public API/SDK. · INTEGRATE only after license/policy review · AGPL-3.0; 35,242 stars; pushed 2026-08-29T00:07:57Z; not archived; default m
Research evidence
- 7 · gitroomhq/postiz-app · Agentic social scheduling, multi-platform publishing, public API/SDK. · INTEGRATE only after license/policy review · AGPL-3.0; 35,242 stars; pushed 2026-08-29T00:07:57Z; not archived; default main. · Useful publisher sidecar; AGPL and external platform account policies matter. It cannot decide whether a creator may be represented by a post.
1 mention
HKUDS/ViMax ↗
13 · HKUDS/ViMax · Director/screenwriter/producer/generator agentic video pipeline, artifacts/storyboards/render checkpoints. · STUDY generation pipeline · MIT; 12,142 stars; pushed 2026-07-29T08:56:47Z; not archived; de
Research evidence
- 13 · HKUDS/ViMax · Director/screenwriter/producer/generator agentic video pipeline, artifacts/storyboards/render checkpoints. · STUDY generation pipeline · MIT; 12,142 stars; pushed 2026-07-29T08:56:47Z; not archived; default main. · Strong generation/iteration analogy; README does not establish creator consent, adult safety, version approval, or delivery authority. Keep as a provider job behind HALO.
1 mention
kukuhtw/ppv_stream_rust ↗
16 · kukuhtw/ppvstreamrust · Creator video upload/catalog, protected HLS, watermarking, access/payment ledger, storage workers. · STUDY delivery/protection · Apache-2.0; 61 stars; pushed 2026-06-21T09:02:35Z; not archive
Research evidence
- 16 · kukuhtw/ppvstreamrust · Creator video upload/catalog, protected HLS, watermarking, access/payment ledger, storage workers. · STUDY delivery/protection · Apache-2.0; 61 stars; pushed 2026-06-21T09:02:35Z; not archived; default main. · Relevant to paid delivery and watermark language, but it is a creator commerce app, not agency approval/rights control; README itself says production hardening remains.
1 mention
moodle/moodle ↗
9 · moodle/moodle · Full LMS, competencies, courses and badges. · Study/possible later sidecar; GPL-3.0. Reject wholesale replacement because it duplicates identity, creator boundaries, and HALO authority.
Research evidence
- 9 · moodle/moodle · Full LMS, competencies, courses and badges. · Study/possible later sidecar; GPL-3.0. Reject wholesale replacement because it duplicates identity, creator boundaries, and HALO authority.
1 mention
moov-io/accounts ↗
moov-io/accounts · https://github.com/moov-io/accounts · 56 · Apache-2.0 · 2020-10-28T02:54:38Z · true · master · Reject; archived
Research evidence
- moov-io/accounts · https://github.com/moov-io/accounts · 56 · Apache-2.0 · 2020-10-28T02:54:38Z · true · master · Reject; archived
1 mention
myshell-ai/OpenVoice ↗
15 · myshell-ai/OpenVoice · Instant voice cloning, style control, cross-lingual generation. · STUDY/provider adapter · MIT; 37,348 stars; pushed 2025-04-19T16:00:00Z; not archived; default main. · Similar to GPT-SoVITS;
Research evidence
- 15 · myshell-ai/OpenVoice · Instant voice cloning, style control, cross-lingual generation. · STUDY/provider adapter · MIT; 37,348 stars; pushed 2025-04-19T16:00:00Z; not archived; default main. · Similar to GPT-SoVITS; useful comparative provider evidence, not a safe content workflow.
1 mention
OrangeViolin/content-pipeline ↗
11 · OrangeViolin/content-pipeline · Claude Code skill claiming material→draft→layout→image→multi-platform distribution with human direction. · STUDY agent workflow; do not embed · MIT; 216 stars; pushed 2026-04-12T18:56
Research evidence
- 11 · OrangeViolin/content-pipeline · Claude Code skill claiming material→draft→layout→image→multi-platform distribution with human direction. · STUDY agent workflow; do not embed · MIT; 216 stars; pushed 2026-04-12T18:56:12Z; not archived; default main. · Good proposal for prompt-to-derivative orchestration; a skill is not a media/rights authority. Buzz can invoke a bounded proposal action after HALO supplies approved context.
1 mention
pavlohushuliak/my-influencer ↗
10 · pavlohushuliak/my-influencer · UGC creator/brand matching, briefs, applications, content delivery/performance. · STUDY vocabulary; reject dependency · NOASSERTION; 21 stars; pushed 2025-10-24T22:58:42Z; not archived
Research evidence
- 10 · pavlohushuliak/my-influencer · UGC creator/brand matching, briefs, applications, content delivery/performance. · STUDY vocabulary; reject dependency · NOASSERTION; 21 stars; pushed 2025-10-24T22:58:42Z; not archived; default main. · Direct creator/brief signal but no verified license source (recursive tree contained no license-like path), no proven adult rights, and no evidence of production maturity.
1 mention
QmiAI/Qmedia ↗
12 · QmiAI/Qmedia · Local multimodal content search/RAG for image/text/short video, with local deployment. · STUDY/search adapter · MIT; 633 stars; pushed 2026-04-09T05:48:58Z; not archived; default main. · Could help pr
Research evidence
- 12 · QmiAI/Qmedia · Local multimodal content search/RAG for image/text/short video, with local deployment. · STUDY/search adapter · MIT; 633 stars; pushed 2026-04-09T05:48:58Z; not archived; default main. · Could help private discovery, but search must be rights-filtered before indexing and cannot grant reuse.
1 mention
RVC-Boss/GPT-SoVITS ↗
14 · RVC-Boss/GPT-SoVITS · Few-shot TTS/voice conversion WebUI, training data and multilingual inference. · STUDY/provider adapter; no direct rights transfer · MIT; 61,311 stars; pushed 2026-08-18T09:16:25Z; not archived
Research evidence
- 14 · RVC-Boss/GPT-SoVITS · Few-shot TTS/voice conversion WebUI, training data and multilingual inference. · STUDY/provider adapter; no direct rights transfer · MIT; 61,311 stars; pushed 2026-08-18T09:16:25Z; not archived; default main. · Model capability only. Consent, likeness, provenance, deletion, and human release are HALO responsibilities.
1 mention
shotgunsoftware/python-api ↗
18 · shotgunsoftware/python-api · Official Autodesk Flow Production Tracking Python API. · STUDY/API comparator; legal review · NOASSERTION; 321 stars; pushed 2026-08-24T15:08:58Z; not archived; default master. · LICENSE
Research evidence
- 18 · shotgunsoftware/python-api · Official Autodesk Flow Production Tracking Python API. · STUDY/API comparator; legal review · NOASSERTION; 321 stars; pushed 2026-08-24T15:08:58Z; not archived; default master. · LICENSE was inspected: BSD-style redistribution text with Shotgun-specific attribution/disclaimer, but GitHub still reports NOASSERTION. Do not relicense or copy without review.
1 mention
shotgunsoftware/tk-core ↗
19 · shotgunsoftware/tk-core · Official Flow Production Tracking Toolkit core API. · REJECT direct reuse; study boundary · NOASSERTION; 104 stars; pushed 2026-08-28T15:41:23Z; not archived; default master. · LICENSE was
Research evidence
- 19 · shotgunsoftware/tk-core · Official Flow Production Tracking Toolkit core API. · REJECT direct reuse; study boundary · NOASSERTION; 104 stars; pushed 2026-08-28T15:41:23Z; not archived; default master. · LICENSE was inspected and expressly limits use to eligible Shotgun/Flow customers and internal/non-commercial use. This is not a general OSS dependency.
1 mention
shoz496351/reelbase ↗
9 · shoz496351/reelbase · Recent prototype claiming creator portal, tokenized upload, rights-aware library, deterministic candidate validation, AI strategist. · STUDY only; reject adoption this wave · NOASSERTION; 0 star
Research evidence
- 9 · shoz496351/reelbase · Recent prototype claiming creator portal, tokenized upload, rights-aware library, deterministic candidate validation, AI strategist. · STUDY only; reject adoption this wave · NOASSERTION; 0 stars; pushed 2026-08-09T09:12:27Z; not archived; default main. · README is unusually close to the problem and explicitly calls itself a take-home prototype. Recursive tree inspection found no license-like path; no license source to rely on. The rights-before-model and invented-ID rejection ideas are worth fixture tests.
3 mentions
0xDevDav/AirChatter ↗
Archived narrow extension
Research evidence
- The exact-onlyfans repositories are useful as vocabulary, not as foundations: AirChatter is archived and only a Chrome assistant; of-crm describes admin/supervisor/chatter roles, clocking, sales, shifts and reports but has no declared licence and a placeholder middleware note; velvet-desktop is an unlicensed, empty/low-signal repository; and onlyfans-crm-comparison is a CC-BY comparison dataset, not an operating system. This is a confirmed market gap, not a reason to lower the quality bar.
- 0xDevDav/AirChatter · https://github.com/0xDevDav/AirChatter · 1 · MIT · 2026-02-08T18:42:42Z · true · master
- 0xDevDav/AirChatter · https://github.com/0xDevDav/AirChatter · 1 · MIT · 2026-02-08T18:42:42Z · true · master · Archived Chrome extension for Chatterly, not a direct OFM system; assistant concept requires review/personalization. MIT does not overcome irrelevance/staleness.
3 mentions
EddyRoig-1/velvet-desktop ↗
Empty or low-signal and unlicensed
Research evidence
- The exact-onlyfans repositories are useful as vocabulary, not as foundations: AirChatter is archived and only a Chrome assistant; of-crm describes admin/supervisor/chatter roles, clocking, sales, shifts and reports but has no declared licence and a placeholder middleware note; velvet-desktop is an unlicensed, empty/low-signal repository; and onlyfans-crm-comparison is a CC-BY comparison dataset, not an operating system. This is a confirmed market gap, not a reason to lower the quality bar.
- EddyRoig-1/velvet-desktop · https://github.com/EddyRoig-1/velvet-desktop · 0 · NOASSERTION · 2026-01-10T23:29:06Z · false · main
- EddyRoig-1/velvet-desktop · https://github.com/EddyRoig-1/velvet-desktop · 0 · NOASSERTION · 2026-01-10T23:29:06Z · false · main · Tree had no license-like source and no usable README evidence. Reject.
3 mentions
keydbeats1/of-crm ↗
Unlicensed incomplete prototype
Research evidence
- The exact-onlyfans repositories are useful as vocabulary, not as foundations: AirChatter is archived and only a Chrome assistant; of-crm describes admin/supervisor/chatter roles, clocking, sales, shifts and reports but has no declared licence and a placeholder middleware note; velvet-desktop is an unlicensed, empty/low-signal repository; and onlyfans-crm-comparison is a CC-BY comparison dataset, not an operating system. This is a confirmed market gap, not a reason to lower the quality bar.
- keydbeats1/of-crm · https://github.com/keydbeats1/of-crm · 0 · NOASSERTION · 2025-08-10T22:25:51Z · false · main
- keydbeats1/of-crm · https://github.com/keydbeats1/of-crm · 0 · NOASSERTION · 2025-08-10T22:25:51Z · false · main · README describes a role/shift/sales concept, but the tree had no license-like source. No reuse permission; reject as dependency.
3 mentions
kgorlov/RecruitingOS-Adult-Recruiting-CRM ↗
Marketing page without inspectable product source
Research evidence
- RecruitingOS — kgorlov/RecruitingOS-Adult-Recruiting-CRM · reject · README explicitly says it is a private commercial product page and that production source/deployment/demo are shared only after contact. The workflow is relevant, but there is no inspectable implementation or license; do not treat marketing copy as OSS evidence.
- kgorlov/RecruitingOS-Adult-Recruiting-CRM · https://github.com/kgorlov/RecruitingOS-Adult-Recruiting-CRM · 0 · NOASSERTION · 2026-06-04T21:10:06Z · false · master · No license endpoint result; root has no license-like file.
- kgorlov/RecruitingOS-Adult-Recruiting-CRM · https://github.com/kgorlov/RecruitingOS-Adult-Recruiting-CRM · 0 · NOASSERTION · 2026-06-04T21:10:06Z · false · master · Tree had no license-like source; README presents a private/commercial adult recruiting workflow. Treat as interview/market signal only, not code.
3 mentions
vhvyvy/FlowOF ↗
Unlicensed and unsafe credential example
Research evidence
- FlowOF — vhvyvy/FlowOF · reject · The README and tree are unusually relevant—tenant onboarding, source mapping, chatter portal, KPI, finance, and admin routes—but the repo has no license, and its README contains a plaintext database credential in a deployment example. Do not copy, deploy, or repeat the credential. API metadata says 261 files and last push 2026-08-01.
- vhvyvy/FlowOF · https://github.com/vhvyvy/FlowOF · 0 · NOASSERTION · 2026-08-01T12:56:23Z · false · main · No license endpoint result; root has no license-like file.
- vhvyvy/FlowOF · https://github.com/vhvyvy/FlowOF · 0 · NOASSERTION · 2026-08-01T12:56:23Z · false · main · Tree had no license-like source. Public README also exposed a credential, so it is a security negative finding; do not copy, run, publish, or repeat the secret.
2 mentions
Barklim/onlyfClient ↗
Stale, unlicensed frontend
Research evidence
- OFTtracker — Barklim/onlyfClient · reject · Actual README describes an OnlyFans autochat/tracker frontend and related repos, but direct API metadata says last push 2023-12-09 despite newer search-index timestamps. No license file; stale multi-repo frontend is not a safe HALO donor.
- Barklim/onlyfClient · https://github.com/Barklim/onlyfClient · 24 · NOASSERTION · 2023-12-09T11:08:36Z · false · main · No license endpoint result; root has no license-like file.
2 mentions
BBPOTKLO/OFVAULT ↗
Practice project with unsafe platform boundary
Research evidence
- OFVAULT — BBPOTKLO/OFVAULT · reject · README calls it a small practice project built in a few hours and warns that parts may need adjustment. No license file. Credential/content archival and platform-scraping risk make it unsuitable for HALO’s vault.
- BBPOTKLO/OFVAULT · https://github.com/BBPOTKLO/OFVAULT · 1 · NOASSERTION · 2026-05-09T23:16:03Z · false · main · No license endpoint result; root has no license-like file.
2 mentions
behavero/agencyos ↗
Generic starter, not the claimed agency system
Research evidence
- AgencyOS — behavero/agencyos · reject · Search description says gamified creator-economy CRM, but README is a generic Next.js starter with an “OnyxOS” chat/whale-priority section. No license and no matching agency domain implementation.
- behavero/agencyos · https://github.com/behavero/agencyos · 0 · NOASSERTION · 2026-02-06T19:25:41Z · false · main · No license endpoint result; root has no license-like file.
2 mentions
CLEMENT3Z/agency ↗
Empty repository
Research evidence
- Creator OS — CLEMENT3Z/agency · reject · API says the repository is empty (0 KB), has no license, and only a 0-star OFM/AI-OFM tool description.
- CLEMENT3Z/agency · https://github.com/CLEMENT3Z/agency · 0 · NOASSERTION · 2026-07-16T16:11:05Z · false · main · Repository is empty; no license endpoint/root license file.
2 mentions
Haseebcodejourney/creatorflow-dashboard ↗
Small unlicensed demo
Research evidence
- CreatorFlow Dashboard — Haseebcodejourney/creatorflow-dashboard · reject · README is a 0-star React/Tailwind demo description for adult creator calendar/analytics/fan messaging/compliance; no license and no implementation evidence beyond a 115 KB repository.
- Haseebcodejourney/creatorflow-dashboard · https://github.com/Haseebcodejourney/creatorflow-dashboard · 0 · NOASSERTION · 2026-05-24T10:02:43Z · false · main · No license endpoint result; root has no license-like file.
2 mentions
Manish-Prajapati32/Influencer-Connect ↗
Claims exceed inspectable implementation
Research evidence
- Influencer Connect — Manish-Prajapati32/Influencer-Connect · reject · README claims broad creator/editor/writer/designer/voice-artist role dashboards, messaging, AI recommendations, subscriptions, RBAC, and RLS, but the repository is only 124 KB with no license and API last push 2026-02-11. Claims exceed verifiable implementation evidence.
- Manish-Prajapati32/Influencer-Connect · https://github.com/Manish-Prajapati32/Influencer-Connect · 0 · NOASSERTION · 2026-02-11T23:58:32Z · false · main · No license endpoint result; root has no license-like file.
2 mentions
Nayzerftn/ofm-connect ↗
Large unlicensed repository without inspectable evidence
Research evidence
- OFM-Connect — Nayzerftn/ofm-connect · reject · API reports a 201,264 KB repository, 0 stars, no license, and README is only a product/deploy link. Size and absence of inspectable documentation make it an unreliable lead.
- Nayzerftn/ofm-connect · https://github.com/Nayzerftn/ofm-connect · 0 · NOASSERTION · 2026-05-20T16:54:00Z · false · main · No license endpoint result; root has no license-like file.
No repositories match this view. Reset the filters or search a broader capability.
Evidence library
Read every source report.
The catalogue is an index. The full reasoning, verification ledgers, licences, negative findings, product evidence and synthetic proof plans remain visible in the generated report pages.
research/sourcing-campaign/SYNTHESIS.md
Sourcing decision
Cross-lane architecture and experiment order
Read report → research/sourcing-campaign/full-saas-systems.mdFull-SaaS systems
Complete systems, compositions, Buzz boundary, and OFM donors
Read report → research/sourcing-campaign/web-live-products.mdLive products + wide GitHub funnel
1,781 unique discovery results, 30 promoted candidates, and commercial benchmarks
Read report → research/sourcing-campaign/github-wide-funnel.mdGitHub wide funnel
Workflow queries, project-specific source inspection, verification, and rejects
Read report → research/sourcing-campaign/operator-signals.mdOperator signals
OFM personas, pain clusters, daily loop, vocabulary, and confidence labels
Read report → research/sourcing-campaign/local-corpus.mdLocal corpus
Candidates recovered from the local RepoCard and curated repository corpora
Read report → research/sourcing-campaign/buzz-integration.mdBuzz integration
Authority split, typed links, events, agents, approvals, and production blockers
Read report → research/ofm-domain-campaign/01-creator-lifecycle.mdCreator lifecycle
Acquisition through consent, access, renewal, export, and exit
Read report → research/ofm-domain-campaign/02-chatter-revenue-ops.mdChatter revenue operations
Queues, shifts, playbooks, conversations, QA, attribution, and handoffs
Read report → research/ofm-domain-campaign/03-content-studio-ai.mdContent studio + AI
Briefs, versions, approval, Drive, customs, publishing, and provenance
Read report → research/ofm-domain-campaign/04-money-ledger-payouts.mdMoney, ledger + payouts
Source events, liabilities, statements, reconciliation, rails, and legal gates
Read report → research/ofm-domain-campaign/05-gamification-chatter-training.mdTraining + gamification
Simulation, rubrics, coaching, certification, rewards, fairness, and wellbeing
Read report → research/ofm-domain-campaign/06-owner-intelligence-platform.mdOwner intelligence
Exception-first control, decisions, evidence, metrics, and closure
Read report → research/ofm-domain-campaign/INTERNAL-PRIOR-ART.mdInternal prior art
Reusable HALO and Oracle patterns with explicit non-transfer boundaries
Read report →Generated by site/scripts/generate-ofm-hub.mjs from canonical Markdown · machine-readable catalogue: /data/ofm-repository-catalog.json · research-only