For Solution Architects & Systems Integrators
Deliver a working proof of concept, assembled in the visual builder and running on your preferred infrastructure. Handoff documentation generates automatically from the workflow itself, so it stays current even as the workflow changes. The TypeScript SDK is available for requirements the visual builder doesn't cover.
Your evaluation journey
Evaluate Norsk Studio, from initial proof of concept through to proposal and production deployment.
Norsk Studio runs the same platform on-premises, on any cloud provider, and in hybrid configurations, so that a single deployment model can apply across customers with different infrastructure, rather than requiring a different approach for each engagement. Customers choose the mode that fits their own requirements — data sovereignty, regional compliance, or a staged migration — without changing the underlying platform.
Read the deployment docs →Use an evaluation licence on an active engagement, with a customer's real protocol mix, asset formats, and infrastructure. The proof of concept assembled in the visual builder becomes the implementation: your delivery team extends it via the SDK if needed, then deploys it — the same workflow graph throughout, with no rebuild. Redundancy, failover behaviour, and monitoring can be validated during the proof of concept itself, before the system goes live in front of a customer.
Talk to Us →The auto-generated OpenAPI spec, the exported workflow graph, and the deployment guide together form a handoff package that both internal and customer teams can use to operate the deployment independently. Workflow graphs are versioned JSON, so they can also be stored and reused across future engagements with similar requirements — each delivered engagement adding to a reusable library rather than starting from a blank page.
Browse the workflow configuration docs →Deploy Norsk entirely on client-owned infrastructure with no external calls in the media path — for clients with data sovereignty requirements or security perimeters that put cloud off the table entirely.
Any major cloud provider or private cloud, in any region. Norsk is genuinely cloud-agnostic — not cloud-first with an on-prem asterisk. The same workflow runs in whichever region the client's audience and compliance requirements demand.
On-prem ingest from existing hardware, cloud processing and CDN delivery. The most common architecture for broadcasters modernising without a full migration — and one Norsk handles from a single workflow, not a stitched-together approach.
G&L has delivered two major productions on Norsk — different clients, different verticals, different technical challenges. Components built for one engagement carried directly to the next.
With Norsk, we have all the media processing needs covered, and can focus on the business logic instead.
G&L built Playout Manager — a multi-tenant live streaming platform now in production with major German public broadcasters including WDR. The Compositor component, handling real-time HTML5 overlay compositing over live video, is built entirely on Norsk. G&L owned the business logic, scheduling, and multi-tenant architecture. Norsk handled the media processing.
Playout Manager case study →Norsk enabled us to deliver complex media processing in record time with high system availability.
G&L reused Norsk components from the WDR work to build the European Parliament's streaming platform — 32 SDI inputs, 32 audio language tracks per video (beyond SDI's native 16-track limit), hardware-accelerated transcoding, and distribution to CDN, social media, and VoD.
European Parliament case study →— —Alexander Leschinsky, CEO, G&L Systemhaus
Get a free evaluation licence for your current engagement, and build the proof of concept on a real bid, not a sandbox. Or talk to a solutions engineer about a partner arrangement.
Talk to a solutions engineerTotal cost of ownership (TCO)
Flexible billing models — per channel, per hour, or shaped to your use case. No lock-in to a cloud provider's pricing model. Deploy on your hardware or your cloud — the economics stay yours.
On-premises, AWS, GCP, Akamai, or hybrid. Deploy where your content and your team are — and move it when your situation changes.
Billing that fits your use case — per concurrent channel, per hour, or a model shaped to how you actually run. Talk to us about what works for your economics.
No mandatory cloud intermediary. Your content, metadata, and audience data remain in your infrastructure — including for European procurement and data-sovereignty requirements.
Fixed licence, stated assumptions. Model your costs before you commit. No surprise bills when a big event drives a spike.