Scale on infrastructure already paid for
Local and distributed processing across ordinary workstations and a simple Windows server—without requiring a dedicated shared-storage investment.
Kiff Production
We build infrastructure from inside production.
We find where information, labour and time disappear in real unscripted television workflows—and build the systems that carry production knowledge from recorded material into the edit.
- Hours processed
- 5,000+
- Programme rough cuts
- 70
- Up to workflow improvement
- 15×
- Gullruten nominations
- 2×
What exists now
The achievement is not an app. It is a production capability.
The difficult part was learning the workflow deeply enough to know what must survive from one stage to the next—and then building infrastructure around that knowledge.
One continuous production flow
-
01
RecordedMedia, speech, sound and production context
-
02
ProcessedHigh-volume local and distributed infrastructure
-
03
StructuredLogs, scenes, people, stories and relationships
-
04
EditableManuscripts, boards, AAF timelines and rough cuts
- Hours processed
- 5,000+
Logging, transcription and structured production material already carried through the systems.
- Programme rough cuts
- 70
Seventy programmes carried from production information into generated editorial timelines.
- Workflow improvement
- 15×
Up to fifteen times the efficiency where logging is a load-bearing part of production.
- National recognition
- 2×
Public innovation nominations at Gullruten in consecutive years.
Keep production knowledge continuous
Speech, metadata, scenes, stories, multicam and external sound remain connected instead of being repeatedly copied, flattened and reconstructed.
Deliver into editorial—not into a demo
Manuscripts, scene boards, searchable material, AAF timelines, rough cuts and music reports arrive as usable production outputs.
The durable layer
“The application has no experience. It just works.”
The experience lives in the people who can enter a production, find where information and labour disappear, and rebuild the infrastructure around the real workflow. The code can change. That capability remains.
How we build
Start with production reality. Keep rebuilding against it.
Begin at the live workflow
Observe where people wait, rebuild information, lose context or compensate manually. The system starts there.
Integrate before replacing
Work with the tools, storage and editorial practices already carrying the production. Remove the breakpoints without demanding a clean-room workflow.
Measure the whole chain
A fast transcription step means little if assistants or editors still inherit the same bottleneck. The outcome is measured at the edit.
Let edge cases change the architecture
Missing timecode, external audio, multicam, changing metadata and new editorial needs are not exceptions to hide. They are production.
Local processing
Distributed compute
Transcription
Logging
Story structure
Scene boards
AAF
Multicam
External sound
Rough cuts
Music reporting
Production signals
2023 → now
A sequence of production problems becoming infrastructure.
Each generation is evidence of the same capability: meet the real constraint, preserve what matters, and build the next layer.
-
2023—2024
Distributed local speech infrastructure
Speech recognition and speaker separation distributed across existing post-production workstations. Large interview volumes moved directly into established CatDV and Avid workflows with searchable markers.
-
2025
From a processing pipeline to production memory
Thousands of hours became searchable, structured and reusable inside active Norwegian television productions. The work received its first Gullruten innovation nomination.
-
2025—2026
From production memory to story structure
Logging, scene construction, story structure, boards and manuscripts became connected representations of the same production information.
-
2026
From story structure into the edit
Scene boards, AAF timelines, multicam, external sound, rough cuts and music reports now carry that structure into operational editorial outputs.
A surface in the world
The work has a surface now.
We build the surface contact requires without deciding who should find it or which contact will matter. Someone may arrive knowing why—or discover the connection here. We let contact happen, update from what actually changes, and move.