Public Cloud

What is inside

Public Cloud, by Public Protocol, is one application for the everyday work of a life or a community. Each part is described here as it is designed, with its state on 16 November 2026 beside it. Where a part is planned and not built, this page says so.

The parts

Conversations

Core built and tested

Private messages between two people or a small group. They are end-to-end encrypted, which means only the people in a conversation can read them: the encryption happens on each person's own device, and the services in between carry only what they cannot open.

No phone number and no email address is asked for. A conversation begins from a username or from a single invitation code. A username is optional, can be changed or dropped at any time, and cannot be looked up in a list: someone has to know it exactly. A person found that way shows their username and nothing more, until they choose to send a contact card.

Everything a person has is kept on their own device as one encrypted file, so closing the application loses nothing.

Not built yet: the interface, and a way for one person's several devices to share history. Members of a group cannot yet compare keys with each other directly.

Communities

Core built and tested

A community is more than a group chat. Anyone can create one. People come in three ways: an administrator adds them, a member invites them, or a link is shared. A link can require approval, expire, admit a set number of people, and be reset. A community can be private, or public with a name of its own to be found by.

Its members, their roles and its rules are signed records that every member's device holds and checks. There are administrators, moderators and members.

Moderation belongs to the community. Where anyone can join by a link, a moderation agent must be present, and it is a member that everyone can see in the member list. It receives what every member receives and nothing else. Today it applies the community's own written rules in the form of a list of refused words and a limit on how fast a member may post. A removal is a signed record naming the rule, and the person removed can appeal once to the community's human moderators. Private conversations are never scanned.

What people should know plainly: removal stops future delivery. It cannot recall what a removed member already holds. Detection of illegal images is not built and waits on legal advice. The agent exists as tested code, not yet as a program a community can start.

Files

Core built and tested

A file is encrypted on the device, under a key of its own, and cut into pieces before it is stored. Whoever stores the pieces cannot open them. Sharing a file means giving someone a link that carries the right to read it, and nobody else has that right.

Storing the pieces on the Tenzro network is written and tested against a stand-in. It has not been checked against a live network. Very large files need more work.

Calendar and contacts

Shared data built and tested

A calendar for yourself and for the groups you belong to, and the people you know with only the details each of them has chosen to show you. Both are shared data that lives on each person's device and merges when devices next reach each other, so they keep working without a connection.

A contact card holds a name, a picture and a line of description. Its owner decides who receives it, can send different cards to different people, and can take one back.

The first version of the calendar shares only the times you are busy with other people, not what you are doing. There is no interface yet.

Tasks and projects

Shared lists built and tested
Projects planned

Shared lists of what needs doing, kept the same way as the calendar: on each device, merged when they meet. A list belongs to a conversation, a group or a community, and each person has a private one.

The planning of larger work, with boards and stages, was added to the plan on 16 November 2026. It is not designed yet.

Docs

Planned, not designed

Documents written together, readable only by the people they are shared with. Added to the plan on 16 November 2026. Nothing of it is designed or built.

Mail

Planned, not designed

Mail at your own address, kept in your own cloud with everything else. This is an intention, not yet a design.

One thing can be said now, because it follows from how mail works everywhere: a message exchanged with an address outside is not private in the way a conversation is. The other side's mail service can read it.

Running a community or a business

Records built and tested
The rest planned

Membership, roles, rules, removals and appeals are kept as records the group holds and can check. That much is built.

Tools for the management side of a group or a small business are intended and not designed.

The assistant

Not built

An assistant you talk to, as one more conversation in the list. By design it runs on a model on your own machine, so nothing it reads leaves the device. A model elsewhere is used only if you turn it on, with a plain statement of what is sent.

It acts through the same steps a person takes: find a message or a file, add a task or an event, draft a reply for you to send. It never sends anything on its own.

The application

Being built

Everything above is reached today from a terminal program. The application people will see is being built for the web and the desktop first. Phones come later.

The same core that runs on the desktop has been compiled for the browser. It has not yet been run there. Search is to be an index kept on the device only.

The application is also being given a design system and templates of its own, so that a deployment can take a community's look and starting structures. Make it your own