System architecture - Layered design of the ATK platform

ATK's lifecycle management capabilities

Atomic DvP Settlement: The XvP settlement system coordinates multi-party token exchanges where all legs execute together or the entire settlement reverts. True T+0 finality without counterparty risk or trusted intermediaries.

Vault-Based Custody: Multi-signature treasury management with maker-checker workflows, configurable quorum requirements, and role-based access control. No single point of failure. Emergency controls and full audit trails.

Scheduled Yield Management: Fixed yield schedules eliminate manual calculation of dividends, interest, and coupon entitlements. Configure once; calculate entitlements automatically on payment dates for on-demand claiming with cryptographic proof of entitlement.

Integrated Observability Stack: Production-ready monitoring with VictoriaMetrics, Loki, Tempo, and Grafana pre-configured with comprehensive dashboards. No vendor integration required—metrics, logs, traces, and alerting included from day one.

This architecture eliminates the reconciliation nightmares, custody-compliance disconnects, and T+2 settlement delays that prevent institutional adoption. By embedding regulatory compliance directly into the asset path through ERC-3643, integrating lifecycle management through addon contracts, including production-grade observability, and unifying all operations through a monorepo-based stack, ATK delivers the deterministic state transitions and audit-ready trails that enterprise teams demand.

Layered architecture

ATK follows a layered, modular architecture that separates concerns while maintaining tight integration between components:

The architecture demonstrates clear separation of concerns with well-defined interfaces between layers:

• Frontend Layer provides user interfaces for different stakeholder types (issuers, investors, compliance officers, administrators)
• API Layer handles request processing, authentication, and type-safe data validation
• Business Logic Layer implements core tokenization functionality with embedded compliance
• Data Layer provides persistence, caching, file storage, and blockchain indexing
• Blockchain Layer delivers the foundational smart contract infrastructure with compliance built-in
• Infrastructure Layer enables deployment across public chains, consortium networks, and private EVM builds

Monorepo structure

ATK is organized as a Turborepo monorepo, enabling efficient dependency management, build optimization, and development workflows:

This structure hard-codes integration discipline the market has been missing. Contracts, the TanStack Start dApp, the ORPC API module, TheGraph indexer, end-to-end tests, and Helm charts live in one workspace. Shared packages eliminate ambiguity about interfaces, so lifecycle flows never drift between teams. Environments deploy from one Helm-defined topology, meaning policy, infrastructure, and product evolve together.

Technology stack

ATK leverages modern, enterprise-grade technologies optimized for performance, security, and developer experience:

Core asset types

ATK supports five primary asset classes, each optimized for specific financial instruments:

Why this architecture beats point tools

Traditional tokenization approaches suffer from fatal fragmentation:

• Issuance wizards without registry truth or embedded compliance create rework and legal risk
• Compliance databases in middleware disconnect from the asset path, enabling non-compliant transfers
• Custody vaults cannot see rule updates, breaking synchronization
• Settlement workarounds keep cash and tokens on separate systems, forcing T+2 delays

ATK's unified control plane eliminates these problems:

• Templated legality: Jurisdiction-specific templates (Reg D, Reg S, MiCA) baked into smart contracts from deployment
• Registry truth: Real-time ownership registry synchronized through TheGraph indexers
• Programmable lifecycle: All operations exposed through APIs enable white-label integration
• Embedded compliance: ERC-3643 enforcement in the state-transition path, not as a sidecar
• Single control plane: Every capability (issuance, onboarding, transfers, settlement, reporting) resides on the DALP

Consider a bond, feeder fund, and deposit note issued simultaneously:

1. Product leads model each instrument in the web console, generating ERC-3643 blueprints
2. Compliance configures country, investor-limit, and lock-up modules once—policies apply everywhere
3. Identity teams onboard investors through shared REST APIs—claims synchronize across offerings
4. Custody operations pre-stage HSM-backed wallet tiers directly in DALP custody services
5. Settlement wires cash legs via payment gateway adapters, keeping cash and tokens in lockstep
6. Corporate actions schedule through the servicing workflow engine—investors and auditors see the same data

Because every step references the same control plane, there is no reconciliation step between products. Issuance, compliance, custody, and settlement remain consistent across instruments and venues.

Performance targets

Performance varies by deployment configuration and blockchain network characteristics. These design targets guide capacity planning:

Security & compliance first

Security and compliance are architectural concerns, not bolt-ons:

• ERC-3643 Integration: Security token standard with transfer restrictions built into contract logic
• OnchainID Protocol: Decentralized identity with KYC/AML claim verification
• Role-Based Access: OpenZeppelin AccessManager for granular permissions
• Upgradeable Proxies: Safe contract evolution without data migration
• Audit Trails: Immutable event logs for regulatory reporting
• Multi-Signature Controls: Bank-grade custody with approval workflows

Integration points

ATK integrates with external systems while maintaining control:

• Identity Systems: OnchainID and third-party KYC providers plug into the identity registry
• Banking Rails: Core banking and payment systems connect through mediation services (ISO 20022, SWIFT)
• Custody Providers: Custodian APIs surface into the same business services that govern transfers
• Storage Networks: IPFS and MinIO for document persistence and metadata
• Monitoring: OpenTelemetry integration for observability and SIEM integration

What stakeholders get

• Institutions: One SLA and risk profile. Lifecycle policy changes propagate everywhere because the control plane owns them end-to-end.
• Compliance Teams: Deterministic, pre-transfer checks and auditor-ready logs rather than reconciling middleware exports.
• Operations Teams: Monitor one set of metrics and alerts, rehearse failovers, manage capacity using the same pipelines that drive production.
• Developers: Ship features instead of glue. The API surface, smart contracts, and UI stay aligned through shared types and tests.