OSC URL Patterns

All resources in Eyevinn Open Source Cloud follow specific URL patterns depending on the resource type and environment.

Service Instance URLs

Service instances are accessed via URLs that include your tenant ID:

{tenantId}-{instanceName}.{serviceId}.auto.{env}.osaas.io

Example: myteam-redis1.valkey-io-valkey.auto.prod.osaas.io

The tenant ID is your account identifier. The instance name is what you chose when creating the instance. The service ID identifies which service it is.

My Apps URLs

Apps deployed via My Apps use the web-runner service:

{tenantId}-{appName}.eyevinn-web-runner.auto.{env}.osaas.io

Example: myteam-mywebapp.eyevinn-web-runner.auto.prod.osaas.io

You can also configure a custom domain for your app.

TCP Service Endpoints

Services that expose raw TCP ports (databases such as PostgreSQL, Valkey, MariaDB, and ClickHouse) can be made reachable outside the cluster using set-instance-public-access. When public access is enabled, the service gets a NodePort allocation and is reachable at:

{serviceId}.{tcpDomain}:{port}

Example: eyevinn-postgresql.tcp.prod.osaas.io:31742

The serviceId component is the stable service identifier (e.g. eyevinn-postgresql), not the per-tenant instance name. This means the hostname is consistent across all tenants running the same service.

Note: set-instance-public-access controls TCP-level (NodePort) exposure only. Services with an HTTP web UI (Keycloak, catalog UIs, identity providers) are routed through a shared ingress with the OSC SSO auth gate — HTTP access and the auth gate cannot be toggled per-instance with this tool.

Use get-instance-status to see the allocated TCP endpoint after enabling public access.

Platform Service URLs

Internal platform services (not user-facing) use:

{service}.svc.{env}.osaas.io

Environments

Environment	Domain suffix
Development	.dev.osaas.io
Staging	.stage.osaas.io
Production (Linode)	.prod.osaas.io
Production (Elastx)	.prod-se.osaas.io

Finding Your Instance URL

After creating a service instance, the actual URL is returned in the creation response. You can also find it by using the describe-service-instance tool or viewing the instance in the dashboard at https://app.osaas.io.