# Kolo docs > Documentation for Kolo, a peer-to-peer stack in Go: guides, concepts and the API of every library. ## Start - [Introduction](https://docs.kolo.ciranda.dev/index.md): Kolo is a set of small Go libraries for building peer-to-peer apps. Peers find each other, connect directly and keep a signed log, with no server in between. - [Get started](https://docs.kolo.ciranda.dev/start/get-started.md): Run a bootstrap node and two chat peers on one machine. The peers find each other by topic and talk directly. - [FAQ](https://docs.kolo.ciranda.dev/faq.md): Short answers to common questions about Kolo, with a link to the page that shows each one. What is not built yet is on the Roadmap. ## Build - [Step 1: Build a chat in your terminal](https://docs.kolo.ciranda.dev/build/terminal-chat.md): A step-by-step tutorial. Two peers on your computer find each other through a bootstrap node and chat directly, with no server in between. - [Step 2: Build a desktop chat](https://docs.kolo.ciranda.dev/build/desktop-chat.md): A step-by-step tutorial. Fill in the Kolo part of a ready-made desktop window: two instances find each other through a bootstrap node and chat directly, with no server in between. - [Step 3: Keep messages for offline peers](https://docs.kolo.ciranda.dev/build/offline-messages.md): Keep messages for people who are offline: every message is also written to your signed log and kept by a pin, which cannot read it, until the other peer comes back. - [Step 4: Invite someone to a group](https://docs.kolo.ciranda.dev/build/invite-to-group.md): Add invites to the chat: the owner creates an invite with an expiry, a number of uses and approval, and the other person joins with the code and receives the conversation key through it. - [Step 5: Profiles and rooms](https://docs.kolo.ciranda.dev/build/profiles-and-rooms.md): Give the group names and rooms: every member publishes a profile, and the owner keeps the room and member lists, all stored with kolo-kv and synced to the other members and the pin. - [Step 6: Several conversations in one app](https://docs.kolo.ciranda.dev/build/several-conversations.md): Keep several conversations in one window: each one in a folder of its own, with its own key, kolo-id, logs, pin and invites, and one service that routes the window's calls. - [Step 7: Agree on members and rooms with kolo-braid](https://docs.kolo.ciranda.dev/build/shared-state.md): Keep the member list and the room list of each conversation in a kolo-braid, so every member ends with the same lists, admins approve and remove members, and the chat talks only to the people on the agreed list. - [Step 8: Use the public network](https://docs.kolo.ciranda.dev/build/public-network.md): Start the chat on the public network by default, so people on different networks find each other with no setup, keep your own network with -bootstrap, and say what to do when no entry node answers. - [Run your own infrastructure](https://docs.kolo.ciranda.dev/build/own-infrastructure.md): Copy-paste commands to run your own entry node, relay and pin, and to point the Kolo examples at them. There is no public relay and no public pin. - [Run a pinning peer on a VPS](https://docs.kolo.ciranda.dev/build/pinning-peer-vps.md): A step-by-step guide. Build the kolo-pin binary, run it on a Linux server with systemd, and pin a log to it from an owner's computer. - [Monitoring a pinning peer](https://docs.kolo.ciranda.dev/build/monitoring-pinning-peer.md): Read the metrics of a kolo-pin pinning peer with Prometheus, keep the endpoint private, and get an alert before its storage fills up. - [Choosing pinning peers](https://docs.kolo.ciranda.dev/build/choosing-pinning-peers.md): Keep each log on two or more pinning peers in different places, picked the same way by every device. - [Invite someone to a group, in a terminal program](https://docs.kolo.ciranda.dev/build/invite-terminal.md): A step-by-step guide. A member makes an invite code, someone joins with it, and the member approves, denies or revokes. - [Share files between two terminals](https://docs.kolo.ciranda.dev/build/share-files.md): A step-by-step tutorial. One terminal shares a file with kolo-blobs, the other receives it with a share code and checks every byte; then the same for a folder and its versions with kolo-files. - [Build a shared document in two terminals](https://docs.kolo.ciranda.dev/build/shared-doc.md): A step-by-step guide. Two people write one document with kolo-braid, see the same lines in the same order, find out what settled and tentative mean, and remove a writer. - [Build a video call](https://docs.kolo.ciranda.dev/build/video-call.md): A step-by-step tutorial. Fill in the Kolo part of a ready-made desktop window: cameras and microphones, an invite, a relay that the host runs, and group keys that keep audio, video and names from the relay. ## Built with Kolo - [Built with Kolo](https://docs.kolo.ciranda.dev/built-with-kolo.md): Example programs written by the Kolo team to show the libraries working together. They are demonstrations, not production software and not products. ## Concepts - [Concepts](https://docs.kolo.ciranda.dev/concepts.md): The few ideas Kolo is built on, one short page each. - [Peers](https://docs.kolo.ciranda.dev/concepts/peers.md): A peer is an Ed25519 key. Two peers are the same peer when their public keys are equal. - [Topics](https://docs.kolo.ciranda.dev/concepts/topics.md): A topic is a 32-byte value. Peers announce the topics they are on and look up the others, with no directory server. - [Logs](https://docs.kolo.ciranda.dev/concepts/logs.md): A log is a list of entries that only grows. Its owner signs it, and anyone with the owner's public key can check it. - [Replicas](https://docs.kolo.ciranda.dev/concepts/replicas.md): A replica is a checked, read-only copy of another peer's log. It only grows after every new piece verifies. - [Deletion](https://docs.kolo.ciranda.dev/concepts/deletion.md): Kolo deletes an entry by destroying its key. Deletion is best effort, and this page says exactly what that means. - [Relay](https://docs.kolo.ciranda.dev/concepts/relay.md): When two peers cannot reach each other, a relay you run can join them. It is off unless you turn it on. ## Libraries - [Libraries](https://docs.kolo.ciranda.dev/libraries.md): Small Go libraries. Each does one job and has its own page with install steps, a quick start, the API and its limits. - [kolo-id](https://docs.kolo.ciranda.dev/libraries/kolo-id.md): Ed25519 node identity for Kolo, with signing, verification, a private key file, a 24-word recovery phrase and device certificates. - [kolo-codec](https://docs.kolo.ciranda.dev/libraries/kolo-codec.md): Canonical binary encoding for Kolo, where every value has exactly one valid encoding. - [kolo-log](https://docs.kolo.ciranda.dev/libraries/kolo-log.md): A signed append-only log that any peer can check and its owner can still delete from. - [kolo-store](https://docs.kolo.ciranda.dev/libraries/kolo-store.md): Persistent storage for Kolo logs and read-only replicas on one machine. - [kolo-blobs](https://docs.kolo.ciranda.dev/libraries/kolo-blobs.md): Encrypted, content-addressed file storage. Store a file of any size, read any range of it, and keep it on pinning peers that cannot read it. - [kolo-files](https://docs.kolo.ciranda.dev/libraries/kolo-files.md): An encrypted tree of files and folders with its whole history. Check out any earlier version, compare two, and keep only the files a device needs. - [kolo-sync](https://docs.kolo.ciranda.dev/libraries/kolo-sync.md): Copies a signed kolo-log log from one peer to another, pull only, or fetches some of its entries without a replica. - [kolo-kv](https://docs.kolo.ciranda.dev/libraries/kolo-kv.md): An ordered key-value store with one writer, kept in a signed Kolo log. - [kolo-braid](https://docs.kolo.ciranda.dev/libraries/kolo-braid.md): The signed strands of several members merged into one deterministic order, which an apply function you write turns into a view. - [kolo-transport](https://docs.kolo.ciranda.dev/libraries/kolo-transport.md): One QUIC connection between two Kolo peers, with multiplexed streams and hard limits. - [kolo-secure](https://docs.kolo.ciranda.dev/libraries/kolo-secure.md): An encrypted, authenticated channel between two Kolo peers, bound to their kolo-id keys. - [kolo-dht](https://docs.kolo.ciranda.dev/libraries/kolo-dht.md): Find peers by topic without a central server, and connect to them through NATs. - [kolo-swarm](https://docs.kolo.ciranda.dev/libraries/kolo-swarm.md): Join a topic and keep connections to the peers found on it. - [kolo-relay](https://docs.kolo.ciranda.dev/libraries/kolo-relay.md): An optional, self-hosted relay that joins two Kolo peers that cannot connect directly. - [kolo-invite](https://docs.kolo.ciranda.dev/libraries/kolo-invite.md): Invite codes for a group. A member creates one, someone joins with it, and the member approves or denies. - [kolo-moq](https://docs.kolo.ciranda.dev/libraries/kolo-moq.md): Publish, subscribe to and relay live tracks over Kolo connections, with MoQ Transport draft 22. A relay shares one upstream subscription among many subscribers, and the secobj package seals objects so a relay forwards them without reading them. - [kolo-media](https://docs.kolo.ciranda.dev/libraries/kolo-media.md): A catalog, LOC packaging, a clock, playout and audio and video sync for broadcasts over kolo-moq. It works on encoded frames and is pure Go. A broadcast can be sealed so a kolo-moq relay forwards it without reading it. - [kolo-audio](https://docs.kolo.ciranda.dev/libraries/kolo-audio.md): Audio devices, capture and playback as 16-bit PCM, resampling, mixing and Opus. No cgo, no C compiler and nothing to install. - [kolo-video](https://docs.kolo.ciranda.dev/libraries/kolo-video.md): Camera capture, I420 frames, VP8 and VP9 with libvpx, and optional H.264 from the operating system's own codec. No cgo, no C compiler and nothing to install. - [kolo-node](https://docs.kolo.ciranda.dev/libraries/kolo-node.md): A bootstrap server for the kolo-dht network, the address new Kolo peers join through. - [kolo-pin](https://docs.kolo.ciranda.dev/libraries/kolo-pin.md): A peer that stores encrypted data for others without being able to read it. ## Reference - [Security](https://docs.kolo.ciranda.dev/reference/security.md): What the Kolo libraries protect, how they do it, and what they leave to you. - [Limits](https://docs.kolo.ciranda.dev/reference/limits.md): Every fixed size, count, timeout and configurable default of the Kolo libraries, one table per library. - [Changelog](https://docs.kolo.ciranda.dev/reference/changelog.md): What changed in each library, newest version first, from each library's CHANGELOG.md. - [Roadmap](https://docs.kolo.ciranda.dev/roadmap.md): What comes next for Kolo: a local bridge, large groups, a web edge, Bluetooth LE between nearby peers, a JavaScript SDK and apps. No dates, and everything is still beta.