Reuse business capabilities
Use the customer, agreement, payment, and lending modules that fit.
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.
Your teams can inspect the code.Scroll to explore
The foundation
What the platform gives a service.
Connect to existing systems
Explicit interfaces to your core, policy, claims, and finance systems.
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 modulesYour own services and modelsOther 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.
- 01
Collect the application
The channel captures the request and onboarding data.
- Channel
- Firefly modules
- 02
Coordinate the opening
A domain service links agreement, holder, and account.
- Process and decision
- Firefly modules
- 03
Create the records
Core modules record the account and its first entries.
- Firefly modules
- 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.
- 01
Serve the customer or agent
Party details, distributor access, and product data, together.
- Channel
- Firefly modules
- 02
Prepare the application
Collect the evidence the insurer’s review needs.
- Process and decision
- Firefly modules
- 03
Connect the insurer
Send the application to its rating, underwriting and policy systems.
- Firefly modules
- Third party, behind an adapter
- 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.
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.
Dashed outlines are in development; solid pieces are available today.
Policy lifecycle
Product, party, and agreement foundations, extended to policies and renewals.
Underwriting operations
Evidence, underwriting rules, referrals, and decisions, under the insurer’s authority.
Claims operations
Claim notification, evidence, assessment, and authorized settlement, connected to provider services.
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.
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.