Skip to main content
note

Current status: protocol specifications (draft). Runtimes are planned deliverables — not yet available.

What is Faberio?

Faberio is an open platform for creating distributed applications quickly and simply. Applications share state through an open protocol rather than a vendor-controlled backend.

A Faberio network combines participants' personal devices — smartphones, tablets, laptops, and personal computers — with optional always-on servers operated by users or independent operators in a peer-to-peer, decentralised network. Always-on nodes help updates propagate faster, but they are not required.

This architecture does not depend on centralized cloud platforms. Data replicates in the background across participating nodes — no single vendor owns the hosting layer or holds custody of the data.

The platform is built on the Faberio Protocol and a set of Faberio Runtimes — execution environments for different technology stacks, including Linux servers, containers, and Flutter on mobile, with more to follow. All runtimes implement the same protocol and can join the same network.

Each Faberio Runtime hosts applications and provides platform services: node identity, node discovery, secure connectivity between nodes, a distributed database, distributed file storage, and access control over data replicated between nodes. Developers can focus on application logic instead of rebuilding distributed infrastructure for every product.

Faberio is infrastructure, not a ready-to-use distributed application. See Application Examples for representative categories, including Federated Community Hub, Local Civic Platform, Resilient Emergency Collaboration, and other business applications.


Why Faberio Exists

Much of today's software is delivered as vertical SaaS: one vendor provides the application, holds the data, and runs the hosting for an entire product category.

Community platforms and business applications are common examples. The user experience is familiar, but data custody, pricing, export, and long-term availability remain under vendor control.

Without a shared platform, teams building distributed applications must repeatedly solve the same problems:

  • Replication and state synchronisation
  • Peer and service discovery
  • Secure communication between nodes
  • Distributed messaging and remote procedure calls
  • Identity management
  • Distributed database and file storage

Faberio moves these concerns into the platform layer. The same product categories — Federated Community Hub, Local Civic Platform, Resilient Emergency Collaboration, and other business applications — can run on user devices and operator-controlled infrastructure, with replication and identity built into the Runtime instead of bundled into a closed SaaS stack.

The platform is language-independent. Official SDKs and an open protocol specification let multiple runtime implementations interoperate across heterogeneous hosting environments.


Contact

Source: github.com/faberio-platform/faberio-docs