A sourced, dated comparison across personal open-source agents, self-hosted AI platforms, and premium enterprise suites—with honest Lorenz maturity labels.
A category-level view across personal open-source agents, self-hosted AI platforms, and premium enterprise suites. Detailed profiles and primary sources are available on the Compare page.
On smaller screens, focus this region and scroll horizontally to read every category.
| Decision area | Lorenz | Personal open source | Open-source platforms | Premium enterprise |
|---|---|---|---|---|
| Primary job | Lorenz Operate AI across people, knowledge, agents, models, and infrastructure under one evidence and policy plane. | Give an individual or technical team a powerful self-hosted assistant or agent computer. | Build private chat, RAG applications, agents, and visual workflows on infrastructure you manage. | Bring AI into an established productivity suite, cloud, enterprise-search layer, or system of record. |
| Hosting and model control | Lorenz Approved local, in-country, managed, and external lanes can share one policy contract; effective sovereignty depends on tenant configuration. | Strong local and self-host freedom; the operator owns hardening, provider choices, availability, and compliance. | Usually strong self-hosting and multi-model choice, with enterprise operations varying by product, edition, and license. | Strong managed controls and regional options, normally within the vendor's cloud and model ecosystem. |
| Enterprise identity and tenancy | Lorenz Tenant/user/role context, forced RLS in critical domains, governed corporate identity, scoped workspaces, and fail-closed erasure. | Often optimized for a trusted operator or project; team isolation and identity are deployment responsibilities. | Multi-user, SSO, RBAC, and ACL depth range from community features to enterprise editions. | Typically strong SSO, SCIM, RBAC, audit, lifecycle, and permission inheritance. |
| Knowledge and grounding | Lorenz MNEME plus a source-grounded Second Brain with citations, revision, conflict handling, ACL-first retrieval, and explicit degradation. | Useful memory and document context; enterprise permission propagation and source governance are commonly operator-built. | RAG and document chat are mature strengths, especially in Dify, AnythingLLM, Open WebUI, and LibreChat. | Strong connected company knowledge, often inheriting permissions from the vendor ecosystem or search index. |
| Actions, approval, and recovery | Lorenz Guardian decisions, risk/DLP policy, Action Journal, evidence, idempotency, work packets, and undo metadata share one control plane. | Powerful tools and configurable approvals; the safety and recovery contract depends on the chosen setup. | Tool approvals and workflow logs exist in leading products, while cross-workspace recovery semantics vary. | Strong administrative governance, with effect evidence and rollback shaped by each connected application. |
| Durable agent execution | Lorenz Controlled-preview immutable graphs, fenced leases, signed checkpoints, lineage, Project Agent, and web/iOS supervision. | Strong autonomous loops and scheduled work, generally optimized for direct operator control. | Visual workflows and agent graphs are a core strength for builder platforms; persistence models differ. | Rapidly expanding agent builders, registries, orchestration, and governance at enterprise scale. |
| Voice, mobile, and channels | Lorenz Web and native iOS, streaming voice, account-scoped voice identity, email/calendar/meeting work, and governed connected channels. | OpenClaw leads on chat-channel breadth; Agent Zero leads on a general agent desktop. | Primarily web-first; voice, desktop, embed, and mobile options vary by product. | Polished cross-device experiences and deep native distribution in existing work suites. |
| Adoption and ecosystem | Lorenz High-control operating model with an emerging ecosystem; several differentiated v3 capabilities are still preview or activation-gated. | Fast experimentation, active communities, broad plugins, and low entry cost. | Mature communities and quick local value; enterprise support and license terms differ. | Strongest distribution, support, procurement maturity, certifications, and connector estates. |
Lorenz is optimized for organizations that need execution boundaries, deployment choice, tenant isolation, and auditable runtime behavior together.
Lorenz differentiates through one policy and evidence plane across knowledge, models, tools, approvals, durable agents, and recovery.
Lorenz keeps the control plane stable while models and deployment lanes evolve, but premium suites currently lead on distribution, support, and connector breadth.
The profiles below summarize documented positioning, strengths, and buying considerations. They compare product defaults—not a perfectly customized deployment—and link to primary sources reviewed on September 2, 2026.
Open-source personal agent
Self-hosted gateway connecting chat channels to coding agents, tools, skills, cron, and webhooks.
Primary sources
Open agent computer
Dockerized Linux desktop, browser, documents, projects, memory, skills, plugins, and host bridge.
Primary sources
Open-core agent builder
Visual platform for production agent workflows, knowledge pipelines, plugins, and application publishing.
Primary sources
Local AI workspace
MIT-licensed local-first document chat, RAG, agents, workflows, voice, and multi-user self-hosting.
Self-hosted enterprise workspace
Multi-model workspace with enterprise identity, permissions, logging, HA, on-prem, and air-gap options.
Primary sources
Self-hosted multi-model chat
MIT-licensed chat with agents, MCP, RAG, artifacts, code execution, approvals, and granular ACLs.
Premium horizontal work AI
Chat, company knowledge, deep research, workspace agents, Codex, plugins, and office extensions.
Premium productivity ecosystem
AI and agents embedded in Microsoft 365, Graph, Entra, Purview, and Power Platform.
Primary sources
Premium agent control plane
Enterprise search, no-code and coded agents, registry, identity, gateway, and governance on Google Cloud.
Primary sources
Premium knowledge and coding AI
Deep knowledge and coding work with large context, projects, connectors, Claude Code, and enterprise administration.
Premium enterprise search and agents
Permission-aware enterprise search and agents across a large connector estate.
Primary sources
Premium CRM agents
CRM-native agents operating on Salesforce data and workflows through the Einstein Trust Layer.
Primary sources
Open source does not automatically mean secure or insecure. Premium does not automatically mean sovereign or non-sovereign. Effective posture depends on edition, configuration, providers, identity, infrastructure, and operations.
Capability maturity
Lorenz publishes status at capability level. Source code, controlled preview, tenant activation, and production proof are not interchangeable.
Bind work to a user, tenant, role, policy, approval, audit record, and recovery path.
Current evidence
Tenant context, forced RLS in critical domains, Guardian, Action Journal, DLP/risk gateway, and work packets are implemented.
Market context
Premium suites are strong on identity and administration; open-source products range from personal defaults to enterprise ACL editions.
Compile governed sources into citable pages with revision, conflict, and explicit degradation state.
Current evidence
Second Brain is implemented; contextual Retrieval v2 has signed qualification but remains tenant-activation gated.
Market context
RAG is common across the market; source compilation, conflict lineage, and fail-closed activation are Lorenz's sharper claim.
When the controlled preview is activated, choose Auto, Quick, Think, Research, or Create through server-owned policy while unqualified modes remain visibly blocked.
Current evidence
Backend, web, and iOS contracts plus Routing Receipt and Context Manifest are implemented; Analyze and Build remain unavailable and DEV activation is open.
Market context
Many assistants expose model or mode selectors. Lorenz focuses on making the resolved route, source use, egress, cost band, and degradation inspectable.
Bind sources, claims, citations, runtime identity, results, and completeness to content-addressed evidence.
Current evidence
Research Evidence is an accepted backend foundation; the fixed Analysis package and graph exist locally but live signed sandbox qualification is pending.
Market context
The differentiation is not a longer answer: it is a reproducible boundary between complete, partial, insufficient, qualified, and unqualified results.
Supervise long-running agent work through immutable revisions, leases, checkpoints, lineage, budgets, and controls.
Current evidence
The graph kernel, mTLS runner protocol, web/iOS supervision, SDKs, and Project Agent vertical slice are source-verified alpha.
Market context
Builder platforms and premium clouds are rapidly expanding orchestration; Lorenz focuses on evidence and operator authority.
Move from planning and cited research to fenced changes, tests, review, approval, and draft-only publication.
Current evidence
Repository reconnaissance, test evidence, writer locks, approval binding, signed commits, and idempotent draft PR effects are implemented in the alpha graph.
Market context
Coding agents often optimize for delivery speed; Lorenz optimizes for a reviewable authority and evidence chain.
Review same-repository pull requests on the independent runner without granting approval, merge, or branch-write authority.
Current evidence
Signed webhook intake, exact base/head binding, secret scanning, changed-line validation, deduplication, and a publication kill switch are implemented; the real DEV canary remains open.
Market context
Coding platforms lead on delivery integrations; Lorenz's narrower claim is review evidence tied to tenant policy, runner identity, and revocable publication authority.
Resolve immutable skill versions with declared data, egress, secret, effect, approval, and sandbox boundaries.
Current evidence
Manifest lifecycle and prompt/document packages are implemented; executable packages require separate qualification.
Market context
Open ecosystems lead in extension breadth. Lorenz deliberately trades installation freedom for provenance and policy.
Keep voice continuous across web/mobile while selecting an approved premium or private runtime under consent.
Current evidence
Streaming voice and account-scoped profiles are available; the packaged MINT multilingual clone still needs exact-hardware qualification.
Market context
Premium assistants set a high UX bar; OpenClaw sets a high channel-breadth bar. Lorenz adds explicit routing and consent boundaries.
Use corporate identity and permission-aware sources without turning email domains into tenant authority.
Current evidence
Microsoft tenant binding, admin consent, strict token verification, and separate mailbox/SharePoint permissions are implemented but activation-gated.
Market context
Microsoft, Google, Glean, and Salesforce lead through native ecosystem depth; Lorenz competes on neutrality and explicit boundaries.
Observe approved network appliances through tenant routes and content-minimal AI results without granting mutation authority.
Current evidence
The read-only broker, route registry, Passbolt references, quotas, policy hashes, and System Doctor states are implemented; live canary remains open.
Market context
This is an operational control-plane extension rather than a generic connector count claim.
Areas where Lorenz is differentiated, plus the adoption and ecosystem advantages held by larger competitors.
A stronger fit for finance, healthcare, public sector, manufacturing, and enterprise operations where data handling cannot be casual.
Different countries can keep different hosting, model, and data-routing policies under one Lorenz architecture.
Lorenz can test and adopt regional open-weight or sovereign-hosted models without changing product behavior.
Every powerful capability stays bounded by policy, visibility, human review when needed, and operator control.
Evaluate Lorenz against your required data boundary, identity model, connected systems, action risk, evidence, and recovery needs.