IDS platform

Services on the ids3 cluster at Maastricht University's Institute of Data Science, and how to use them.

Humans: read on. Agents: fetch /llms.txt — the same content, indexed for you, and every page here is also available as raw Markdown by appending .md.


The five things everyone uses

serviceURLsign in withwhat it is for
Coderhttps://coder.k8s.semanticscience.orgKeycloakyour workspace — a VM with a durable home directory, optionally with a GPU
Portalhttps://portal.k8s.semanticscience.orgKeycloakbook GPU time, see your quota, get S3 keys for your data buckets
LiteLLMhttps://litellm.k8s.semanticscience.organ sk- keyone OpenAI-compatible endpoint for every model — local and hosted
Datahttps://data.k8s.semanticscience.orgS3 keys from the portalper-user object storage
Keycloakhttps://keycloak.k8s.semanticscience.orgidentity. You do not visit it; everything else redirects here

One identity for the interactive services: your Keycloak account (realm ids3) signs you into Coder, the portal and SigNoz. LiteLLM is the exception — its API takes an sk- key, and its dashboard uses a separate Keycloak realm (litellm, admins) or an email + password from an invite (everyone else). See Models.

Start here

Also on the cluster

Restricted to operators, listed so you know they exist:

servicewhat
SigNoz — https://signoz.k8s.semanticscience.orgmetrics, logs, traces. Keycloak login; read-only for most people
Vaultsecrets. Nothing you need to touch; apps read it for you
Longhornthe storage behind every volume
ArgoCDdeploys everything on this page from git
Harborcontainer registry

And research projects with their own sites: ontoexplorer, realm-os, shacl, shexmap, sparqlwatch, sulo-schema-builder. Each has an owner; ask in Slack.

How this page is maintained

This site is a directory of Markdown in the MaastrichtU-IDS/services repository, deployed by the same pipeline as everything it describes. If it is wrong, it is wrong in git — open a pull request or say so in Slack.