Ark Labs company primary sources — 2026-08-09

Project status in this pass

• Existing projects/arkade note was strong on mechanism and product shape but still flattened too much of the named operator and rollout boundary into the project note.
• This pass pulled the company-specific control surface out into ../companies/ark-labs.md.

Primary-source snapshots

1) Ark Labs main site

• URL: https://arklabs.xyz/
• Key excerpt:
  • The homepage presents Ark Labs as Building Open, Programmable Finance and says Our technology powers this transformation on Bitcoin.
  • It frames the company around fintech, brokerage, and asset-manager infrastructure rather than around a single consumer app.
  • It directs readers to the Ark Labs blog and Arkade docs as the main public entrypoints.
• Why it matters:
  • This is evidence that the named entity is selling a broader company-shaped infrastructure story around Arkade rather than acting as a passive repo steward.

2) Arkade product site

• URL: https://arkadeos.com/
• Key excerpt:
  • The site markets Arkade as An operating system for Money and says it brings financial applications directly to Bitcoin with no wrappers, no bridges, no compromises.
  • It exposes build/docs entrypoints and explicitly includes an FAQ item Who is the Arkade Operator?.
• Why it matters:
  • The product surface itself keeps the operator question in view, which is a clue that the company boundary matters analytically.

3) Arkade technical primer

• URL: https://docs.arkadeos.com/primer
• Key excerpt:
  • The docs state that Arkade is built, maintained, and operated by Ark Labs.
  • They say applications connect to the Arkade operator through the SDK.
  • They describe the operator as processing transactions, validating them, and coordinating settlement, while users retain unilateral exit rights.
• Why it matters:
  • This is the cleanest direct source tying the live operator path to a named company while still distinguishing bounded operator power from full custody.

4) Arkade security & trust model

• URL: https://docs.arkadeos.com/learn/core-concepts/security-and-trust-model
• Key excerpt:
  • This page again says Arkade is built, maintained, and operated by Ark Labs.
  • It presents Arkade’s security model as one where users can always exit to Bitcoin L1 independently even though normal operation still routes through the operator fast path.
• Why it matters:
  • It shows the protocol’s trust-minimization framing does not erase the relevance of the named operator boundary; it just tries to constrain it.

5) Baltic Honeybadger 2025 rollout post

• URL: https://blog.arklabs.xyz/closing-the-lightning-loop-bitcoins-missing-layer-secretly-goes-live/
• Key excerpt:
  • Ark Labs says Arkade processed its first mainnet payments at Baltic Honeybadger 2025.
  • It says every Lightning payment at the conference ran through Arkade infrastructure, with merchants receiving VTXOs through the Boltz integration and BTCPay plugin-backed merchant flow.
  • It says private mainnet partnerships are open, and that Lightning operators and professional liquidity providers can begin exploring the Fulmine stack.
• Why it matters:
  • This makes the rollout path legibly company-mediated: production adoption, partner relationships, and operator tooling are bundled together under one entity boundary.

6) ArkLabsHQ GitHub organization

• URL: https://github.com/ArkLabsHQ
• Key excerpt:
  • The organization exposes Arkade-adjacent repositories such as Fulmine, the Arkade BTCPay Server plugin, and other supporting software.
• Why it matters:
  • Downstream users will read this org as the canonical implementation and integration surface, which gives the company real documentation and software-path leverage.

7) Fulmine repository

• URL: https://github.com/ArkLabsHQ/fulmine
• Key excerpt:
  • Fulmine is described as a Bitcoin wallet daemon built on Arkade that can be used as a general-purpose Arkade wallet or as infrastructure for Arkade-native services.
  • The README explicitly discusses running as a delegate for automated VTXO renewal and exposes service configuration for swap and operator-facing workflows.
• Why it matters:
  • This shows Ark Labs is not only publishing protocol docs; it is packaging the day-two service software that shapes how operators and liquidity providers actually participate.

Working conclusion

Arkade is worth splitting into protocol and company layers. The project note should keep the VTXO / execution / settlement machinery visible. The company note should capture the named operator boundary around the official docs and repos, the Arkade service path applications connect to, Fulmine and related operator tooling, merchant rollout, and the partnership-mediated path into broader production use.