Remove the maintainer callout and star history chart from the README while keeping translated copies aligned.
28 lines
1.4 KiB
Markdown
28 lines
1.4 KiB
Markdown
---
|
|
title: Related projects
|
|
description: The official Paseo relay and community-built tools and integrations.
|
|
nav: Related projects
|
|
order: 7
|
|
category: Getting started
|
|
---
|
|
|
|
# Related projects
|
|
|
|
## 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).
|
|
|
|
- **[paseo-vscode](https://marketplace.visualstudio.com/items?itemName=hinnes.paseo-vscode)**, a VS Code extension.
|
|
|
|
## Add your project
|
|
|
|
Built something for Paseo, a relay, a deployment recipe, an integration, a client? Open a pull request or an issue on [GitHub](https://github.com/getpaseo/paseo) to get it listed here.
|