HALO Knowledge Docs
Generated knowledge spine · research/sourcing-campaign/local-corpus.md

21 · Local corpus findings

Candidates recovered from the 1.36M RepoCard spine and 307k curated repository corpus.

Generated from research/sourcing-campaign/local-corpus.md · regenerate with /opt/homebrew/opt/node@24/bin/node site/scripts/generate-docs.mjs

Local corpus findings — system-class candidates

Date: 2026-08-29

Status: local candidate generation complete; convergence is recorded in research/sourcing-campaign/SYNTHESIS.md.

Corpus actually searched

  • SISO_Agent_Base/research/repo-catalog/identity/identity.sqlite contains

1,358,200 repo_card rows.

  • SISO_Research/siso-foundry/pipelines/github/awesome/catalog_full.sqlite

contains 307,180 deduplicated repositories and curated list/section edges.

  • The older HALO OSS report did not use either corpus.

The identity spine's free-text layer is lexical and noisy. The curated corpus is most useful for human-maintainer co-placement (projects repeatedly filed as alternatives). Both are candidate generators; GitHub and licence truth must be refreshed before use.

Scope correction

The earlier hunt searched for replacements for existing screens. Shaan's clarification changes the product unit: HALO is a multi-persona agency SaaS, not a set of unrelated features. The system has to serve owners/admins, managers, chatters, creators/models, referral partners, and staff with different modules and authority.

This makes complete products and coherent platform compositions first-class candidates: CRM/relationship OS + chatter workspace + knowledge/notes + agency operations, with one identity and evidence model wherever possible.

First verified AI/Salesforce family

Metadata below was refreshed with gh api repos/OWNER/NAME on 2026-08-29.

RepositoryFresh evidenceInitial reading
twentyhq/twenty55,817★; pushed 2026-08-29; active; default main; API reports NOASSERTIONDescribes itself as “The open alternative to Salesforce, designed for AI.” Strong system-class candidate. Actual root licence is mostly AGPLv3, with enterprise-marked files and MIT SDK/UI/app packages plus a Twenty Application Exception.
qrev-ai/qrev362★; AGPL-3.0; pushed 2026-02-07; activeExplicit “AI First alternative to Salesforce.” Smaller and less fresh; needs product-depth proof.
1Panel-dev/CordysCRM2,660★; pushed 2026-08-28; active; API NOASSERTIONPrivate-deployable AI CRM. Root licence is GPLv3 plus extra logo/maintainer-change terms; legal review required before any reuse.
relaticle/relaticle1,563★; AGPL-3.0; pushed 2026-08-29; activeCRM with native AI agents, 37 MCP tools, REST API, Laravel/Filament. Strong niche candidate for AI-operable records.
WuKongOpenSource/Wukong-AICRM1,237★; pushed 2026-07-06; active; API NOASSERTIONConversational Salesforce alternative. Renamed from the queried AI_CRM path. Actual licence is non-commercial/source-available and explicitly requires permission for production, client work, SaaS, and competing CRM use; study/buy only unless licensed.
pdovhomilja/nextcrm-app684★; MIT; pushed 2026-08-10; activeNext.js/React/shadcn CRM spanning projects, invoicing, documents, email, and AI. Smaller but unusually close to HALO's frontend shape.
marmelab/atomic-crm1,210★; MIT; pushed 2026-08-21; activeFull React/shadcn/Supabase CRM. Useful exact-UI-stack donor, but Supabase-centric and not a complete agency OS.

First verified modular/full-system family

RepositoryFresh evidenceInitial reading
nocobase/nocobase23,921★; pushed 2026-08-29; active; API NOASSERTIONAI + no-code platform explicitly designed to build production business systems. Actual licence is a custom NocoBase agreement with Community and Commercial editions; needs clause-level review before client adoption.
cortezaproject/corteza2,140★; Apache-2.0; pushed 2026-08-27; activeLow-code platform repeatedly co-placed with CRM systems; curated descriptions identify CRM, unified workspace, enterprise messaging, and records-based apps. High-priority system candidate because it crosses modules rather than replacing one screen.
erxes/erxes4,074★; pushed 2026-08-29; active; API NOASSERTION“Experience Operating System” joining marketing, sales, operations, and support. Actual core is AGPLv3 with enterprise plugins and an explicit restriction against hosting a competing SaaS.
frappe/erpnext38,621★; GPL-3.0; pushed 2026-08-29; activeFull ERP foundation with accounting/HR/CRM/business workflows. Deep but likely a parallel datastore and product shell; must be evaluated as sidecar/reference, not assumed replacement.
saeloun/miru-web266★; MIT; pushed 2026-08-22; activeAgency-shaped time tracking, invoicing, expenses/payments, and employee benefits. Narrower than an OS but directly relevant to agency operations.

First verified chatter-workspace family

RepositoryFresh evidenceInitial reading
mattermost/mattermost38,937★; pushed 2026-08-29; active; API NOASSERTIONMature secure collaboration platform. Source is primarily AGPLv3/commercial, compiled distribution has an MIT route, and admin/config/frontend paths have Apache-2.0 terms. Strong sidecar candidate; not a casual code-lift.
zulip/zulip25,786★; Apache-2.0; pushed 2026-08-28; activeThreaded team chat with a clean API licence signal. Strong candidate for chatter channels, shift handoffs, and durable topic history.
RocketChat/Rocket.Chat46,041★; pushed 2026-08-29; active; API NOASSERTIONFull communications OS. Core outside ee/ is MIT; enterprise directories are separately licensed.
element-hq/element-web13,408★; AGPL-3.0; pushed 2026-08-28; activeMatrix collaboration client; useful where federation/E2EE matters, but brings a protocol/server architecture rather than a bounded chat module.

Curated co-placement also surfaced discourse/discourse, jitsi/jitsi-meet, linagora/Twake, nextcloud/server, ONLYOFFICE/CommunityServer, and Teamlinker/Teamlinker. These remain unpromoted until fresh repository and first-party product verification is complete.

Knowledge/workspace candidates the first hunt missed

The local classified corpus contains toeverything/AFFiNE, AppFlowy-IO/AppFlowy, usememos/memos, outline/outline, TriliumNext/Trilium, growilabs/growi, siyuan-note/siyuan, and other knowledge systems. Their relevant job is not generic note-taking: creator relationship memory, meeting notes, SOPs, briefs, decisions, handoffs, and searchable operational history.

AFFiNE is already known elsewhere in the SISO workspace as a complete knowledge/docs module. Its source/licence boundary has prior warnings and must be re-verified for this client; “open source” is not sufficient permission to lift its server code.

Convergence questions

  1. Is Twenty the remembered AI Salesforce-like product, or were QRev/Cordys/Relaticle

closer to what Camron liked?

  1. Does HALO remain the authority with full products mounted as sidecars, or is one full

platform a credible new foundation?

  1. Which chatter workspace best supports role-scoped channels, shift handoffs, QA,

automations, and creator isolation without creating a second employee directory?

  1. Can knowledge, chat, and CRM share identity/navigation while keeping money and creator

records authoritative in one place?

  1. Which licences permit an internal client deployment versus code reuse or a future

commercial HALO product?

Canonical source remains research/sourcing-campaign/local-corpus.md. This HTML is a generated projection; edit the source, then run generate-docs.mjs.