Skip to content

OpenPlatform

Developer hub · firefly-oss

OpenPlatform

Business modules, shared services, and adapter libraries — documented from the repositories that exist today.

Purpose, layer maps, OpenAPI links, and honest gaps for every module id. Framework bootstrap stays in the Jafly docs.

Attitude makes the difference.

OpenPlatform layers: experience, domain, core, and adapters in firefly-oss
  • Train pin 26.10.19
  • Spring Boot 4.1.1
  • Java 25
  • Org firefly-oss

What this hub covers

OpenPlatform is the catalogue of modules under firefly-oss: customers, onboarding, products, agreements, distribution, accounts, payments, lending, risk, and shared identity, plus libraries such as library-psps and library-rails.

Each module page maps real repositories (core-*, domain-*, exp-*), links OpenAPI where published, and states gaps without inventing services. Product narrative lives on fireflysoftware.io/openplatform.

Find your path

New reader

Start here

How OpenPlatform equals firefly-oss, and how to pick a module page.

Platform

Architecture

Experience, domain, and core bands, with adapters at the boundary.

Domain

Module catalogue

Every module id with repository maps and OpenAPI links.

API consumer

OpenAPI index

Known specs per module repository. No invented endpoints.

How modules compose

Channels call experience services. Domain services coordinate commands. Core services persist state. Providers and institution systems sit behind adapters.

OpenPlatform layers: experience, domain, core, and adapters

Pin for consumption accuracy: Spring Boot 4.1.1 via com.firefly:firefly-parent and framework parent 26.10.19. See Versioning and BOM. Framework tooling: Jafly docs.

Elsewhere