This document provides a description of Kaltura’s main service layers, system components and their recommended setup based on several scales of deployments. The document also recommends Kaltura’s ‘best practices’ for system architecture design, to be considered when planning self-hosted deployments of Kaltura’s platform. This document targets technical readers who are wishing to familiarize themselves with the structure, components, and different physical setup considerations for installing and deploying the Kaltura platform.
Extending Kaltura - Core Programming
This quick FAQ outlines the character length limits on Kaltura metadata fields.
Collection of relevant documentation for Kaltura Community Edition
This article describees the KalturaAuditTrail API.
When working with the Kaltura API, a Kaltura Session (aka KS), represents the validation required to authenticate the user calling/performing the API action.
To create a KS, you need a Publisher Account in the Kaltura Server and that account should have API access.
This information is intended to address concerns regarding API backward compatibility and explain best practices for using Kaltura APIs.