Equipment, Modules And APIs

Emiko is broader than one product line. Equipment, services, modules, and integrations can share one ecosystem without losing their own identity.

Equipment Keeps Its Product Identity

Each connected product keeps its own name, purpose, model choices, and technical journey. Installation and service instructions stay under that product.

The central compatibility page shows which equipment can use Emiko. Installation, configuration, and service instructions remain in each product section.

Equipment Compatibility Product Overview

Modules Add Shared Services

Modules can add sharing, forecast data, warnings, reporting, or other services to supported product flows. A module can serve more than one product without becoming a new Equipment product.

APIs Connect Other Systems

APIs and integrations can exchange approved data with external systems. Exact plans, endpoints, fields, and limits belong in the relevant API documentation.

One Ecosystem As It Grows

New products and services can use the same identity, access, Site, and operating model. Users do not have to learn a completely separate platform for every new use case.

Where To Go Next

Use this section to understand the ecosystem. Use the Equipment product branch when you need to perform work.

Emiko Overview Check Compatibility