We run defined banking and insurance operations with AI agents and software. Each service has agreed inputs, acceptance criteria, service levels, and a clear owner for exceptions. Your institution keeps its policies and regulated decision authority.
This organization hosts the public business modules behind Firefly OpenPlatform. Our application frameworks and developer tools live in Firefly Framework.
Website · OpenPlatform · Services · Discuss an operation
Firefly OpenPlatform combines business modules with your own services and existing systems through APIs and events. Use the capabilities that fit the operation, keep the systems that already work, and extend the parts your team owns.
Conceptual composition. The service design defines the modules, integrations, and responsibilities for each implementation.
The public modules cover customers, products, agreements, accounts, payments, lending, insurance, and shared services. Insurance cores record policies, underwriting, claims, and financial flows. Domain and experience services for insurance are not published yet. The platform overview explains that boundary.
| Business area | Start with these repositories |
|---|---|
| Customers and onboarding | Customer records, customer orchestration, onboarding journeys |
| Products and agreements | Product definitions, product catalog, contracts |
| Accounts and financial records | Accounts, ledger, general ledger |
| Payments and cards | Payments, cards, payment rails, payment providers |
| Lending | Origination, servicing, collections |
| Shared services | Documents, notifications, user management |
Browse the capability catalog for the wider portfolio, or read the architecture to understand the service boundaries.
Each service delivers a unit of work your team can accept and measure.
| Service | Unit of work |
|---|---|
| CreditOS | An accepted credit file |
| ServicingOS | An active loan account, serviced for the month |
| CollectionsOS | An account under management |
| UnderwritingOS | A complete submission, ready for your underwriter |
| PolicyOS | A completed policy transaction |
| ClaimsOS | A completed claims stage |
| OnboardingOS | A completed onboarding or refresh case |
| ReconcileOS | A closed reconciliation cycle |
| FinancialCrimeOS | An accepted investigation |
| RiskOS | A completed close or model cycle |
These are managed services, with scope, coverage, integrations, and service levels agreed for each engagement. Open-source components retain their own licenses. AI works within approved limits; people with delegated authority handle significant or out-of-limit decisions. Read how we operate and service levels and control.
For an operational engagement, begin with an operations review. We map the work, agree a Service Blueprint, deploy against acceptance criteria, and then run the service. Our advisory helps teams decide what to keep, delegate, or rebuild.
For engineering, choose a repository from the catalog, read its setup instructions and license, and evaluate the dependencies and maturity for your use case. The deployment guide explains what a Firefly operation needs around the code. Report bugs and propose changes in the relevant repository; follow its contribution and security guidance.
Firefly Framework provides application frameworks for Java, Python, PHP, Rust, and .NET, alongside Forge for software delivery, Agentic for AI applications, and Weave for business processes. Firefly Software builds its services on this foundation.
Explore the ecosystem · Read our perspectives · About Firefly
The Firefly name and visual identity belong to Firefly Software Solutions Inc. Each repository defines its own code license.