Most Developers Think Hyperledger = Fabric. I Did Too
When I first started learning Hyperledger, I thought Hyperledger Fabric was the entire ecosystem.
To be fair, that’s what most blockchain discussions seemed to revolve around. Tutorials, courses, certifications, and enterprise blockchain conversations almost always pointed back to Fabric. As a result, I never paid much attention to what existed beyond it.
That changed while I was preparing for the Hyperledger Fabric Certified Practitioner (HFCP) exam and spending more time exploring the Hyperledger landscape. Before then, I had barely heard of projects like Indy, Besu, or Identus.
One discovery genuinely surprised me: Hyperledger includes an Ethereum client.
For a long time, I associated Hyperledger with permissioned enterprise blockchains and Ethereum with public blockchain ecosystems. Learning about Hyperledger Besu challenged that assumption. It made me realize that Hyperledger isn’t a single blockchain framework — it’s an ecosystem of projects solving different problems.
Another project that caught my attention was Hyperledger Identus. I first heard about it when my manager asked me to explore the platform and build a sample demonstration. Until then, I wasn’t even aware that Hyperledger had a project focused on helping organizations adopt decentralized identity solutions more easily.
The deeper I explored, the more I noticed something interesting: most discussions focus heavily on Fabric, while projects like FireFly, Indy, Cacti, and Identus rarely get the same attention.
Yet many of these projects address challenges that are just as important as the blockchain itself — identity management, interoperability, application integration, and communication between distributed systems.
This article is a walkthrough of the Hyperledger ecosystem from the perspective of someone who started with Fabric and gradually discovered there was much more beneath the surface.
The Project Everyone Knows: Hyperledger Fabric
If you’ve worked with enterprise blockchain, chances are Fabric is the first Hyperledger project you’ve encountered.
Fabric has earned that position for good reason. It provides a modular architecture, permissioned networking, smart contracts through chaincode, and privacy mechanisms such as channels and private data collections. Many enterprise blockchain solutions today are built on top of Fabric.
As I learned more about Fabric, I started appreciating that enterprise blockchain is often less about cryptocurrency and more about trust between organizations. Fabric is designed around that reality.
Organizations want to share data without giving up control. They want governance, identity management, and auditability. Fabric addresses those concerns better than many public blockchain platforms.
For a long time, I assumed this was the entire Hyperledger story.
It wasn’t.
Hyperledger Besu: The Project I Didn’t Expect
Besu was probably my biggest surprise.
I had always mentally separated Hyperledger and Ethereum into different categories. Hyperledger meant enterprise blockchains. Ethereum meant public blockchain networks and smart contracts.
Then I discovered Besu.
Besu is an Ethereum client developed within the Hyperledger ecosystem. It supports Ethereum standards, the Ethereum Virtual Machine (EVM), and Solidity smart contracts while also supporting permissioned enterprise deployments.
What surprised me most was that Besu isn’t limited to private consortium networks. The same client can participate in public Ethereum networks or be deployed in permissioned enterprise environments using consensus mechanisms such as QBFT and IBFT 2.0.
That realization changed how I viewed Hyperledger.
Instead of competing with Ethereum, Hyperledger also provides tools that allow organizations to participate in Ethereum-based ecosystems when that makes sense.
For developers, this means understanding Hyperledger doesn’t automatically mean committing to one technology stack. Depending on the business requirements, Fabric and Besu can both be valid choices.
A simple way I think about it today is:
- Fabric focuses on enterprise business networks.
- Besu brings Ethereum compatibility into both public and enterprise environments.
The fact that both exist under the Hyperledger umbrella was something I genuinely didn’t expect.
Hyperledger Indy: Identity as the Core Problem
Most blockchain conversations revolve around transactions, assets, and smart contracts.
Indy approaches a different problem.
Identity.
At first, I struggled to understand why a dedicated identity ledger was necessary. Why not simply store identity information on an existing blockchain?
The more I learned about decentralized identity, the more the value became clear.
Identity systems have unique requirements. They need verifiable credentials, decentralized identifiers (DIDs), privacy controls, and interoperability across organizations.
Indy focuses entirely on those challenges.
This becomes especially relevant in scenarios such as:
- Educational certificates
- Professional credentials
- Government-issued documents
- Digital identity systems
The interesting lesson for me was that blockchain adoption isn’t only about moving assets. In many cases, establishing trust in identities is the bigger challenge.
Hyperledger Identus: My Introduction to SSI
Unlike Indy, which I discovered while studying the ecosystem, my introduction to Identus came from actual work.
My manager assigned me a task to explore Hyperledger Identus and build a small demonstration application.
That was the first time I had heard of the project.
As I started reading through the documentation and architecture, I realized Identus isn’t trying to be another blockchain platform. Its goal is to simplify the adoption of decentralized identity.
Many organizations understand the benefits of Self-Sovereign Identity (SSI) but struggle with implementation complexity.
Identus provides building blocks that make that journey easier.
One interesting detail I discovered is that Identus wasn’t built from scratch as a brand-new Hyperledger project. It originated as Atala PRISM, an SSI platform developed by IOG before being contributed to Hyperledger. That explained why the project already had mature SDKs, documentation, and a growing ecosystem despite being relatively new to the Hyperledger landscape.
Get Neethu M’s stories in your inbox
Join Medium for free to get updates from this writer.
What stood out to me was the developer experience. The platform includes SDKs for different environments and supports modern identity standards such as DIDs, verifiable credentials, DIDComm v2, and AnonCreds.
Instead of forcing developers to build everything from scratch, it provides practical tools for building identity-driven applications.
Working through a sample implementation helped me appreciate how much effort is required to move decentralized identity from theory into production-ready systems.
Hyperledger FireFly: The Project Nobody Talks AboutAmong all the projects I explored, FireFly might be one of the most overlooked.
Most discussions I encounter focus on Fabric. FireFly rarely comes up.
That’s unfortunate because it addresses a challenge many teams eventually face.
Building a blockchain application isn’t only about interacting with a blockchain.
Applications also need:
- APIs
- Event management
- Data exchange
- Messaging systems
- Integration with existing services
FireFly acts as a layer that helps coordinate these interactions.
The more enterprise systems I looked at, the more I realized that blockchain is usually just one component in a much larger architecture.
FireFly acknowledges that reality.
Another detail I found interesting is that FireFly isn’t tied to a specific blockchain. Whether the underlying network is Fabric, Besu, or another supported platform, FireFly focuses on simplifying application integration rather than promoting a particular ledger.
It focuses on helping developers build production-ready applications instead of spending excessive time wiring together infrastructure components.
Hyperledger Cacti: Solving the Interoperability Problem
One of the recurring themes in distributed systems is interoperability.
Organizations rarely operate on a single platform.
The same is true in blockchain.
Different networks serve different purposes, and sooner or later there is a need for communication between them.
This is where Cacti becomes interesting.
Rather than building another ledger, it focuses on helping systems work across multiple blockchains.
When I first encountered Cacti, it reminded me of a broader lesson in software engineering:
Building a system is only half the challenge.
Making systems work together is often the harder part.
Hyperledger Iroha: Simplicity Has Value
Modern blockchain platforms can become incredibly complex.
Fabric, Ethereum, and other enterprise platforms offer enormous flexibility, but that flexibility often comes with additional operational overhead.
Iroha takes a different approach.
Its design emphasizes simplicity and ease of integration.
It is particularly suitable for scenarios such as IoT systems, lightweight asset management solutions, and environments where a simpler blockchain architecture is preferred.
Exploring Iroha reminded me that not every project needs the most feature-rich platform available.
Sometimes the best solution is the one developers can understand, integrate, and maintain effectively.
It’s worth noting that Iroha 2 represents a significant evolution of the platform, introducing a more advanced architecture and smart contract capabilities while still maintaining the project’s focus on usability and developer experience.
Looking at the Ecosystem Differently
One of the biggest lessons I took away from this exploration is that Hyperledger is not organized around a single idea.
It’s organized around solving different trust-related problems.
Some projects focus on ledgers.
Others focus on identity.
Some focus on application integration.
Others focus on interoperability.
Once I stopped viewing Hyperledger as “the Fabric ecosystem,” the project landscape started making much more sense.
Each project exists because a different problem needed solving.
Final Thoughts
If you’re learning enterprise blockchain today, understanding Fabric is still important.
It’s one of the most influential blockchain platforms in enterprise environments and remains a valuable technology to learn.
But Fabric is only part of the story.
Exploring Besu helped me understand Hyperledger’s connection to Ethereum. Indy and Identus showed me how important decentralized identity is becoming. FireFly highlighted the challenges of application integration, while Cacti demonstrated why interoperability matters.
The more I learned, the more I realized that Hyperledger is not a blockchain platform.
It’s an ecosystem.
And understanding that ecosystem gives you a much clearer picture of where enterprise distributed systems are heading.
