Skip to content

Services & Ownership

The ARKONIX stack is composed of five inter-connected services. This page is the canonical map of what each one does, who operates it, and where its documentation lives.

Service What it is Operated by Docs
arkonix-platform Frontend monorepo: Earn app, partner portal, marketing site Arkonix Finance Platform
arkonix-backend Execution platform: public API, app API, indexing, epoch settlement, strategy execution Arkonix Finance Backend
SignalForge Signal & index generation feeding quantitative strategies Arkonix Capital Management (ACM) SignalForge
arkonix-vault-sdk Consumer-facing React/React Native SDK for partners Arkonix Finance (npm, BUSL-1.1) Vault SDK
arkonix-defi-sdk Internal DeFi protocol SDK used by the execution engine Arkonix Finance (internal) DeFi SDK

Ownership boundaries that matter

SignalForge is an ACM product

SignalForge is owned and operated by Arkonix Capital Management, not by the platform entity. The platform consumes SignalForge outputs (signals/indices) as strategy inputs; strategy execution remains a platform concern. This separation matters for due diligence: the entity producing investment signals is distinct from the entity operating settlement and custody-adjacent infrastructure.

Two SDKs, two audiences

The Vault SDK is the only SDK intended for external use — it is published to npm and documented fully on this site. The DeFi SDK is an internal building block of the execution engine; it is documented here at the architectural level only.

How they connect

  • The platform (frontend) talks to the backend over REST with JWT bearer tokens, and to vault contracts directly through wallets and the Vault SDK.
  • The backend indexes on-chain activity, serves the public API the Vault SDK's financial-data layer consumes, and executes strategies using the DeFi SDK against supported protocols.
  • SignalForge publishes signals and index compositions that subscribed strategies consume at rebalance time.