Skip to content
CN2.DEVBUKYA NARESH

PATH / 04 — BUSINESS & PARTNERSHIPS

TECHNICAL PARTNERSHIPS & PRODUCT OPPORTUNITIES


I'm open to technical partnerships and product opportunities where quantitative systems, market-data infrastructure or research tooling is central. I work independently and take on partnerships selectively.

Partnership models — four forms, one corePARTNERSHIPSELECTIVE · DEFINED SCOPEINFRASTRUCTURERESEARCH PRODUCTDATA LICENSINGOPEN SOURCE

PARTNERSHIP MODELS — FOUR FORMS, ONE CORE.

PARTNERSHIP MODELS

Each model below builds on systems I have already built and can demonstrate — with repositories, case studies and results you can inspect directly.

01

TECHNICAL INFRASTRUCTURE

Co-building market-data pipelines, backtesting engines, or risk systems with shared IP.

Apex Quant EngineQuant Market Data Replay

STAGE: EXPLORATION

02

RESEARCH PRODUCTIZATION

Taking a verified research finding and engineering it into a reusable, documented product.

QRSIPAutomated Trading OS

STAGE: VALIDATION

03

DATA LICENSING

Point-in-time correct market data or derived signals with exact provenance and redistribution rights.

Quant Market Data Replay

STAGE: SCOPING

04

OPEN-SOURCE COLLABORATION

Jointly maintaining critical infrastructure — deterministic simulation, exact decimal arithmetic, replay tooling.

All public repositories

STAGE: ONGOING

PRINCIPLES

WHAT I DON'T TAKE ON

  • No equity-for-work arrangements without a signed agreement and defined scope.
  • No white-labeling of systems — the archive is the proof, the brand stays CN2.DEV.
  • No NDAs that prevent publishing methodology, limitations, or negative results.
  • No partnerships that require misrepresenting backtests as live trading.
  • No 'advisor' roles where the contribution is a name on a slide deck.
  • No revenue-share without auditable, reproducible performance attribution.

NEXT

PROPOSE A PARTNERSHIP