In this section, an Emiko Organization is the company or entity object for Partners and Resellers, an Emiko Site is a site, location, or operating area under that Organization, a Partner owns and operates its own Emiko Site or Sites, and a Customer is a user that requests or uses access through Emiko App. Use Emiko Account only for commercial, billing, plan, contract, Service Fee, or customer-account context.

What Emiko Brings Together

Emiko connects equipment, organizations, users, live data, platform access, modules, and APIs and integrations into one operating model.

• Equipment can be assigned, monitored, and operated inside the same platform.
• Equipment can connect directly to the platform through the supported connectivity path for the relevant equipment.
• Partners can manage access, working relationships, and operational responsibility.
• Customers can request access from the outside and use company or individual identities in Emiko App.
• Resellers and Vikingegaarden can support onboarding, setup, and managed operation where relevant.
• Modules and APIs can extend the ecosystem without changing the core access model.

One Login For The Whole Ecosystem

Emiko Login is used to sign in to Emiko Console and Emiko App. The same identity can be used across supported products, Emiko Sites, Emiko App workflows, and platform services. The visible scope still depends on assigned rights and granted access.

Real-Time By Design

Operational views are live by design. Alarms, state changes, and live values are shown as part of current operation rather than delayed manual refresh work. Historical views such as graphs and reports still belong to the same ecosystem.

Direct Connectivity And Independent Units

Emiko equipment is described as directly connected to the platform when a supported connectivity path is available.

• The ecosystem model explains connectivity through the supported platform path for each connected equipment type.
• Practical connectivity may use GSM, Wi-Fi, or LAN where relevant.
• Individual equipment can operate independently in the ecosystem when the needed connectivity path is available.

Service Sessions And Commercial Flow Variants

The same ecosystem can support app-mediated service-session flows where relevant.

• Common session actions include book, start, stop, and pay when relevant.
• Not every service flow is payment-based.
• Common variants include non-billable use, bill later / invoice flow, and direct in-app payment.
• Partner-defined access and granted scope still control what the user may access and do.

Built For Growth

Emiko is designed to expand into more products, more industries, more services, and more markets over time. The growth model is one ecosystem, one login, one operating model, and room to extend without starting over.

Security & Compliance

Emiko is operated as a cloud-based SaaS ecosystem with role-based access, controlled administrative access, Danish/EU hosting, layered backup protection, central security monitoring and documented supplier assurance.

Security, hosting, backup and compliance documentation can support onboarding, procurement, data processing review, NIS 2 supplier assessment and customer security review.

What You Will Find In This Section

The next pages explain how roles, onboarding, connectivity, operation, service sessions, and growth work in Emiko.