---
title: Onchain entity-formation competitors vs Entity.ID
date: 2026-08-01
expires: 2026-11-01
tags: [entityid, competitors, fundraising, research]
---

# Onchain Entity-Formation Competitors vs Entity.ID (2026-08-01)

**One-line summary:** the verified field splits into three archetypes - OtoCo (pure onchain formation), MetaLeX (law-plus-code structuring + the most advanced onchain fundraising stack), MIDAO (jurisdiction monopoly) - and **no competitor combines formation + fundraising in one flow. Entity.ID already spans both; the recommended move is to harden the fundraising module along the cyberRaise pattern.**

Method: deep-research workflow, 104 agents, 22 sources fetched, 110 claims extracted, 25 claims through 3-vote adversarial verification (24 confirmed, 1 refuted). All findings below carry source links. Entity.ID's own capabilities sourced from [[BRANDBOOK-v1]], `team-paper.md`, `dashboard-ui.md`.

## 1. The competitive field

### OtoCo (Otonomos) - pure onchain formation
- **Formation:** one Ethereum transaction to the `otoco.eth` Master contract spins up a real Delaware **Series LLC** (series of OtoCo's pre-formed Master Series LLC, 6 Del. C. §18-215 - that's how "instant" is legal). The smart contract holds the Operating Agreement; the connecting wallet legally becomes the first Member. Vendor claims ~5s confirmation. *(3-0 verified; [launch post](https://otonomos.medium.com/otoco-is-live-you-can-now-instantly-form-a-real-world-llc-using-your-ethereum-wallet-f31e1b99fa8), [FAQ](https://otoco.gitbook.io/otoco/c.-faqs/faqs-1/faqs))*
- **Cap table / governance:** multi-member LLCs use "mirror tokens" - ownership stakes mirrored as tokens, functioning as a live cap table. Members vote on Reserved Matters (transfers, dissolution, acquisition); routine powers delegated to a Manager. *(mirror tokens 3-0; "vote on all matters" only 2-1 - vendor phrasing, single affiliated source; [newsletter](https://newsletter.otonomos.com/p/upfit-your-llc-otoco-now-lets-you))*
- **Everything else is bolt-on:** fundraising/tokenization/governance were scoped as third-party plugin "kits" (OtoGO launchpool, Sept 2021). Its LLCs are positioned as SAFE/SAFT/SAFTE/TPA *issuer vehicles*, not a fundraising product. Banking via EIN add-on ($189, Mercury) - some banks refuse series-level entities. *(3-0)*
- ⚠️ Refuted 0-3: the circulating "~$25 average total cost incl. gas" figure. Do not cite.

### MetaLeX (+ Aragon) - law-plus-code structuring, best-in-class fundraising
- **BORGs:** traditional entities (corp/LLC/foundation) whose **charters legally embed smart contracts and AI** to run operations/governance. Two families: cyberCORPs/bizBORGs (independent businesses) and DAO-adjacent BORGs (security/grants/IP committees). Live deployments: Lido Alliance BORG (Sept 2024). $2.75M raise (CoinDesk, 2024-05-24). *(3-0; [docs](https://metalex-docs.vercel.app/borg/what-is-a-BORG))*
- **Treasury enforcement (closest analogue to our compliance positioning):** `borg-core` installs as a **Gnosis Safe Guard** that blocks all multisig actions except those whitelisted by the BORG's policy, down to parameter level; the URI of the legal docs is stored onchain, binding onchain authority to legal scope; the DAO can hold legal veto/revocation powers. Enforceability is designed-in, **not court-tested**. *(3-0 x4; [borg-core](https://github.com/MetaLex-Tech/borg-core))*
- **No-code via Aragon (live Sept 2025):** liability wrappers attach to specific wallets/roles rather than the whole DAO; multiple modular BORGs side-by-side (treasury, core team, grants, foundation). MetaLeX does legal design + docs + signer address; deployment happens in Aragon's UI. *(3-0; [Aragon blog](https://blog.aragon.org/borgs-are-live-legal-modularity-for-onchain-organizations/))*
- **cyberRaise (Apr 2025) - the fundraising deep-dive:** convertible deal logic as an automated onchain process:
  - Founder sets terms; both parties sign with wallets; funds + certificate token escrow in a **Deal Manager** contract; close/refund executes atomically ("blockchain as the neutral escrow agent").
  - **Four instruments: SAFE, SAFT, SAFE + Token Warrant, SAFTE - each in U.S. Reg D and offshore Reg S versions.**
  - Investor rights = **non-transferable-by-default Certificate Token NFTs**; optional **LeXcheX** soulbound-NFT accredited-investor verification; no mandatory platform KYC or account creation.
  - **Critically: cyberRaise does NOT form entities** - onchain formation was roadmap-only as of Apr 2025 (v2 post's DGCL §224 constitutive-tokenization language hints it may be advancing). *(3-0 x4; [cyberSAFE post](https://metalex.substack.com/p/metalexs-cybersafe-fund-your-company))*

### MIDAO - jurisdiction monopoly
- Marshall Islands DAO LLCs (for-profit / non-profit / Series) for Web3 projects, DAOs, **and AI agents** - no DAO required. $9,500 + $2,000-5,000/yr (optional $10k TurboDAO 24h onboarding); for-profits pay 3% RMI gross-revenue tax. Moat is **legal, not software**: exclusive public-private partnership makes MIDAO the sole registered agent for RMI DAO LLCs (2022 DAO Act), independently corroborated. *(3-0; [midao.org](https://www.midao.org/), fetched 2026-08-01)*
- ⚠️ Direct overlap with our thesis: MIDAO explicitly markets **AI-agent incorporation**.

## 2. Function matrix vs Entity.ID

| Function | Entity.ID (shipped/planned) | OtoCo | MetaLeX (+Aragon) | MIDAO |
|---|---|---|---|---|
| Formation | 7-step proto-entity wizard, free, KYC'd members, public name (`*.venture.public.entity.id`); incorporation as an upgrade | Delaware Series LLC in 1 tx, wallet = first Member | None (roadmap); wraps existing entities | RMI DAO LLC, $9.5k, human-service |
| Treasury | Safe SDK multisig, threshold approvals, multi-lane view (USDC/USD/ETH/T-bill) | None native; EIN + Mercury add-on | Safe Guard policy enforcement, parameter-level whitelists, legal-doc URI onchain | None |
| Banking | Planned bank-account lane; beneficial-ownership package for banks | $189 EIN add-on; banks may refuse series entities | Via wrapped entity | Via formed entity |
| Fundraising | Post-money SAFEs in-product, settle to treasury, cap table auto-updates | Positioned as issuer vehicle only; plugins | **cyberRaise: 4 instruments x Reg D/Reg S, Deal Manager escrow, cert NFTs, LeXcheX** | None |
| Governance | Proposals/votes/amendments on the record; vesting as deterministic logic | Mirror-token voting on Reserved Matters | Charter-embedded smart-contract governance, DAO veto | Statutory DAO LLC governance |
| Compliance | KYC (Sumsub), KYA, compliance-by-registration, EU AI Act disclosures | Minimal | Legal-doc-to-code binding | RMI statute |
| AI agents | KYA + Natural Attribution (agent → venture → verified person) | No | AI in charters (governance tooling) | **Markets AI-agent incorporation** |

**The verified gap we own:** OtoCo forms but doesn't raise; MetaLeX raises but doesn't form; MIDAO forms offshore with no software. Nobody ships **form + raise in one flow bound to a public registry record** - we already do both halves.

## 3. Implementation recommendation - Entity.ID fundraising module

(Analyst synthesis on 3-0-verified underlying claims; confidence medium by design.)

Adopt the cyberRaise architecture natively on top of the formation flow we already own:

1. **Deal Manager escrow contract** - holds investor funds + an issuer-minted certificate token; atomic close/refund; the contract, not a platform, is the escrow agent. Fits our Safe-SDK treasury: closed funds settle straight into the venture's multi-lane treasury.
2. **Instrument templates** - extend beyond our current post-money SAFE to the four-instrument set: SAFE, SAFT, SAFE + Token Warrant, SAFTE, each parameterized as **Reg D (506(b)/506(c)) and Reg S** variants. Terms are wizard parameters, same UX grammar as the formation wizard.
3. **Certificate NFTs as the rights record** - non-transferable by default; double as the live cap table (OtoCo's mirror-token lesson), auto-updating the record we already maintain.
4. **Soulbound accreditation attestations** (LeXcheX pattern) - Reg D raises verify accredited status via attestation, no platform-wide KYC burden on investors; slots into our existing Secondary/Attestations registrar model.
5. **The differentiator: bind the raise to the registry record.** Because proto-entities are Entity.ID-native, the raise contract references the entity's Universal Identifier directly - investors verify members, ownership, governance history before wiring. The one-flow "form + raise" neither OtoCo nor MetaLeX ships today.

Register note: all of the above is investor-deck vocabulary. Site copy stays in the locked non-crypto register ("raise from your dashboard - funds settle to your treasury, your record updates itself").

## 4. Caveats and open questions

- Nearly all evidence is **vendor-authored**; fine for capability claims, but **no adoption/revenue/traction data survived verification for any competitor**.
- Legal enforceability of BORG charters and wallet-signed membership is designed-in, **not court-tested** anywhere in the record.
- **Coverage gaps** (named in scope, no surviving claims): doola, Stripe Atlas, Clerky, Wyoming DAO LLC/DUNA providers, Otonomos-proper. Needs a follow-up sweep.
- Open: has MetaLeX shipped onchain formation since Apr 2025 (v2 DGCL §224 language)? Actual volumes per competitor? Any court/SEC test of onchain SAFEs?

---
*Compiled by HusAgent 2026-08-01 via deep-research workflow (104 agents, 3-vote adversarial verification). Entity.ID capability baseline from vault sources.*