Skip to main content
Naïve is open-core. The line is “are we the regulated counterparty of record,” not “do we host it.”

First-party (closed, on our API)

The regulated primitives — identity/entity, money, comms, runtime, and the tool catalog. We’re the issuer / KYB-and-formation entity / carrier registrant. Forking the code doesn’t let you issue a card or form an LLC, because the moat is the operated regulated bundle and the per-tenant governance, not the SDK shape.

Open (OSS on GitHub)

Cloud infrastructure (the Naive-managed cloud provisioner, with managed hosting as the upsell), database, tracing, and custom modules. Anyone could run these; we host for convenience. They compete with InsForge / Supabase / Stripe Projects, so they are complements and distribution, never the headline.

The litmus test

If we open-sourced this module, could someone run it without us?
  • Yes → open module.
  • No, because we’re the regulated counterparty → first-party.

What this means in practice

CapabilityTierWhy
Identity / entity (KYB / EIN / formation)First-partyWe’re the formation + KYB counterparty
Money (card issuing, interchange)First-partyWe’re the issuer of record
Comms (numbers, A2P/10DLC, email reputation)First-partyWe’re the carrier registrant
Runtime (hosted microVMs)First-party (wrapped)Operated; provider kept swappable
Cloud (apps/db/compute/queue)Open moduleCommodity; bring your own
Tracing / observabilityNative + exportableRequired to govern; exports to Langfuse/Datadog/OTel
Custom modulesOpenAuthored by you
The SDK, CLI, templates, and skill onboarding are distribution, not defensibility — the moat is the operated regulated bundle and the per-tenant governance gateway.