Inco company primary sources — 2026-08-11

Scope

Focused source capture for the company/entity layer around Inco: legal operator identity, rollout posture, implementation boundary, and the hosted confidentiality-service shell around Inco Lightning.

Primary sources captured

• https://www.inco.org/
  • Homepage markets Inco as full-stack privacy for blockchains, emphasizes compatibility with existing wallets / chains / developer tooling, and frames the stack as a company-packaged privacy layer rather than a new chain.
  • Claims non-custodial posture, verifiable state transitions, and current live support on Base Sepolia / Base Mainnet with Solana Devnet beta.
• https://www.inco.org/about-inco
  • Team page shows Inco as one named operating organization spanning founder, engineering, protocol, operations, business development, design, and smart-contract roles.
• https://www.inco.org/privacy
  • Privacy policy identifies the operating entity as Liquidbox Corp. d/b/a Inco.
  • Says the websites and services are designed for enterprise customers and their representatives.
  • Notes the company is headquartered in the United States.
• https://docs.inco.org/introduction.md
  • Intro says Inco Lightning is live on Base Mainnet and Base Sepolia, with Solana Devnet support available in beta.
  • Frames Inco as a confidentiality layer for existing blockchains.
• https://docs.inco.org/architecture/overview.md
  • Architecture overview lists three main components: smart-contract library, confidential compute server, and client-side JavaScript library.
  • Strong evidence that a named implementation/operator boundary matters alongside the protocol description.
• https://github.com/Inco-fhevm
  • Public GitHub org concentrates demos, templates, forks, and implementation-adjacent repos under one organization, reinforcing that the easiest adoption path still runs through company-maintained code and docs.

Why this source packet matters

The project note already explains the confidentiality middleware. This packet exists to justify the separate entity note: the docs and legal pages make clear there is a named company, a hosted confidential-compute server path, an enterprise-facing service shell, and an explicit rollout boundary deciding what environments are live versus beta.