Source: [Open technology for financial operations](https://fireflysoftware.io/openplatform/) Description: The open business capabilities and engineering foundations behind Firefly operations, connected to existing financial systems. Language: en Firefly OpenPlatform # The open-source modules our services run on. Firefly OpenPlatform covers customers, agreements, payments, and lending, and runs beside your providers and your records. [Book an operations review](https://fireflysoftware.io/contact/) [Explore our services](https://fireflysoftware.io/services/) Firefly OpenPlatform: business modules for customers, agreements, payments, lending, onboarding, products, distribution, accounts and risk, on one open foundation with identity and shared services and a backbone of APIs and events. Your own services, your systems and other providers connect through adapters. Your teams can inspect the code. [Scroll to explore](https://fireflysoftware.io/openplatform/#foundation) The foundation ## What the platform gives a service. 01 ### Reuse business capabilities Use the customer, agreement, payment, and lending modules that fit. 02 ### Connect to existing systems Explicit interfaces to your core, policy, claims, and finance systems. 03 ### Preserve practical control Documented interfaces and agreed portability keep inspection, extension, and transition possible. Open by design ## Change the parts you need, and keep the code if you leave. A closed suite ties change to one vendor’s roadmap. With open modules you change what you need, and Firefly runs the service on them; you can inspect the code and take it with you. BEFORE ### The vendor sets the boundaries AFTER ### You decide where change happens Firefly open modules Your own services and models Other providers and systems Capabilities sit inside one product, so a change waits for the vendor’s next release. As the boundaries open, each responsibility gets the right component: a Firefly module, your own service, or another provider. Not every component needs to be Firefly. Open modules, your own services, and third-party systems work together through explicit connections. Illustrative models, not a comparison of suppliers. ### Access to the code CLOSED-SUITE MODEL Access to the code depends on the supplier’s contract. OPEN COMPOSITION You can inspect the open modules and take them with you; your agreement sets the transition terms. ### How capacity grows CLOSED-SUITE MODEL Capacity and releases may share one deployment unit. OPEN COMPOSITION We set deployment boundaries around the workload, so each part scales on its own. ### What the institution takes on CLOSED-SUITE MODEL A packaged suite puts support with one supplier. OPEN COMPOSITION More control usually means more upgrade work; in a Firefly service, that work is ours. From modules to a working journey ## See how the pieces work together. Each journey shows what the customer does, who decides, and which system records the outcome. BANKING ### Open an account Customer, contract, and financial-record services, coordinated. 1. 01 #### Collect the application The channel captures the request and onboarding data. - Channel - Firefly modules 2. 02 #### Coordinate the opening A domain service links agreement, holder, and account. - Process and decision - Firefly modules 3. 03 #### Create the records Core modules record the account and its first entries. - Firefly modules 4. 04 #### Make it operational Status and parameters make the account usable. - Process and decision - Firefly modules Product rules and accounting controls are set for each implementation. INSURANCE ### Connect an insurance application Firefly handles the shared capabilities; the insurer’s own systems keep their responsibilities. 1. 01 #### Serve the customer or agent Party details, distributor access, and product data, together. - Channel - Firefly modules 2. 02 #### Prepare the application Collect the evidence the insurer’s review needs. - Process and decision - Firefly modules 3. 03 #### Connect the insurer Send the application to its rating, underwriting and policy systems. - Firefly modules - Third party, behind an adapter INSURER SYSTEMS 4. 04 #### Keep the journey connected Link documents and status notices to the customer. - Channel - Firefly modules Policy administration and insurance underwriting are connected systems, not native Firefly modules. [Explore more journeys in the operating-model factory](https://fireflysoftware.io/#operating-model) How it is offered ## What is open source and what is the service. Open-source components keep their licenses; the managed service and your rights in it are defined separately in the agreement. ### Choose components by fit and maturity The service design names the capabilities and integrations it uses. ### Your deployment follows the operation We agree processing locations, cloud, and access for each service. OpenPlatform · Insurance ## We are extending the open foundation into insurance. Today, insurance implementations connect the systems the insurer already uses. Firefly OpenPlatform with four shared capabilities available today: customers, products, agreements and payments. Beside them, in dashed outline, four insurance capabilities in development and not yet available: policy lifecycle, underwriting operations, claims operations and insurance financial flows. Behind, the insurer’s own systems, connected today through adapters and APIs: rating, underwriting, policy administration and claims. Dashed outlines are in development; solid pieces are available today. 01 ### Policy lifecycle Product, party, and agreement foundations, extended to policies and renewals. 02 ### Underwriting operations Evidence, underwriting rules, referrals, and decisions, under the insurer’s authority. 03 ### Claims operations Claim notification, evidence, assessment, and authorized settlement, connected to provider services. 04 ### Insurance financial flows Premiums, commissions, refunds, and indemnity payments, connected to payment services and reconciliation. These capabilities are in development and not included in the currently available module scope. Where to go next ## Explore the foundation. [See the business modules](https://fireflysoftware.io/openplatform/modules/) [Read the architecture](https://fireflysoftware.io/openplatform/architecture/) [Plan the deployment](https://fireflysoftware.io/openplatform/get-started/) [Explore the engineering frameworks](https://fireflysoftware.io/technology/frameworks/) Your first operation ## Bring us one operation. Tell us the process, the volume, and what “done” looks like. We will come back with a scope, a deployment plan, and a proposal. [Book an operations review](https://fireflysoftware.io/contact/) [Request a demo](https://fireflysoftware.io/contact/?request=demo)