SN1
Apex
Competitive problem-solving and research orchestration.
Why these tags?
Reviewed current owner metadata and available linked primary sources; retained the supported product-focus tags.
Basis: Project repository.
Project source ↗THE BITTENSOR SECTOR MAP
Find your corner
of Bittensor.
Robotics. Inference. Security. See who’s building what—and where the sectors overlap.
128 subnet slots20 sectors11 unclassified
Choose a sector
One subnet. More than one lane.
EXPLORE THE NETWORK
All subnets
Browse every subnet slot, or narrow the map to what interests you.
128 subnets found · showing 24
Chart & subnet details
SN2
DaniLabs
Distributed AI inference; its repository describes an observer pilot with scoring still under development.
Why these tags?
Reviewed current owner metadata and available linked primary sources; retained the supported product-focus tags.
Basis: Project repository.
Project source ↗SN3
Teutonic
Competitive model pretraining with independently evaluated checkpoints.
Why these tags?
Reviewed current owner metadata and available linked primary sources; retained the supported product-focus tags.
Basis: Project repository.
Project source ↗SN4
Targon
Confidential compute infrastructure using trusted execution environments.
Why these tags?
The project README makes confidential computing a core offering, supporting Security & Privacy alongside Compute & Cloud.
Basis: Project repository.
Project source ↗SN5
Hone
Reinforcement learning from verifiable software-engineering and terminal tasks.
Why these tags?
Software patches and terminal tasks are primary evaluated outputs.
Basis: Project repository.
Project source ↗SN6
Numinous
Aggregating AI agents for forecasting.
Why these tags?
Reviewed current owner metadata and available linked primary sources; retained the supported product-focus tags.
Basis: Project repository.
Project source ↗SN7
Allways
A transaction layer connecting applications and execution.
Why these tags?
Reviewed current owner metadata and available linked primary sources; retained the supported product-focus tags.
Basis: Project repository.
Project source ↗SN8
Vanta
Liquidity and trade-execution infrastructure.
Why these tags?
Reviewed current owner metadata and available linked primary sources; retained the supported product-focus tags.
Basis: Project repository.
Project source ↗SN9
iota
Distributed model training.
Why these tags?
Reviewed current owner metadata and available linked primary sources; retained the supported product-focus tags.
Basis: Project repository.
Project source ↗SN10
Pareton
Routing and optimizing AI inference.
Why these tags?
Reviewed current owner metadata and available linked primary sources; retained the supported product-focus tags.
Basis: Project repository.
Project source ↗SN11
TrajectoryRL
Agent-policy competitions, including model-fusion routing for Engy.
Why these tags?
Current Season 2 documentation describes deployable inference fusion policies, not only trajectory training.
Basis: Project repository.
Project source ↗SN12
Compute Horde
Decentralized GPU compute for Bittensor validators.
Why these tags?
The documented product is compute for validators. Internal verification alone does not establish a separate cybersecurity offering.
Basis: Project repository.
Project source ↗SN13
Data Universe
Collecting social-media data.
Why these tags?
Reviewed current owner metadata and available linked primary sources; retained the supported product-focus tags.
Basis: Project repository.
Project source ↗SN14
Cacheon
Optimizing kernels for model-inference speed.
Why these tags?
Reviewed current owner metadata and available linked primary sources; retained the supported product-focus tags.
Basis: Project repository.
Project source ↗SN15
ORO
AI agents for commerce.
Why these tags?
Reviewed current owner metadata and available linked primary sources; retained the supported product-focus tags.
Basis: Project repository.
Project source ↗SN16
Zero Hour
Robot task-disruption and recovery data for VLA training.
Why these tags?
Reviewed current owner metadata and available linked primary sources; retained the supported product-focus tags.
Basis: Project repository.
Project source ↗SN17
404—GEN
Competitive 3D content generation.
Why these tags?
Reviewed current owner metadata and available linked primary sources; retained the supported product-focus tags.
Basis: Project repository.
Project source ↗SN18
Zeus
Weather prediction models.
Why these tags?
Reviewed current owner metadata and available linked primary sources; retained the supported product-focus tags.
Basis: Project repository.
Project source ↗SN19
blockmachine
Decentralized RPC and archive-node services.
Why these tags?
Reviewed current owner metadata and available linked primary sources; retained the supported product-focus tags.
Basis: Project repository.
Project source ↗SN20
Witness
Models for video understanding.
Why these tags?
Reviewed current owner metadata and available linked primary sources; retained the supported product-focus tags.
Basis: Project repository.
Project source ↗SN21
AdTAO
Predicting the impact of advertising interventions.
Why these tags?
Reviewed current owner metadata and available linked primary sources; retained the supported product-focus tags.
Basis: Project repository.
Project source ↗SN22
Desearch
A public-web index and retrieval infrastructure for AI search and research.
Why these tags?
Its README explicitly describes collecting, refreshing and preparing web data as well as search.
Basis: Project repository.
Project source ↗SN23
Trishool
AI alignment research and evaluation.
Why these tags?
Reviewed current owner metadata and available linked primary sources; retained the supported product-focus tags.
Basis: Project repository.
Project source ↗SN24
Quasar
Coordinating decentralized pretraining of Quasar language models.
Why these tags?
The current repository describes coordinated language-model pretraining; inference hosting is not established as its current product.
Basis: Project repository.
Project source ↗How the map works
Tags describe a project’s stated work. A subnet can belong to several sectors, so sector counts overlap. They are editorial classifications—not rankings, proof of adoption or confirmation that every announced product is live.
Reviewed using owner-submitted on-chain metadata at block 9,340,975 and linked project repositories. All 128 slots were reviewed. Unnamed, deprecated, parked, sale and unclear identities remain visible under Unclassified when no product sector can be established. A subnet number can be reused; classifications need review when ownership, identity or purpose changes.
View the dated metadata and source record ↗