Singapore concept launch · AI for Good Summit, Shangri-La Singapore · 5–7 Nov 2026Meet us →Get in touch
Product Roadmap

Gen1 validates.
Gen2 produces.

A two-generation path from FPGA proof-of-concept to production silicon. Gen1 closes the architecture on a 64-chip domain. Gen2 scales to production MoE, long-context, and agentic workloads.

Gen1 to Gen2 structural architecture evolution
Pre-silicon · Sim & validation POC Oct · FPGA build Nov Updated 14 October 2026

Gen1 — Architecture Validation

Goal: prove the core principles of state-resident structural computing on real hardware — before any tape-out commitment. We report what is done, what is in progress, and what is next. Nothing below is a silicon measurement.

Done
  • Gen1 architecture defined: compute array, state domain, and fabric topology
  • Design partners engaged for front-end (Taiwan) and implementation (Canada)
  • FPGA platform selected: AMD Alveo V80 compute nodes, AMD Versal VPK120 fabric node
In progress
  • Architecture specification and cycle-level C-model
  • Multi-node FPGA proof-of-concept: compute and fabric nodes in build
  • Proof-of-concept compiler for compile-time state-path scheduling
  • Singapore concept launch, 5–7 Nov 2026 (architecture exhibit, no live compute)

Gen1 closes the architecture. Gen2 moves to production silicon.

Download public technical overview (PDF) Detailed per-generation parameters and dated milestones are available under NDA.

Checking access...

SIF-Link: keep the PHY, delete the rest

SIF-Link keeps the physical layer (SerDes, alignment, CRC) and reuses mature commercial IP. Everything whose job is to manage unpredictable traffic — routing, flow control, QoS, CXL transactions — is deleted and replaced by compile-time configuration.

KEPT
+ PHY / PCS (SerDes)
+ Link-layer CRC
+ Fixed-length flit
DELETED
— Address/ID routing
— Credit flow control
— QoS / TC / VC
— CXL transactions
— Hot-plug enum
SIF-Link protocol simplification

Determinism by design

SIF traffic has no unpredictability by construction: single-source per slot, fixed fanout, compiler-scheduled. No mechanism is needed to manage what doesn't exist. Latency equals pure pipe depth — no queueing term.

Want the full technical detail?

Request NDA access Public overview (PDF)
Partner Portal