puter/paseo
1
0
Fork 0
mirror of https://github.com/getpaseo/paseo.git synced 2026-07-29 12:01:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(relay): point readers to the official service

Browse Source 
Remove the maintainer callout and star history chart from the README while keeping translated copies aligned.
This commit is contained in:
Mohamed Boudra
2026-07-26 20:46:06 +02:00
parent 72c7d3fe3e
commit fe28850fad
8 changed files with 27 additions and 62 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
public-docs/community.md
View File

@@ -1,21 +1,25 @@
---
title: Community projects
description: Community-built tools and integrations for Paseo, including self-hosted Docker builds and an alternative relay.
nav: Community
title: Related projects
description: The official Paseo relay and community-built tools and integrations.
nav: Related projects
order: 7
category: Getting started
---
# Community projects
# Related projects
Projects built by the Paseo community. These **aren't official Paseo projects** and aren't covered by Paseo's support, but they're useful starting points, especially for self-hosting. Review the code before running anything that touches your machine or your agents.
## Official relay
**[getpaseo/paseo-relay](https://github.com/getpaseo/paseo-relay)** is Paseo's official distributed relay server, written in Elixir. It powers hosted remote access and can also be self-hosted. For how the relay fits into Paseo's connection model, see [Security](/docs/security).
## Community projects
The projects below are built by the Paseo community. They **aren't official Paseo projects** and aren't covered by Paseo's support, but they're useful starting points, especially for self-hosting. Review the code before running anything that touches your machine or your agents.
## Self-hosting
- **[blockfeed/paseo-selfhosted](https://github.com/blockfeed/paseo-selfhosted)**, a Docker build that runs the Paseo web UI connected to a self-hosted local daemon. A good reference if you want a containerized setup. For the built-in way to serve the UI from the daemon, see [Self-hosting the web UI](/docs/web-ui).
- **[zenghongtu/paseo-relay](https://github.com/zenghongtu/paseo-relay)**, a lightweight self-hosted relay server for Paseo, written in Go. Run your own relay instead of the hosted one for fully self-hosted remote access. For how the relay fits into Paseo's connection model, see [Security](/docs/security).
- **[paseo-vscode](https://marketplace.visualstudio.com/items?itemName=hinnes.paseo-vscode)**, a VS Code extension.
## Add your project

2
public-docs/security.md
View File

@@ -23,7 +23,7 @@ Clients connect to the daemon over WebSocket. There are two ways to establish th
## Relay connections (recommended)
The relay is the simplest way to connect from your phone. It requires no VPN setup, no port forwarding, and no firewall configuration. The daemon can stay bound to localhost or a socket file, it connects _outbound_ to the relay, and your phone meets it there.
The relay is the simplest way to connect from your phone. It requires no VPN setup, no port forwarding, and no firewall configuration. The daemon can stay bound to localhost or a socket file, it connects _outbound_ to the relay, and your phone meets it there. The official relay server is the open-source Elixir service at [getpaseo/paseo-relay](https://github.com/getpaseo/paseo-relay).
> **The relay is designed to be untrusted.** All traffic between your phone and daemon is end-to-end encrypted. The relay server cannot read your messages, see your code, or modify traffic without detection. Even if the relay is compromised, your data remains protected.