Platform architecture


The platform is designed to solve a wide range of tasks for information systems production in the most efficient way.

Platform architecture

The Flexberry platform can be divided into 2 parts:

  • Tools that are used for design and programming (design stage - Design-Time)
  • Ready-made components that allow you to build by bricks an application or information system (program execution stage - Run-Time)

Architecture design tool – Flexberry Designer

Generators allow you to get the application source code based on the application model. The generated application is a workable application, furthermore it can be run without any necessary modifications.

Try our products

Platform products are available for free during the trial period or for open projects. Try it, and decide if they are suitable for your tasks.

Try now

Applications architecture

The architecture of applications built on the platform typically includes the following elements:

Why Microsoft .NET / Mono have been chosen?

  • Microsoft .NET and Mono – are the honest OpenSource, C# – programming language is ECMA, ISO standard
  • Cross-platform
  • Widespread language, well-developed ecosystem

Why OData has been chosen?

  • Client-server communication protocol describes both data structure and sampling setup in the best way
  • It is used as the protocol in such products as SAP, 1C
  • OData, unlike GraphQL, was originally conceived as a protocol for enterprise applications

Why EmberJS has been chosen?

  • Designed for complex multi-functional web applications
  • The most popular Open Source framework isn’t managed by any corporation
  • There is full MVC "out of the box" unlike React or Vue


  • System software
    • OS
      • Microsoft Windows
      • Linux
    • DB
      • Microsoft SQL Server
      • Postgre SQL
      • Oracle DB
      • MongoDB
  • Client software
    • Modern browser
    • Mobile device

Additional features

Another look at the application architecture.

Order a free demo

Sign up for a remote demonstration to see the Flexberry platform capabilities including implemented applications.

Apply for a demonstration

Functional subsystems

List of functional subsystems and its architecture

Functional subsystems implement various of special features in the applications. Used open solutions are described below.

Subsystem Architecture elements
Flexberry Base – subsystem of input and search of information (data tracking)
  • Data warehouse (PostgreSQL, Microsoft SQL Server, Oracle, MongoDB, etc.)
  • The data access layer based on Flexberry ORM
  • Logic and user interface layer
Flexberry GIS – geographic information subsystem
  • Data map warehouse (PostgreSQL, Microsoft SQL Server)
  • The layer of data map access based on Flexberry ORM
  • GeoServer – geo data server
  • Leaflet-based map layer mapping components
  • Integration with the Flexberry Base
Flexberry Service Bus – an enterprise service bus
  • The service of messages reception and transmission
  • Administrative application for management and monitoring
Flexberry Analytics – reporting and business analytics
  • Pentaho-based reporting server
  • An OLAP server based on Mondrian
  • Integration with the Flexberry Base
Flexberry BPM – process approach
  • jBPM-based BPM process execution system
  • The layer of BPM solution interface abstraction
  • Integration with the Flexberry Base
Flexberry Portal – corporate portal
  • Corporate portal based on Alfresco
  • Integration with the Flexberry Base

Integration with the platform and its capabilities expansion

The platform is an open solution and available for expansion in a variety of ways

  • Universal integration approach:
    • Data warehouse
    • Authorization system (authentication)
    • User interface
  • Integration at the platform level:
    • Flexberry Service Bus
    • OData
    • Flexberry ORM object model
  • Architecture expansion due to the possibility of replacing components

Have any questions?

Just ask them in any convenient way and we will answer them.