Own the audio catalog
Keep tracks, metadata, artwork, licenses, HLS outputs, podcasts, and playlists in systems operated under the Vianordis environment.
Vianordis--:--:-- UTCVianordis / ED. 02 / 2026
§ 07 — App support
Sonoris
Sovereign audio publishing for music, podcasts, and live sessions.
Sonoris lets organizations host tracks, playlists, podcasts, listening rooms, and live streams in one EU-resident audio platform instead of scattering media, rights, shares, and audience activity across consumer streaming services.
01 — Problem
Audio teams lose control when every format lives in a different tool.
Music, podcasts, live sessions, and community listening are usually managed through separate consumer platforms. That makes identity, rights, visibility, audience access, reporting, and data residency hard to govern, especially for organizations that must explain where content and listener activity live.
- Tracks, podcast episodes, live audio, playlists, and audience rooms are spread across disconnected services.
- Rights, licenses, artwork, metadata, and visibility rules are difficult to keep consistent.
- Public sharing often means surrendering catalog control to a third-party distribution platform.
- Teams lack one place to see plays, reports, ownership, and publication status.
- Regulated organizations cannot easily prove where audio assets, metadata, and access decisions are stored.
02 — Solution
Sonoris unifies audio publishing under the Vianordis operating model.
Sonoris combines a Next.js creator workspace, a Go API, Keycloak identity, PostgreSQL catalog records, Ceph object storage, an ffmpeg HLS worker, and real-time room services. Teams can upload audio, enrich metadata, transcode for playback, publish podcasts, create playlists, issue controlled shares, and host listening sessions without leaving the sovereign environment.
- Creators manage tracks, artwork, categories, lyrics, licenses, visibility, playlists, podcasts, rooms, and live streams from one product surface.
- Operators keep identity, tenant boundaries, object storage, database records, and public access paths inside Vianordis infrastructure.
- Audiences receive browser playback, public share links, RSS feeds, listening rooms, and live-session access through controlled routes.
03 — Benefits
Business outcomes before audio features.
Sonoris is built for teams that want the reach of modern audio publishing without losing governance over content, users, distribution, and data residency.
Publish more formats from one place
Use one platform for music libraries, podcast feeds, curated playlists, controlled shares, synchronized rooms, and live audio events.
Control audience access
Use private, unlisted, and public visibility with expiring or max-use share tokens for tracks and playlists.
Reduce operational friction
The upload, transcode, playback, sharing, and publishing path is part of one product instead of a chain of ad hoc media tools.
Support rights and moderation
Attach licenses, categories, lyrics, descriptions, and artwork to catalog records, and collect track reports for review.
Bring audio into real-time workflows
Run social listening rooms, room chat, live streams, and agent-driven playback requests around the same audio catalog.
04 — How it works
From upload to governed distribution in three steps.
- 01
Upload and enrich
Creators add audio with title, description, artist, category, lyrics, artwork, license, source, and visibility metadata.
- 02
Transcode and publish
The backend stores originals in S3-compatible object storage, the worker prepares HLS playback, and teams publish through playlists, shares, podcast episodes, or RSS feeds.
- 03
Engage and govern
Audiences listen in the browser, join rooms or live sessions, and teams monitor plays, reports, shares, and access through identity-bound routes.
05 — Features
What teams can actually do in Sonoris.
Track upload and library
Create tracks, upload audio, manage title, description, artist, category, lyrics, artwork, license, source, status, visibility, and play counts.
HLS playback pipeline
Serve browser-friendly playback through HLS manifests and segments after worker-based transcoding from the original uploaded asset.
Playlists and controlled shares
Create playlists, add or remove tracks, search collections, and issue public share links with optional expiry and use limits.
Podcast publishing
Create shows, manage episodes backed by catalog tracks, and expose token-protected RSS and episode audio routes for podcast clients.
Listening rooms
Create open or invite-only rooms, connect participants, synchronize room state, and post room messages around shared listening sessions.
Live audio streams
Schedule, start, stop, and connect to live streams with persistent metadata and optional recording track references.
Search, licensing, and library views
Search tracks and playlists, browse library content, and use seeded Creative Commons or custom license records.
Agent playback surface
Expose authenticated agent endpoints for search, track operations, playlist actions, uploads, and browser playback requests.
06 — Architecture
Architecture and security model.
Sonoris separates the creator UI, API policy, catalog storage, object storage, transcode worker, public playback, and real-time listening layer so each part can be operated and reviewed deliberately.
- Next.js 15 and @gsc/web-kit provide the authenticated audio workspace, player, upload flow, shared pages, and chat routes.
- NextAuth and Keycloak provide user identity, refreshable access tokens, and organization sign-in.
- A Go Fiber API exposes protected track, playlist, search, share, room, podcast, library, live, and agent routes behind JWT and tenant middleware.
- PostgreSQL schemas store catalog, licenses, playlists, shares, podcasts, rooms, messages, live streams, reports, agent play requests, and navigation records.
- Ceph RGW / S3-compatible object storage holds original audio, artwork, HLS output, and waveform assets.
- A Go worker uses ffmpeg to transcode uploaded audio for HLS playback.
- A Go WebSocket service supports room synchronization for live listening sessions.
- Public routes expose token-scoped track shares, playlist shares, podcast RSS feeds, and episode audio without opening the protected API.
07 — Use cases
Where Sonoris fits.
Creator and label catalogs
Publish music, artwork, metadata, lyrics, licenses, playlists, and controlled share links without relying on consumer streaming dashboards.
Corporate audio libraries
Host training audio, leadership briefings, product explainers, internal podcasts, and curated playlists inside an identity-bound environment.
Podcast networks
Manage shows, episodes, publication metadata, RSS access, and episode audio delivery from the same catalog used for playback.
Live audio events
Create scheduled streams for announcements, interviews, community sessions, or private organization broadcasts.
Social listening rooms
Bring audiences together around synchronized playback, invite-only rooms, and room chat.
Regulated media distribution
Use EU-resident storage, tenant-aware APIs, controlled visibility, and share limits when content cannot be pushed through unmanaged platforms.
08 — Integrations
Built on infrastructure teams already understand.
Sonoris uses standard identity, storage, media, and runtime components instead of a closed consumer-media stack.
Keycloak
Keeps access tied to organization accounts, roles, and sign-in policy.
NextAuth
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.
Ceph RGW / S3
Provides the governed place where service data and files are stored.
ffmpeg
Shows how this service fits into the wider Vianordis environment instead of standing alone.
HLS.js
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.
WebSocket rooms
Shows how this service fits into the wider Vianordis environment instead of standing alone.
RSS feeds
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Agent / MCP tools
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.
Sonoris is designed so catalog ownership, audience access, public sharing, and playback infrastructure can be explained to IT, security, legal, and communications teams.
Data residency
Audio metadata lives in PostgreSQL and media assets live in EU-operated S3/Ceph object storage.
Identity
Protected routes use Keycloak JWT validation and tenant middleware before catalog or room access.
Visibility
Tracks, playlists, podcasts, and live streams support private, unlisted, or public visibility patterns.
Share control
Public track and playlist shares use opaque tokens with optional expiry and max-use limits.
Rights context
Catalog records support licenses, ownership, categories, descriptions, lyrics, artwork, and source metadata.
Moderation path
Track reports capture reason, detail, status, creation time, and review timestamps for follow-up.
Operational hardening
The API uses specific CORS origins, bearer auth, upload cleanup, health checks, and Kubernetes deployment primitives.
10 — Pricing
Start with the published plan or map your audio workflow in a demo.
Sonoris is listed on the Vianordis rate card. For media teams and regulated organizations, a demo is the fastest way to review catalog structure, storage, podcast publishing, live events, sharing policy, and identity requirements.
11 — FAQ
Questions technical buyers usually ask.
Who is Sonoris for?
Sonoris is for creators, media teams, communications teams, podcast publishers, and organizations that need controlled audio hosting instead of unmanaged consumer streaming tools.
Is Sonoris only for music?
No. Sonoris supports tracks, playlists, podcasts, shared audio links, listening rooms, live streams, and internal audio-library use cases.
How are uploads handled?
Users create a track record, upload the original audio asset, and the backend moves the track through upload and transcode states before HLS playback is available.
Can podcasts be published through RSS?
Yes. Sonoris stores podcast and episode metadata, then exposes token-protected public RSS and episode audio routes for podcast clients.
Can audio be shared publicly?
Yes. Owners can create public track or playlist share tokens, with optional expiration and max-use controls.
Does it support live or interactive listening?
Yes. Sonoris includes listening rooms with messages and live stream routes for scheduled, live, and ended stream states.
How is access controlled?
Authenticated API routes are protected by Keycloak JWT validation and tenant middleware. Public playback paths are limited to share tokens or podcast RSS tokens.
12 — Next step
Bring audio publishing into the same sovereign platform as the rest of your cloud.
See how Sonoris can replace scattered streaming, podcast, sharing, and live-audio tools with one governed workspace for catalog control and audience engagement.