Keep collaboration sovereign
Run meetings inside the Vianordis environment with EU-operated infrastructure, controlled identity, and governed room records.
Vianordis--:--:-- UTCVianordis / ED. 02 / 2026
§ 07 — App support
Korum
Sovereign video meetings for teams that cannot lose control.
Korum gives European organizations a controlled meeting layer for internal calls, customer sessions, workshops, and external conference-room interop without routing collaboration through a black-box video SaaS.
01 — Problem
Enterprise meetings are usually fast, but rarely controlled.
Video calls carry customer discussions, legal decisions, support sessions, board meetings, and operational incidents. The tools are often separate from identity, recordings leave the sovereign environment, and external room systems become manual exceptions.
- Meeting access is split from central SSO and tenant policy.
- Recordings and meeting metadata are difficult to govern consistently.
- External SIP, VTC, Jitsi, and H.323 systems require side channels or separate bridges.
- Hosts lack a clean room dashboard for limits, status, participants, and ownership.
- Regulated teams cannot easily prove where collaboration traffic, records, and controls live.
02 — Solution
Korum brings meetings back under the Vianordis control plane.
Korum combines a Next.js meeting workspace, a Go API, Keycloak SSO, PostgreSQL records, and a LiveKit media layer. Users create rooms, join through SSO, meet in the browser, record when allowed, and connect external conferencing systems through a governed SIP bridge.
- Teams create and manage meeting rooms from a dashboard with account limits and room status.
- Participants join through controlled links, media preview, and organization SSO.
- Operators keep identity, tenant policy, recordings, SIP trunks, and media infrastructure under one European operational model.
03 — Benefits
Business outcomes before meeting controls.
Korum is built for organizations that want modern browser meetings without surrendering access policy, recording posture, or interoperability.
Reduce meeting-tool sprawl
Give users one workspace for rooms, join links, recordings, limits, and meeting defaults instead of scattered conferencing accounts.
Support external participants
Use the SIP bridge to connect standards-based endpoints, Jitsi meetings, and H.323 systems when partners cannot join through the browser.
Control recordings
Expose recording controls only when the account and room policy allow it, then keep recording records tied to the meeting room.
Use familiar browser meetings
Participants get video, audio, chat, screen sharing, and media preview without installing a separate desktop client.
Fit tenant operations
Administrators can govern tenants, room limits, participant limits, AI configuration, and SIP trunks through protected API routes.
04 — How it works
From room creation to governed meeting in three steps.
- 01
Provision identity and limits
Keycloak groups and conferencing claims define who can access Korum, create rooms, record meetings, and use tenant-level administration.
- 02
Create and join rooms
Hosts create rooms from the dashboard, share the join link, and participants enter through the browser with media preview and SSO.
- 03
Meet, bridge, and record
The LiveKit room handles video, audio, chat, and screen sharing while Korum controls recordings and optional external-system invites.
05 — Features
What teams can actually do in Korum.
Room dashboard
Create, search, join, and delete rooms while seeing active meeting count, room limits, participant limits, and personal-room context.
Browser meeting surface
Join full-screen LiveKit sessions with video, audio, chat, screen sharing, disconnect handling, and room-aware controls.
Guest join flow
Open a meeting link, preview camera and microphone, then continue through SSO into the room.
Recording controls
Start and stop recordings from the meeting header when recording is enabled for the user and room.
External bridge
Show dial-in details, configure inbound bridge mappings, and invite SIP, Jitsi, or H.323 endpoints into a room.
Tenant administration
Admin routes support tenant records, AI configuration, SIP trunks, and per-tenant conferencing policy.
06 — Architecture
Architecture and security model.
Korum separates user experience, API policy, identity, and media transport so each layer can be operated, audited, and scaled deliberately.
- Next.js and the Continuum design system provide the meeting dashboard, join flow, settings, and in-room shell.
- NextAuth and Keycloak gate access through gscmeet groups, tenant membership, conferencing claims, and refreshable access tokens.
- A Go Fiber API exposes room, recording, token, user, AI, tenant, and SIP bridge endpoints behind JWT middleware.
- PostgreSQL stores tenants, users, rooms, participants, recordings, room permissions, and SIP bridge records.
- LiveKit provides the WebRTC media layer with VP8, H.264, Opus, simulcast, and room tokens.
- A three-node LiveKit cluster uses Redis coordination and dedicated media edge IPs for room distribution.
- LiveKit SIP handles external conferencing interop through inbound trunks, dispatch rules, outbound calls, and room-level bridge permissions.
07 — Use cases
Where Korum fits.
Internal operations
Run daily standups, incident rooms, project calls, and team workshops with identity-bound access.
Customer sessions
Host sales calls, onboarding, support sessions, and success reviews without moving the meeting workflow outside Vianordis.
Regulated meetings
Use recording controls, SSO, tenant policy, and EU-operated infrastructure for committees, reviews, and sensitive discussions.
Hybrid conference rooms
Bridge browser participants with SIP, Jitsi, and H.323 systems when partners or boardrooms use existing hardware.
Admin-managed conferencing
Control limits, tenant access, SIP trunks, and conferencing permissions from protected administrative paths.
08 — Integrations
Connects to the infrastructure enterprises already run.
Korum is built around standard identity, media, database, and telephony components rather than a proprietary meeting silo.
Keycloak
Keeps access tied to organization accounts, roles, and sign-in policy.
FreeIPA / LDAP
Shows how this service fits into the wider Vianordis environment instead of standing alone.
NextAuth
Shows how this service fits into the wider Vianordis environment instead of standing alone.
LiveKit
Shows how this service fits into the wider Vianordis environment instead of standing alone.
LiveKit SIP
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Redis
Shows how this service fits into the wider Vianordis environment instead of standing alone.
PostgreSQL
Stores structured service records in a controlled tenant-aware backend.
SIP / VTC
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Jitsi
Shows how this service fits into the wider Vianordis environment instead of standing alone.
H.323
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Kubernetes
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Custom APIs
Lets approved systems connect without ad hoc exports or manual copy-paste.
09 — Trust
Compliance and trust signals.
Korum is designed so meeting access, recordings, tenant boundaries, and external interop can be described to IT, security, and compliance teams.
Identity
Keycloak SSO with group-based access and tenant membership claims.
Tenant control
Tenant, user, room, limit, recording, AI, and SIP trunk policy live behind protected API routes.
Media control
LiveKit rooms use issued tokens, dedicated media services, and centrally operated signaling.
Interop governance
Room-level bridge records define inbound dial-in, PINs, allowed systems, and outbound invites.
Operational hardening
API middleware includes JWT auth, CORS policy, helmet headers, rate limits, logging, and recovery.
European operation
Korum runs as part of the Vianordis Kubernetes environment with EU-operated infrastructure.
10 — Pricing
Use published pricing or map your meeting estate in a demo.
Korum is listed on the Vianordis rate card. For regulated teams, a demo is the fastest way to review participant limits, recording policy, SSO groups, SIP trunks, and external-room requirements.
11 — FAQ
Questions technical buyers usually ask.
Who is Korum for?
Korum is for organizations that need browser video meetings with stronger control over SSO, tenants, recordings, and external conferencing interop.
Do participants need a desktop app?
No. Korum uses browser-based LiveKit meetings. Participants can open a link, preview camera and microphone, then continue through SSO.
Can Korum connect to external meeting systems?
Yes. The SIP bridge supports SIP/VTC endpoints, Jitsi meetings, and H.323 endpoints when a room bridge and tenant trunk are configured.
How is access controlled?
Access is controlled through Keycloak groups and conferencing claims, with JWT-protected API routes for rooms, recordings, users, tenants, and bridges.
Can meetings be recorded?
Yes, when recording is enabled for the user and room. Hosts can start or stop recording from the meeting header, and recordings remain tied to the room.
Does Korum support scheduling today?
The UI has a scheduled-meetings placeholder, but scheduling is not marketed here as a shipped backend workflow. Current production copy focuses on room creation, live meetings, recording, and bridge controls.
12 — Next step
Move meetings into the same sovereign operating model as the rest of your cloud.
See how Korum can replace unmanaged video SaaS with controlled rooms, SSO, recordings, browser meetings, and SIP/VTC interop.