The Bitxenia project was born from the need to explore alternative infrastructures for the development and deployment of community-based, distributed, and decentralized applications.

Today, most web applications depend on infrastructure providers such as AWS, Azure, or Google Cloud, which offer agile and scalable solutions for hosting and maintenance. However, this model is not always suitable for community-oriented applications — projects that are created, maintained, and governed collectively. In such cases, decision-making is distributed among participants, oriented toward the common good, and based on collaboration. This structure ensures that the evolution of an application responds directly to the needs of its community.

Community-oriented applications face a distinct set of challenges that traditional infrastructure models fail to address:

• Centralized dependency — relying on third-party providers introduces control, cost, and policy risks.
• Limited autonomy — community projects often lack access to flexible, low-cost hosting environments they can govern collectively.
• Censorship and restrictions — certain projects may be subject to content moderation, access limitations, or regional blocks.
• Economic barriers — many community initiatives operate on volunteer work or donations, making commercial infrastructure unsustainable.
• Value misalignment — principles like openness, transparency, and shared ownership conflict with centralized service models.

As a result, community applications struggle to maintain technical sovereignty — the ability to host, evolve, and sustain themselves independently of commercial providers.

Bitxenia aims to rethink how communities deploy and maintain digital infrastructure. Rather than relying on external hosting, our goal is to empower users to become active participants in the operation of their own applications, distributing both resources and governance.

To achieve this, we explore technologies that embody the original spirit of the Internet — decentralization, collaboration, and openness — through peer-to-peer systems capable of providing reliable and censorship-resistant environments.

To address these challenges, Bitxenia evaluates different decentralized ecosystems capable of replacing or complementing traditional cloud architectures. The focus is placed on two main technological pillars: IPFS and Blockchain.

The InterPlanetary File System (IPFS) is a distributed protocol for storing and sharing data through content addressing rather than location-based references. Files are divided into blocks and identified by unique cryptographic hashes, allowing users to retrieve data directly from peers instead of centralized servers.

This approach provides greater resilience, integrity, and redundancy, since any peer hosting a copy of the content can serve it to others. Complementary projects such as libp2p (peer-to-peer networking layer) and OrbitDB (distributed database built on IPFS) enable the creation of fully decentralized application architectures. Tools like IPNS and ENS allow for dynamic and human-readable content addressing, while IPFS Cluster coordinates collaborative pinning between nodes.

The Blockchain ecosystem — and particularly Ethereum — offers a different but compatible approach to decentralization. While IPFS focuses on distributed file storage, Ethereum is designed for distributed computation through smart contracts: self-executing code deployed on a global, consensus-driven network.

This enables applications to implement features such as on-chain governance, verifiable logic, and token-based incentives. Ethereum’s ecosystem includes complementary technologies like Swarm (decentralized storage network) and ENS (Ethereum Name Service) for naming and addressing resources.

Unlike IPFS, which optimizes for lightweight data distribution, blockchain-based systems emphasize state consistency, traceability, and immutability, making them suitable for cases that require trust and verifiable execution.

The following sections expand on each of the technologies introduced here.

• In IPFS Ecosystem you’ll find a detailed explanation of how decentralized storage and data synchronization were implemented using IPFS, libp2p, and OrbitDB.

• In Blockchain Ecosystem you’ll explore how Ethereum and Swarm enable distributed computation, storage, and name resolution through smart contracts and peer-to-peer coordination.

Together, these components form the foundation of Bitxenia’s experimental infrastructures — two distinct yet complementary approaches to building open, resilient, and community-owned applications.