Using Alloy Hub¶
Alloy Hub is the web interface and registry for Alloy blueprints. Use it to discover community blueprints, manage your organization’s blueprints, and get the blueprint names you need for alloy-provisioner install and alloy-host init.
Explore¶
The Explore area lists public blueprints you can use without logging in. Each blueprint has a name (e.g. community/arm-none-eabi, community/raspberry-pi-arm64) and optional tags (e.g. latest, 1.0.0).
- Blueprint name: Use this with the provisioner or alloy-host, e.g.
alloy-provisioner install community/arm-none-eabioralloy-host init my-env --blueprint community/arm-none-eabi. - Tags: Shown on the blueprint detail page. Pin a version in CI or scripts, e.g.
community/arm-none-eabi:1.2.0.
My Hub (organizations)¶
If you have an organization on Alloy Hub, My Hub gives you:
- Repositories: Create and manage private or org-scoped blueprints. Push new versions from your machine using the Alloy CLI and the credentials from Hub.
- Collaborations: Invite members and manage access.
- Settings: Billing, usage, and notifications (depending on your plan).
To use a private or org blueprint, log in so the provisioner can authenticate to the registry. See Installing environments and Blueprint variables for env files and registry credentials.
Finding blueprint names for install or clone¶
- Open alloy-it.io and go to Explore (or My Hub for your org’s blueprints).
- Click a blueprint to open its detail page.
- Use the pull or install command shown there, or build the name yourself:
project/repository(e.g.community/raspberry-pi-arm64). Add:tagfor a specific version.
Examples:
alloy-provisioner install community/arm-none-eabi
alloy-provisioner install community/raspberry-pi-arm64:latest
alloy-host init nrf-dev --blueprint community/nrf91
Next steps¶
- Get started: choose your installation path (native, alloy-host, Docker).
- Installing environments: install the provisioner and run a blueprint.
- Publishing to Alloy Hub: add a community blueprint or publish an org blueprint.