From overview to integration.
Find the right entry points for teams, developers and operators – organised by task rather than internal system structure.
Where would you like to begin?
Concepts and integration paths
The hub organises the available entry points and shows which technical reference is relevant for each task.
Orpheus & modules
Workspaces, tenants and Eurydike, Elysium, Aion, Chiron, Themis, Icarus and Iris.
Authentication & access
Identities, roles, permissions and secure access in the relevant operating context.
Assets & delivery
Media, versions, approvals, connected storage and controlled provision.
Campaigns & placements
Lumiin concepts, Unreal integration, inventory, contexts and delivery.
Integrations & webhooks
Connect existing services, events and downstream workflows without inventing endpoints.
SDKs & tools
Available plugins, technical tools and project-specific integration material.
Learn, track changes, solve problems
Tutorials & examples
Task-based entry points explain common workflows without inventing technical detail.
Changelog & release notes
Product changes and relevant notices are assigned transparently to the respective product.
Troubleshooting
Capture the symptom, environment and affected service, then route it through support.
Workspaces and modules
Orpheus organises work in tenants and workspaces. Aion structures projects, Eurydike manages media, Elysium protects sensitive originals, Chiron brings creative tools together, Themis connects business operations, Icarus keeps communication in context and Iris handles media playback and presentation.
Access is provisioned only within the relevant organisational and operational context. Together, we define which modules and integrations the workflow requires.
Integration and delivery
Lumiin connects defined advertising placements with contextual delivery. Integration covers technical connection, available inventory, eligible contexts, reporting and billing.
API, plugin and integration material is provided on a project basis. For specific questions, we align engine, formats and operating model directly.
Operations start with clear boundaries
A self-hosting configuration is adapted to infrastructure, identity model, storage paths and integrations. Before implementation, we define responsibilities for provisioning, updates, backups and support.
Binding technical prerequisites follow from the concrete system architecture and are documented in the project.
Still have a technical question?
Tell us the product, environment and goal. We can then point you to the right reference or integration path.