What each part of Firefly does.

We commit to the results of Firefly services and reuse the same open technology across them. Each part keeps its own responsibilities and licenses.

How the ecosystem fits together

The company

Firefly Software

The commercial company responsible for its client contracts, delivery, and operating commitments.

Meet the company
The service portfolio

Firefly services

The portfolio of services customers scope and purchase, supported by named OS applications.

Explore our services
The applications

OS applications

The service-specific workspaces, workflows, and commercial capabilities used to deliver and oversee an operation.

The composable platform

Firefly OpenPlatform

Reusable open business capabilities selected for the service and connected to existing systems.

Explore Firefly OpenPlatform
The frameworks

Firefly Framework ecosystem

Firefly Framework · pyfly · Firefly Agentic · Firefly Weave

The engineering foundations for applications, integrations, AI tasks, and workflow coordination.

The family includes jafly for Java, pyfly for Python, larafly for PHP, rsfly for Rust, and netfly for .NET. Each project has its own scope and release lifecycle.

Explore the engineering frameworks
The open-source foundation

Firefly Software Foundation

The nonprofit organization that develops and maintains the open-source projects.

Meet the foundation

Open-source code and commercial terms are separate.

Open-source repositories keep their own licenses. Commercial applications, delivery, client configuration, and intellectual property are set in the agreement.

The service is the commercial starting point

Choose the operation and the result first. The architecture then identifies the applications, components, integrations, and AI agents needed to deliver it.

Explore our services

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.