Public Protocol
Platform

Chapter 13, Digital

Digital infrastructure

Your own machines, services and records.

Chapter
13
Group
Digital
Elements
8
State
8 open, 0 drafted, 0 reviewed, 0 proven
Library
6 external, 2 Public Protocol, 2 from founding partners
Safety
Up to S1
Release
16 November 2026

Purpose

Run one's own computing, services and records.

Principles

This chapter is written against the eight principles, the four checks and the reference community at two scales.

Open for contributions Principles particular to this domain. Add to it

Framework

The framework is the method that ties the chapter's elements together: the questions a community answers in order, the quantities to establish, the decision points and the checks.

Open for contributions The framework for digital infrastructure. Add to it

Elements

An element is one thing a community needs to have worked out. Each has a sheet in the same form. The figures are the resources that support the element at each stage.

Along the arc

What the library holds for this domain at each stage.

1 Learn

Understand

2 Design

Size and choose

3 Build

Build or obtain

4 Deploy

Install, run and measure

Resources

10 entries in the library for this domain. Those marked External are the work of others, listed by link, and carry the label “External resource. Not made or verified by Public Protocol”.

ResourceTypeOriginMaturitySafetyLicence, as stated at its source
Digital Public Goods StandardStandardExternalNot assessedS0Not read on the date checked
ForgejoToolExternalNot assessedS0Described as "free software" at the source; site CC BY-SA 4.0
NextcloudToolExternalEstablishedS1Described as "100% open source" at the source; the licence is not named on the page opened
OpenMRSToolExternalEstablishedS1Described as "open and free" at the source; the licence is not named on the page opened
WebLLMRepositoryExternalNot assessedS0Apache-2.0
YunoHostToolExternalNot assessedS1Not stated on the page opened
CompisleSystemFounding partnerNot assessedS2Not stated by the maker
Furcate OSSystemFounding partnerNot assessedS1Apache-2.0 for anything that makes a trust claim, as its site states
Public CloudSystemPublic ProtocolNot assessedS1AGPL-3.0
Public OSSystemPublic ProtocolNot assessedS1AGPL-3.0-only

Depends on, and needed by

This chapter needs

Machines need power, links and hardware.

The whole dependency drawing

Settled and open

What is settled is recorded here as elements are reviewed. The standing questions for every element of this chapter: who can afford this; who does the work; who decides.

Wanted for this chapter

  • Identity and keys
  • Backup
  • Local AI models

Contribute to this chapter

Safety and legal cautions

Data loss, privacy and security are the hazards.

General cautions, not advice on any person's case. The law of the place applies.

Who in the ecosystem works on this

  • Public Cloud, made by Public Protocol. A cloud that belongs to the people who use it. Public Cloud gives a person or a community a cloud of their own, private to them, with conversations, mail, documents, files, a calendar, contacts and tasks in one place.
  • Public OS, made by Public Protocol. The way a person or a community gets a machine that runs Public Cloud: a server that holds their cloud, and a desktop on which its applications are at home.
  • Tenzro, founding partner. The network between deployments and the settlement layers: a way for machines to exchange and settle work.
  • Furcate, founding partner. The cloud operating system: Furcate OS, an open, native Linux operating system for computing infrastructure.
  • Compisle, founding partner. Designs and develops modular physical infrastructure for computing, energy, living and research; uses the Public Protocol blueprint and frameworks.
  • Praecise, founding partner. Commercial managed services for those who want a deployment run for them, and a contributor of open-source tools.
  • Living Worlds Lab, founding partner. Digital twins and simulations, and training for machines and robotics.

What a founding partner offers passes the same review and carries the same labels as anything else.

Pathways through this chapter