Accounts and project access
Account and project access
Section titled “Account and project access”After onboarding, you receive access to two connected services. Spike-1 is the compute platform where your workloads run; you submit and manage that work through Run:ai. Harbor is the container registry that stores the versioned images used by those workloads.
Sign in at spike.run.ai because Run:ai is the SaaS
control plane connected to the TU/e cluster. spike.tue.nl hosts this
documentation; it is not the cluster login. Your project connects Run:ai and
Harbor and determines which compute resources, data sources, environments, and
container images you can use.
Check your access
Section titled “Check your access”- Open spike.run.ai and sign in with your TU/e account.
- Select the project created during onboarding and confirm that you can open its workloads, environments, data sources, and compute resources.
- Open Harbor and confirm that the matching project and its repositories are visible.
- Keep the project name handy. You will use the same name when tagging container images and when asking SCC for help.
- If you are off campus, connect EduVPN before testing command-line access, data transfer, or port forwarding.
Commercial partner teams on Spike A receive access across three coordinated layers:
- TU/e NOP Account (VPN access): Following completion of the User Account Registration Form, you receive a TU/e Non-Payroll account used to authenticate onto the TU/e VPN and access the secure network boundary.
- Commercial Run:AI Project: Your dedicated project space connected to the NVIDIA Blackwell B300 GPU pool and VAST Data parallel storage mounts (
/dataor/vast). - Private Harbor Repository: An isolated registry project at
harbor.spike.tue.nl/<company-project>for storing proprietary Podman container images.
Sign in at spike.run.ai using your authorized partner credentials. Your project defines your contracted GPU quotas (NVIDIA Blackwell B300), VAST Data volume mounts, and container registry boundaries.
Check your access
Section titled “Check your access”- Connect to TU/e VPN: Use your issued NOP account credentials to establish a secure VPN connection.
- Verify Run:AI access: Open spike.run.ai, sign in, and confirm that your commercial project is listed with its Blackwell B300 compute templates and VAST Data storage sources.
- Verify Harbor access: Open Harbor and confirm that your company’s isolated repository project is accessible.
- Tag container images: Use your company project identifier for container image tagging (
harbor.spike.tue.nl/<company-project>/<image>:<tag>). - Contact your AI engineer: If project quotas, storage mounts, or registry permissions are not visible, notify your assigned Supercomputing Brabant (SCB) Engineer.
When something is missing
Section titled “When something is missing”| What you see | Check first | What to do next |
|---|---|---|
| Run:ai rejects the sign-in | Confirm that you used the TU/e account included in the intake | Ask your assigned engineer (SCC for Spike 1 / SCB for Spike A) to check whether onboarding and account activation are complete. |
| The Run:ai project is missing | Check the project selector and the exact account you used | Send the project name and your TU/e username to your SCC or SCB contact so they can check membership and role. |
| The Harbor project is missing | Compare its name with the Run:ai project | Ask your SCC or SCB contact to check your membership of the matching Harbor project. |
| The web portals work, but terminal or data traffic fails | Check whether EduVPN or TU/e VPN is connected | Reconnect VPN and retry the same command before changing credentials or configuration. |
When reporting an access problem, include the project name, the service that failed, and the approximate time. Never send browser sessions, registry passwords, access tokens, or private keys.