Application architecture examples.

Real patterns. Illustrative scenarios.

Explore how a team could build applications on the Createrun framework, from a focused internal tool to connected operational systems. These scenarios describe design choices and evaluation targets.

Illustrative reference scenarios, not customer testimonials or measured deployment results. Each project needs its own functional, security and performance validation.

Discuss your scenario
REFERENCE ARCHITECTURE · RETAIL

A nationwide grocery retailer with a large store network.

Reference architecture; this is not a case study of a named Createrun customer.

This scenario connects recipes, suppliers and production batches so a retailer can investigate a recall. The application design includes versioned recipes, supplier reviews, traceability and retention rules defined by the retailer. Query completeness and response time are evaluation targets.

The same domain model could become a partner-built application. Packaging it for distribution requires testing, licensing and Store review; this scenario is not a currently installable product listing.

What this pattern includes

  • Recipe versioning across a large private-label catalog
  • A multi-stage supplier audit process (RFP → site visit → approval → renewal)

Why Createrun

  • Batch traceability with full chain of custody for product recalls

Design target

  • A weekly catalog approval workflow with category-manager sign-off
  • On-premises deployment, so supplier data stays on the retailer's network
  • Each buying team's users and data are scoped as their own organization
  • Custom forms for each food category without rebuilding the runtime
  • Category managers author their own reports
  • Trace a recalled batch through recipes and suppliers in minutes
  • Validate traceability completeness against the retailer's source records

    • At a glance

    • Industry: Discount retail / grocery
    • Users: Buying + production teams
    • Deployment: On-prem
    • Data residency: In-country
    • Review context: Personal data protection

    A reusable food-production application is a possible publishing opportunity, subject to implementation and release review.

    REFERENCE ARCHITECTURE · LOGISTICS

    At a glance

    • Industry: European logistics / transport
    • Users: Dispatch ops + dock supervisors
    • Deployment: Hybrid (cloud authoring · on-prem runtime)
    • Data residency: EU
    • Review context: Data protection + customs export controls

    Designed to replace a patchwork of spreadsheets, a custom .NET intranet, and a third-party TMS with one Createrun workflow.

    A European road-freight operator running three depots from one workflow.

    Reference architecture; this is not a case study of a named Createrun customer.

    This scenario brings shipment, dock and driver-compliance records into a shared application. Operations staff help define the process; the team validates changes and access rules before deployment.

    A staged shipment workflow drives every delivery. Configurable screen components let dispatch supervisors add fields per route, such as a dangerous-goods class or customs document links, without touching code.

    What this pattern includes

    • A seven-stage shipment workflow with parallel customs and driver-compliance branches
    • Dock-arrival forms designed for rugged tablets; scan volumes validated during the pilot

    Why Createrun

    • Three depots on three instances, licensed and updated from the Createrun Store

    Design target

    • Audit-ready telemetry feeding the team's existing monitoring stack
  • Operations staff work with developers to define and validate workflow changes
  • Supervisors add route-specific fields through configurable screen components
  • The Createrun Store licenses and updates all three instances
  • Telemetry plugs into the monitoring stack the team already runs
  • Cut per-shipment manual data entry by replacing re-keying with structured forms
  • Retire the spreadsheet, intranet, and TMS patchwork and make Createrun the system of record
    • REFERENCE ARCHITECTURE · HEALTHCARE

    A mid-size hospital system running clinical operations on premises.

    Reference architecture; this is not a case study of a named Createrun customer.

    This scenario assumes a hospital requires local processing of patient data. It explores internal tools for admissions, materials management and incident reporting, with clinical and privacy requirements evaluated separately.

    The proposed design uses a locally hosted instance and a compatible local AI model. The deployment review must account for telemetry, support access, licensing, updates and integrations before an isolation claim can be made.

    What this pattern includes

    • Admissions intake forms with conditional fields per department
    • Materials management with par-level alerts and a supplier portal

    Why Createrun

    • Clinical incident reporting with a multi-stage review process

    Design target

    • Single sign-on through the built-in identity provider (OpenID Connect)
  • An on-premises install on the hospital's own servers
  • Customer-authored project files and custom source available for review; modeled Createrun functionality delivered as DLLs, with framework and third-party dependencies reviewed separately
  • No mandatory cloud telemetry; the observability stack is opt-in and fully local
  • Users sign in once through the built-in identity provider, so access is managed in one place
  • Document application dependencies, their licenses and the evidence available for review
  • New internal tools ship without any patient data leaving the network

    • At a glance

    • Industry: Private healthcare
    • Users: Clinical + admissions + materials
    • Deployment: On-premises
    • Data residency: Hospital network only
    • Identity: The built-in identity provider (OpenID Connect single sign-on)

    Customer-authored project files and custom source can be reviewed for an audit; modeled Createrun functionality is delivered as DLLs. Neither grants ownership of the framework nor establishes regulatory compliance.

    MORE REFERENCE ARCHITECTURES IN PROGRESS

    More reference architectures are in progress. If you would like to see how one of these patterns maps to your organization, get in touch and we will walk through it together.

    In progress · Manufacturing

    Shop-floor data collection and a supplier portal for a mid-market manufacturer.

    Field-data forms run on warehouse tablets, and back-end queries roll up to executive dashboards.

    In progress · Financial services

    Internal compliance reporting and KYC review for a mid-tier bank.

    Multi-stage approvals and query access controls, with secret storage and rotation evaluated for the deployment.

    In progress · Public utility

    Customer-billing exception workflows for a regional utility.

    Case management for field workers, with role-based visibility and data-minimization rules defined for the project.

    Your scenario?

    Your industry is not listed here.

    Book a demo and we will map a reference architecture to your use case and walk you through it.

    Book a demo →

    See it working on a scenario like yours.

    Bring your application requirements, or explore a development environment for projects in your preferred stack. We will agree a focused evaluation with you.

    Start for free