Kollab vs Mike

The primitive here is a shared prompt-and-context registry with a workflow runner bolted on — which is a real problem, but the DX bet is squarely on the no-code crowd, not engineers who'd actually compose this into something. The Skills layer sounds like saved prompts with parameters, and there's no public API, no SDK, no repo to audit — so the 'full participant' positioning is marketing until I can call an agent from my own code. The moment of truth is building your first Skill, and if that's a form with dropdowns rather than a function signature, I'm out.

Self-hosted legal AI that runs on your own Claude or Gemini API key is genuinely clever — the pricing model alone makes this worth exploring. The codebase is clean and the tabular citation view is the kind of UX detail that shows someone actually thought about the legal workflow. Deploy this for any firm that's been priced out of Harvey.

The direct competitors here are Notion AI with its database integrations, and more pointedly, Microsoft Copilot Pages — both of which already sit inside workflows teams actually use daily, backed by companies that own the productivity stack. The specific scenario where Kollab breaks is at the organizational scale: persistent memory across sessions sounds great until you have 200 employees, conflicting contexts, and no audit trail for what the agent 'remembered.' What kills this in 12 months isn't a competitor — it's that Slack and Notion each ship a native Skills-equivalent, and the integration layer Kollab's Bots occupy evaporates overnight.

Solo dev projects in legal tech carry serious liability risk — if the model hallucinates a clause or misses a citation, the consequences aren't a bad tweet, they're malpractice exposure. Until this has real-world usage data from actual attorneys and independent security audits, enterprise law firms should stay cautious. Also, Claude Sonnet or Gemini Flash are not the same as GPT-5.5 fine-tuned on case law.