Skip to content
MIGSLAB
LinkedIn
All projects
PRJ-01Platform initiative

AIRO

Adaptive Integration and Rapid Optimization

AIRO is a platform initiative rather than a single application. It treats a business application as a description: entities, forms, views, navigation, security and processes are all stored as metadata that the platform can interpret.

The aim is to make a new business capability a matter of configuration wherever that is enough, and an extension point where it is not.

Category
Platform initiative
Status
Active initiative
Technologies
.NET / C# / ASP.NET / Vue 3 / TypeScript / PostgreSQL / SQL Server
  1. 01Define
    • EntitiesObjects and attributes
    • Forms and viewsHow records are shown
    • NavigationMenus and actions
    • Security rolesAccess per entity
  2. 02Package
    • ConstructsReusable application units with import and export
  3. 03Forge
    • Metadata forgeTurns definitions into runtime metadata
  4. 04Run
    • Adaptive entitiesData services shaped by metadata
    • FluxStaged processes across entities
    • CortexMapped API surfaces
  5. 05Connect
    • Data connectorsPostgreSQL, SQL Server, MySQL, MongoDB
    • MessagingQueue and Pulsar integration
From definition to runtime. Business applications are described as metadata, then forged into what the platform serves.
A / Capabilities

Platform architecture

  • Metadata-driven design

    Entities, attributes, forms, views, menus, selection sets, dashboards and security roles are defined as data, not hand-written for each application.

  • Reusable application constructs

    Related definitions are grouped into constructs that can be exported and imported between environments, with a recorded history of both.

  • A forging step

    Definitions are forged into runtime metadata for entities, navigation, dashboards, processes and APIs, separating what is being edited from what is being served.

  • Platform extensibility

    Flux models staged processes across entities, and Cortex exposes mapped API surfaces, so solutions can grow beyond generated forms and views.

B / Engineering notes

How it is built

  • Separate services

    Metadata, adaptive entities, authentication, organization management and public access are built as separate .NET services.

  • Storage independence

    A shared SDK provides data connectors for PostgreSQL, SQL Server, MySQL and MongoDB behind a common core.

  • Engineering philosophy

    The platform exists to move repeated work out of each application and into one place, where it can be designed and improved once.