Open-source silicon · MIT licensed

The AI accelerator anyone can study, fabricate, and extend.

T1C — short for Tier 1 Chip — is an open-source AI accelerator architecture built under ADDX Entp. The architecture, instruction-set specification, fabrication planning and contribution paths all sit in a public repository. It is a design and research project, not a shipped product — and that is exactly why it is being shared now.

drag to orbit · pinch to zoom
Scroll
MIT Licensed 130nm shuttle ready 9 ISA operations 4 isolated tenants Designed in India

We design it. World builds it.

Architecture

Four ideas, working together.

T1C asks one question: can an AI accelerator be designed openly enough that other engineers can study it and extend it, instead of treating the chip as a sealed black box?

01 — Digital in-memory computing

Compute where the data already lives.

For most AI workloads, raw arithmetic is only part of the cost. Moving weights, activations and KV-cache data between memory and compute can dominate the practical design far more than the multiply-accumulate operations themselves — the classic Von Neumann bottleneck, which gets worse as models grow.

T1C's answer is digital in-memory computing (D-IMC): pushing more of the computation physically closer to where the data already sits, so less of it has to move at all.

D-IMC concepts
Open questions, left visible
  • MappingUnderspecified
  • Numerical precisionUnder review
  • CalibrationOpen
  • SRAM organisationDraft
  • VerificationNot started
02 — Memory-isolated multi-tenancy

Four tenants. One die. No shared risk.

MIM partitions a single chip so that up to four isolated tenants can run separate workloads on the same piece of silicon without stepping on each other. For shared AI infrastructure, that could make capacity far more predictable and affordable.

Isolation is a much bigger problem than dividing memory into regions. It requires explicit resource accounting, quality-of-service assumptions, scheduling behaviour, error handling, and analysis of possible side channels. T1C presents MIM as an architectural direction worth stress-testing — not a finished security guarantee.

Multi-tenancy model
What isolation actually requires
  • Max tenants4 per chip
  • Resource accountingRequired
  • QoS assumptionsTo be defined
  • SchedulingTo be defined
  • Side-channel analysisNot started
Why T1C

Not faster. Open.

T1C is explicitly not positioned as a faster chip than an H100. Its case rests on a different set of trade-offs entirely — openness, cost, and buildability.

01

Open instruction set

Nine architectural operations — matrix multiply, accumulation, KV-cache read/write, DMA, softmax, RMS norm, partition config. Register classes and encoding are published, not hidden.

02

Real fabrication paths

Not "coming soon". Free research shuttles through IHP Germany at 130nm, plus GlobalFoundries, Efabless and Tiny Tapeout routes that are available today.

03

Honest numbers

Published figures are architectural projections, clearly labelled as such. No fabricated ranking claims, no artificial traffic, no borrowed benchmarks.

04

MIT licensed

Free to use, modify, fabricate and sell. Attribution is appreciated but not legally required. The whole project — docs, ISA, planning — lives in one public repository.

9
Architectural ISA operations
MATMUL · ACC · KV · DMA · SOFTMAX · RMSNORM · PARTITION
4
Isolated tenants per chip
MIM — MEMORY-ISOLATED MULTI-TENANCY
$465
Estimated blade cost, midpoint
$280–$650 RANGE
16
Projected tok/s on one blade
LLaMA 7B · 12–20 TOK/S PROJECTED
Honest numbers

Projections, not benchmarks.

T1C has not been fabricated. Every figure below is an architectural projection from the repository — stated plainly, because a number you cannot verify is not a number worth shipping.

SystemLLaMA 7B speedMax modelCostOpen source
T1C — 1 blade12–20 tok/s~64B (INT4)$280–$650MIT
T1C — 8 blades96–160 tok/s~512B (INT4)$2,240–$5,200MIT
NVIDIA RTX 409080–100 tok/s~24B (FP16)$1,500No
NVIDIA H1001000+ tok/sUnlimited$30,000No

T1C is not faster than an H100 and does not claim to be. The pitch is openness, DIY buildability, hardware tenant isolation at a low price point, and an Indian-designed alternative to a market dominated by closed, expensive silicon.

The problem todayT1C's approach
An NVIDIA H100 costs around $30,000A T1C blade is estimated at $280–$650
Closed source — you cannot modify itFully open source, MIT licensed
Needs a specialised cleanroomFabricatable through community shuttle runs
Von Neumann bottleneckD-IMC — compute happens inside memory
No affordable hardware multi-tenancyMIM — four isolated tenants per chip
From architecture to silicon

Openness only matters if it can be built.

The repository lays out concrete, presently-available fabrication paths rather than a vague "coming soon". The recommended starting point is IHP Germany — a free research shuttle route for open-source projects, which removes the single biggest cost barrier to a first physical test chip.

MethodNodeCostAvailability
IHP Germany (research)130nmFreeAvailable now
GlobalFoundries 65LP MPW65nm$15–40 / chipAvailable now
Efabless + SkyWater130nm$100–300 / slotAvailable now
Tiny Tapeout130nm~$100 / slotAvailable now
See full silicon economics
Where the project actually stands

Not taped out. Not pretending otherwise.

T1C has not been taped out, fabricated, or brought to silicon. There are no measured silicon results, no validated production-cost figures, and no finished commercial benchmarks to point to yet.

  • ✓System architecture documentationDone
  • ✓Instruction-set specification (9 operations)Done
  • ✓Fabrication planning & shuttle routesDone
  • ◐Reproducible software modellingIn progress
  • ○Verilog RTL — MAC array, KV-cache, DMA, MMUUnclaimed
  • ○KiCad blade PCB designUnclaimed
  • ○RTL validation & Verilator simulationUnclaimed
  • ○Tape-out, silicon testing, hardware benchmarkingFuture
Contribute

Specific gaps, not a generic "help wanted".

Contribution paths are split by discipline, with named unclaimed items. Full details live in the repository's CONTRIBUTING.md.

Hardware engineers

RTL and board design

Verilog modules for the MAC array, KV-cache controller, DMA engine, MIM MMU and voltage monitor — plus the KiCad blade PCB layout.

Software engineers

Runtimes and tooling

A llama.cpp backend, a Verilator simulation model, a Python assembler, a Linux kernel driver, and an ONNX Runtime provider.

Anyone

Docs, testing, critique

Documentation improvements, translations, blog posts and tutorials, testing and bug reports — and honest critique of the weakest assumptions.

Real engineering. Honest numbers.
An open future.

From India — for the world. The architecture documents and ISA specification go well beyond what is summarised here, and the repository is where the real discussion happens.