# 👋 Welcome to FLECS

## **The shared software layer for industrial automation**

FLECS is a neutral platform for **Software Defined Automation**.

It provides the shared software layer that turns fragmented industrial software delivery into a **scalable, secure, and role‑respecting ecosystem** – across machines, vendors, and lifecycles.

Industrial automation does not suffer from a lack of innovation. It suffers from a **scaling problem**:

- Software is developed by many actors: OEMs, component manufacturers, integrators, and app vendors
- Operation, updates, and responsibility remain fragmented
- Integration effort, lifecycle risk, and security exposure increase over time

FLECS addresses this structural challenge by standardizing how industrial software is **packaged, distributed, deployed, updated, and operated.** Without replacing existing roles or customer relationships.

## 👥 Who is this documentation for?

This documentation is structured by role. Choose your perspective to get started faster:

- **Machine Builders / OEMs** Build branded, vertical software platforms for your machines. Separate hardware and software delivery, manage updates, and create new digital revenue streams.
- **Component Manufacturers** Package, distribute, maintain, and update your software at scale, securely and CRA‑ready, without losing ownership or visibility.
- **Plant Operators** Operate heterogeneous machines with consistent software rollout, fewer platforms, and clear responsibility across the full lifecycle.
- **App Vendors & Developers** Build, publish, and distribute industrial apps via marketplaces, from public reach to fully branded ecosystems.

## 🧩 What FLECS provides

FLECS is **not**:

- a replacement for PLCs, SCADA systems, or engineering tools
- a proprietary lock‑in platform
- a consumer‑style app marketplace

FLECS **is**:

- a shared software layer for industrial operation
- a standardized runtime and lifecycle environment
- a foundation for branded marketplaces and digital business models

FLECS is built around two layers:

- **FLECS Core** runs directly on every Linux-based device – on-premise, offline-capable, no cloud dependency required.
- **Connected Services** is the server-side layer for app management and catalog, fleet management, app distribution, licensing, and business tooling – deployable as managed, dedicated, or self-hosted.

At its core, FLECS enables:

- Standardized packaging and distribution of industrial software
- Secure deployment and update management across device fleets
- Operation on Linux‑based PLCs, IPCs, edge devices, and cloud environments
- Whitelabeled platforms and marketplaces under your brand
- Clear separation of responsibilities between all roles

## 🚀 How to use this documentation

Use this documentation as a practical guide to understand, evaluate, and implement FLECS:

- [**What We Do**](https://docs.flecs.tech/introduction/what-we-do/index.md) – Understand the platform logic and ecosystem model
- [**Our Features**](https://docs.flecs.tech/introduction/our-features/index.md) – Explore concrete capabilities and system components
- [**First Steps**](https://docs.flecs.tech/fundamentals/first-steps-with-flecs/index.md) – Install, deploy, and run your first FLECS setup
- [**Connected Services**](https://docs.flecs.tech/flecs-marketplace/overview/index.md) – Fleet management, app distribution, and business tooling
- [**Developer Guides**](https://docs.flecs.tech/engineering/index.md) – Build, publish, and manage industrial apps

If you are unfamiliar with specific terms, refer to the [**Glossary**](https://docs.flecs.tech/foundation/glossary/index.md) for precise definitions.

FLECS is productive, not conceptual.

A fully branded platform can be live within **6 weeks** via the FLECSelerator onboarding, running on your infrastructure, under your control.

This documentation is your reference for building scalable, software‑defined automation with FLECS.