Skip to content

☁️ Hosting & Deployment

How FLECS runs in your environment

FLECS is composed of two layers:

  • FLECS Core runs directly on every Linux-based device – on-premise, offline-capable, always under your full control.
  • Connected Services is the server-side platform layer for fleet management, app distribution, licensing, and business tooling.

FLECS Core always operates on the device itself. The deployment question applies to Connected Services – and here you have three options.

Three deployment options

Managed Tenant

The fastest path to production.

FLECS operates the platform infrastructure. You get a dedicated tenant on shared infrastructure – ready immediately, without building or maintaining any server environment.

  • Shared infrastructure, isolated tenant
  • Hosted and operated by FLECS
  • Own branding and domain
  • Scales with your growth
  • No server maintenance on your side

This is the recommended starting point for most companies.

Dedicated Instance

Fully isolated, operated by FLECS.

Your own isolated instance, hosted by FLECS. Complete data separation from other tenants, with your own domain and the ability to manage sub-tenants for your customers and partners.

  • Dedicated, fully isolated infrastructure
  • Own branding, domain, and sub-tenants for customers & partners
  • FLECS handles operation, updates, and maintenance
  • Full data separation

This option suits companies with higher isolation requirements or those managing multiple customer environments under one platform.

Self-Hosted

Total control on your own infrastructure.

The complete FLECS platform runs on your servers. You control data, updates, and operations without any external dependencies.

  • Runs on your own servers or private cloud
  • No external dependencies
  • Full data sovereignty
  • Your own update cycles and maintenance

This option is available as part of the Enterprise Edition.

FLECS Core is always on-premise

Regardless of which Connected Services deployment option you choose, FLECS Core on the device never changes:

  • 100% on-premise execution
  • No cloud dependency for device operation
  • Offline-capable

Devices continue to function normally even when the Connected Services layer is unreachable.

Open standard: Margo

FLECS is compatible with the Margo interoperability standard for edge application management.

This means no proprietary ecosystem lock-in: you can switch deployment options at any time without losing your investment in apps, configurations, or workflows.

Getting started: FLECSelerator

Every deployment starts with the FLECSelerator – a structured onboarding program to get your platform ready for production.

It covers:

  • Platform and branding configuration
  • Marketplace and WebApp setup
  • System provisioning and integration
  • Initial app publishing and operational readiness

✅ The FLECSelerator ensures your platform is correctly configured before going live. 💡 The onboarding fee is fully credited toward your first subscription year.

For a detailed overview, a whitepaper is available on request.

Ownership and responsibility

Regardless of deployment option:

  • You control branding, pricing, users, and customer access
  • You retain customer relationships and billing responsibility
  • FLECS provides and maintains the platform technology
  • You scale independently using CI/CD and integration tooling