IOModel Studio

IOModel Stack

ID	iomodel
Description	Self-hosted IOModel deployment (default Docker Compose / Kubernetes stack).
Key	iomodel
Type	namespace

Table of contents

Stack Guide

Components at a glance

Why it's structured this way

Deploying the whole stack

Stack Guide

The IOModel Stack is the complete self-hosted deployment of IOModel: a web application, its realtime collaboration backend, an identity provider, a relational database, and a cache — all sitting behind a single TLS-terminating edge.

What this namespace represents

This object is a logical grouping (namespace) for everything that ships in one deployment unit. On Kubernetes it maps to a Namespace; with Docker Swarm it maps to a single stack.

Components at a glance

Component	Role	Workload type
Reverse Proxy	TLS termination, HTTP/WS routing	Ingress / edge
IOModel Studio	Web UI + API	Stateless `Deployment`
Yjs Realtime Server	Live collaboration over WebSocket	Stateless `Deployment`
Keycloak	Identity provider / SSO (optional)	`Deployment`
PostgreSQL	Application database	Stateful (`StatefulSet`)
Redis	Cache & coordination	Stateful (`StatefulSet`)

Group everything under one namespace and deploy components independently:

kubectl create namespace iomodel
kubectl -n iomodel apply -f k8s/

kubectl create namespace iomodel
kubectl -n iomodel apply -f k8s/

apiVersion: v1
kind: Namespace
metadata:
  name: iomodel
  labels:
    app.kubernetes.io/part-of: iomodel-stack

apiVersion: v1
kind: Namespace
metadata:
  name: iomodel
  labels:
    app.kubernetes.io/part-of: iomodel-stack

Stateful components (postgres, redis) use StatefulSets with volumeClaimTemplates; stateless components (studio, yjs_server, keycloak) use Deployments fronted by Services and an Ingress.

Stack Guide

Components at a glance

Stack Guide

Components at a glance

Why it’s structured this way

Deploying the whole stack