IOModel Studio

ID	iomodel.studio
Description	The application (web UI and API).
Key	studio
Type	deployment

Table of contents

Studio Guide

Studio Guide

IOModel Studio is the application itself — the Next.js web UI and the API that backs it. It is the component users actually interact with, and the hub that talks to every other service in the stack.

Role in the stack

Studio reads and writes to PostgreSQL, caches in Redis, authenticates users via Keycloak, and mints short-lived WebSocket tokens for the Yjs Realtime Server.

Why it’s needed

Product surface — serves the web UI and the REST/RPC API.

Setting	Purpose
`DATABASE_URL`	PostgreSQL connection string
`REDIS_URL`	Cache / coordination endpoint
`AUTH_KEYCLOAK_ISSUER`	OIDC issuer for sign-in
`AUTH_URL`	Public origin of the deployment
`COLLAB_JWT_SECRET`	Signs realtime WS tokens for the Yjs server

A horizontally scalable Deployment behind a Service, with a one-shot migration Job:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: studio
  namespace: iomodel
spec:
  replicas: 2
  selector: { matchLabels: { app: studio } }
  template:
    metadata: { labels: { app: studio } }
    spec:
      containers:
        - name: studio
          image: iomodel/studio:latest
          ports: [{ containerPort: 3200 }]
          envFrom: [{ secretRef: { name: studio-env } }]
          readinessProbe:
            httpGet: { path: /api/health, port: 3200 }

apiVersion: apps/v1
kind: Deployment
metadata:
  name: studio
  namespace: iomodel
spec:
  replicas: 2
  selector: { matchLabels: { app: studio } }
  template:
    metadata: { labels: { app: studio } }
    spec:
      containers:
        - name: studio
          image: iomodel/studio:latest
          ports: [{ containerPort: 3200 }]
          envFrom: [{ secretRef: { name: studio-env } }]
          readinessProbe:
            httpGet: { path: /api/health, port: 3200 }

Run migrations first

Apply the migration Job (or an init container) so the schema is ready before pods serve traffic.

Roll out Studio

Apply the Deployment and Service; scale replicas to match load.

Expose via Ingress

Route external / traffic to the studio service (see the Reverse Proxy guide).

Links and Communications

1 incoming link · 4 outgoing links · 2 workflows

Incoming Links(1)

Source object	Label	Link type	Relation	Raw id	Required	Description
Reverse Proxy deployment.iomodel.reverse_proxy ingress_controller	routes HTTPS to	—	links	iomodel.studio	—	—

Outgoing Links(4)

Target object	Label	Link type	Relation	Raw id	Required	Description
PostgreSQL deployment.iomodel.postgres statefulset	reads / writes	—	links	iomodel.postgres	—	—
Redis deployment.iomodel.redis statefulset	caches in	—	links	iomodel.redis	—	—
Keycloak deployment.iomodel.keycloak deployment	authenticates via	—	links	iomodel.keycloak	—	—
Yjs Realtime Server deployment.iomodel.yjs_server deployment	mints WS tokens for	—	links	iomodel.yjs_server	—	—

Related Workflows(2)

Workflow	Model	Participant id	Participant label
Release upgrade release-upgrade	deployment	iomodel.studio	IOModel Studio
User sign-in sign-in	deployment	iomodel.studio	IOModel Studio