# 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

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:** Understand the platform logic and ecosystem model
* **Our Features:** Explore concrete capabilities and system components
* **First Steps:** Install, deploy, and run your first FLECS setup
* **Marketplace as a Service:** Learn how to launch your own branded marketplace
* **Developer Guides:** Build, publish, and manage industrial apps

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

## 📚 Key entry points

* [What We Do](https://docs.flecs.tech/product-docs/introduction/what-we-do): Platform purpose and ecosystem logic
* [Our Features](https://docs.flecs.tech/product-docs/introduction/our-features): Core capabilities and components
* [First Steps with FLECS](https://docs.flecs.tech/product-docs/fundamentals/first-steps-with-flecs): Getting started hands‑on
* **Need help with a term?** See the [Glossary](https://docs.flecs.tech/product-docs/foundation/glossary) for definitions of key concepts.

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.

## Quick links

{% content-ref url="what-we-do" %}
[what-we-do](https://docs.flecs.tech/product-docs/introduction/what-we-do)
{% endcontent-ref %}

{% content-ref url="our-features" %}
[our-features](https://docs.flecs.tech/product-docs/introduction/our-features)
{% endcontent-ref %}

{% content-ref url="../foundation/glossary" %}
[glossary](https://docs.flecs.tech/product-docs/foundation/glossary)
{% endcontent-ref %}

## Get Started

We've put together some helpful guides for you to get setup with our product quickly and easily.

{% content-ref url="../fundamentals/first-steps-with-flecs" %}
[first-steps-with-flecs](https://docs.flecs.tech/product-docs/fundamentals/first-steps-with-flecs)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.flecs.tech/product-docs/introduction/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.