Glossary
Definitions of key terms and components used throughout the FLECS platform and documentation.
This glossary provides definitions of key terms, technologies, and components used in the FLECS ecosystem. It helps clarify concepts for developers, system integrators, OEMs, and operators working with the FLECS platform.
A
App
A containerized or packaged software module that runs on a FLECS-enabled device. Typically delivered via the FLECS Marketplace.
App Bundle
A complete package containing an app’s image, metadata, and configuration. Used for deployment through FLECS Core.
App Manifest
The metadata file that defines how an app is built and executed. Usually in manifest.json or flecs.yaml format.
Includes app name, version, ports, environment variables, and permissions.
B
Branch Marketplace
A whitelabeled version of the FLECS Marketplace, tailored to a specific vendor or domain. Can include private apps and customized branding.
C
CI/CD
Continuous Integration / Continuous Deployment. A system used to automate building, testing, and publishing apps to the FLECS Marketplace.
Core
Short for FLECS Core, the runtime that manages app execution, lifecycle, and system integration on supported Linux devices.
D
Device Onboarding Service (D-O-S)
A FLECS feature that enables automated provisioning of new devices. Applies configuration profiles and installs selected apps during device setup.
Docker.platforms
A file listing supported build targets for an app, e.g. linux/amd64, linux/arm64.
E
Editor (App Editor Port)
A web-based UI exposed by an app to allow configuration or visualization. Defined in the app manifest under editors.
F
FLECS Core
An open-source runtime agent that enables secure app management, remote updates, and system orchestration on Linux-based devices.
FLECS Marketplace
A platform for discovering, licensing, and installing industrial software — integrated into FLECS Core and WebApp.
FLECSelerator
The onboarding program that guides vendors through branding, app publishing, and deployment setup during the first subscription phase.
M
Manifest File
See: App Manifest. A required file in every FLECS app that describes its metadata and execution environment.
Multi-instance
A flag in the manifest that allows an app to run multiple instances in parallel on a device.
N
Namespace
A logical grouping of apps, devices, or users. Used for organizing access, visibility, or deployment targets in enterprise setups.
O
OTA (Over-the-Air) Update
Remote update functionality built into FLECS Core. Supports updating apps and system components securely over the network.
P
Private App
An app that is only visible and installable within a whitelabeled Marketplace or specific customer environment.
S
Service Mesh
A communication layer within FLECS Core that enables apps to exchange data securely using standard protocols like MQTT, OPC UA, HTTP.
Subscription (Whitelabeling)
A paid plan that unlocks access to private Marketplaces, WebApp branding, custom domains, and analytics.
T
Tenant (Marketplace Tenant)
A customer-specific or vendor-specific version of the FLECS Marketplace. Can include branding, filtered app selection, and user management.
V
Variant
A version of an app built with different settings, features, or debug levels. Variants require separate Dockerfile.<variant> and Docker.platforms.<variant> files.
W
WebApp
The browser-based UI that runs on FLECS-enabled devices. Used to manage apps, configurations, users, and updates.
WebApp Whitelabeling
Part of the Whitelabel Subscription. Allows customization of the WebApp design and user experience to match your corporate identity.
Y
YAML (flecs.yaml)
A file format used to define the structure and behavior of an app. Alternative to manifest.json. Human-readable and used in some custom deployments.
Last updated
Was this helpful?