Guides by role¶
AIGr.id is shared by many people, each doing a different job. Find your role below. Each guide lists what that role can do, in the order you are likely to do it, and links to the reference pages you need.
flowchart LR
NA["Network admin"] -->|"runs the network<br/>that clusters join"| CA["Cluster admin"]
CA -->|"runs the cluster<br/>that nodes join"| NC["Node contributor"]
BC["Block creator"] -->|"deploys models<br/>onto clusters"| CA
VC["vDAG creator"] -->|"chains blocks<br/>into workflows"| BC
IU["Inference user"] -->|"sends tasks to<br/>blocks and vDAGs"| VC
IU --> BC
| Role | Who they are | Main tasks | Guide |
|---|---|---|---|
| Network admin | Creates and governs a network | Install the management cluster; write and update network-wide governance policies | Network admin guide |
| Cluster admin | Owns a Kubernetes cluster and contributes it to a network | Join the cluster; set cluster rules; monitor stability; host add-ons such as registries and inference servers | Cluster admin guide |
| Node contributor | Owns a single machine with spare capacity | Join the machine to a cluster | Node contributor guide |
| Block creator | AI/ML or software developer | Package models and code as components; deploy them as blocks; choose placement and scaling policies | Block creator guide |
| vDAG creator | Developer building multi-step AI applications | Chain blocks into workflows; add quotas, health checks and quality checks; deploy the controller | vDAG creator guide |
| Inference user | Application developer or end user | Find inference servers and vDAG controllers; send tasks; read results | Inference user guide |
One person, several roles
These are roles, not people. In a small setup, one person may run the network, own the cluster and deploy the blocks.