High-Level Architecture

The Innopo high-level architecture defines how modular Business Systems, custom workflow logic, and shared application infrastructure fit together to create complete platforms. It provides a clear, layered structure that balances reusability, maintainability, and flexibility. This page explains how the major parts of the architecture interact and why the system is designed this way.

At a high level, each platform built with the Innopo Modular Systems Framework (IMSF) consists of four core layers: Infrastructure, Business Systems,Workflow Layer, and Interface Layer. These layers work together to produce a consistent yet fully customisable application.

Conceptual Architecture

The architecture can be visualised as a vertical stack of layers, each with a distinct responsibility:

Each layer is isolated but interoperable, enabling rapid development and stable long-term evolution.

1. Infrastructure Layer

This is the foundational layer that all platforms share. It includes the technical stack and core utilities used across every Business System.

Components of the Infrastructure Layer:

• Next.js: Application runtime, routing, server actions.
• shadcn/ui: Shared UI primitives and styling conventions.
• Supabase: Database, migrations, auth, storage.
• API Runtime: Server functions, HTTP handlers, rate limits.
• Session & Context Management: Permissions, role logic.
• Base Schema: Foundational Prisma models used by systems.
• Deployment Infrastructure: Hosting, environments, env variables.

This layer never changes per partner. It provides the foundation upon which all systems operate.

2. Business Systems Layer

The Business Systems layer contains all reusable modules in the Innopo Systems Library. Each system includes its own UI, backend logic, schema, configuration, and documentation. Systems remain versioned and independent, ensuring predictable behaviour.

Examples of Business Systems:

• Authentication System
• Onboarding System
• Quote Engine
• Payments System
• Document Generation System
• Dashboard System
• Automation System

Key principles of this layer:

• Systems are reusable across multiple platforms.
• Each system is pinned to a semantic version.
• Systems follow shared architectural conventions.
• Systems do not contain partner-specific logic.

This layer provides the majority of functionality for every platform, greatly reducing the amount of code that must be written from scratch.

3. Workflow Layer

The Workflow Layer is where each platform becomes unique. It adds the custom rules, decisions, integrations, and branding required for a specific partner. This layer sits above the Business Systems and never modifies system internals.

Workflow Layer Responsibilities:

• Custom approval flows
• Partner-specific logic and state transitions
• Unique pricing, scoring, or rules
• Third-party integrations
• Customised forms or data structures
• Branding and layout adjustments

This layer ensures the platform is uniquely aligned to the partner’s operational workflow.

4. Interface Layer

The Interface Layer provides the unified visual and navigational structure for the platform. It ensures that all systems appear cohesive and that the user experience is consistent.

The interface layer includes:

• Dashboard layout shell
• Sidebar and navigation patterns
• Page templates and section layouts
• Header, footer, and global UI elements
• Shared component styling (via shadcn)

This layer standardises how the platform looks and feels, creating a visual consistency across all assembled systems.

How the Layers Interact

Each layer communicates through defined boundaries, ensuring modularity and maintainability.

Interaction principles:

• Business Systems rely on Infrastructure but are never tightly coupled to each other.
• Workflow Logic extends Business Systems without modifying them.
• Interface Layer provides a unified user experience.
• Systems share common patterns (routing, schema conventions, UI styling) to ensure seamless assembly.

This architectural structure allows Innopo to build platforms quickly while keeping them stable and flexible.

Benefits of This Architecture

• Scalable: New systems can be added without disruption.
• Maintainable: Clear boundaries reduce complexity.
• Predictable: Versioning creates safe upgrade paths.
• Reusable: Systems work across industries and projects.
• Customisable: Workflow layer ensures full partner specificity.
• Consistent: Shared UI and schema conventions create unity.

Summary

The high-level architecture of Innopo combines modular systems, workflow customisation, and unified UI patterns into a single coherent structure. By separating concerns into distinct layers, Infrastructure, Business Systems, Workflow Logic, and Interface, the architecture delivers fast development, long-term stability, and deep customisability. This layered approach is what makes the Innopo Modular Systems Framework efficient, scalable, and uniquely suited for building modern, maintainable platforms.