Community Projects Overview
This is the beginning of the community projects section for self-hosting Agenta.
Community projects are first-class repository topics for self-hosting and deployment surfaces that are tracked explicitly.
They exist to make three things clear:
- what setup a guide or contribution is about
- who is expected to maintain it
- what level of support users should expect
This section will be populated as community projects develop. For now, this page defines the dimensions used across community projects and links each taxonomy value to the matching GitHub issues and discussions views.
How To Read A Community Project
Each community project is described with a small set of dimensions:
| Dimension | Label family | Meaning |
|---|---|---|
| Provider | provider/* | Who provides the infrastructure or hosting environment |
| Platform | platform/* | The deployment target or environment shape |
| Runtime | runtime/* | How Agenta is run or orchestrated |
| OLAP | olap/* | The storage / analytics backend classification used by the setup |
| Maintenance | maintenance/* | Who is expected to keep the setup working |
| Support | support/* | The level of promise made to users |
Provider Labels
The provider/* dimension describes where the infrastructure comes from.
| Label | Issues | Discussions |
|---|---|---|
provider/local | Issues | Discussions |
provider/railway | Issues | Discussions |
provider/hetzner | Issues | Discussions |
provider/aws | Issues | Discussions |
provider/azure | Issues | Discussions |
provider/gcp | Issues | Discussions |
Platform Labels
The platform/* dimension describes the shape of the deployment target.
| Label | Issues | Discussions |
|---|---|---|
platform/local | Issues | Discussions |
platform/vps | Issues | Discussions |
platform/eks | Issues | Discussions |
platform/aks | Issues | Discussions |
platform/gke | Issues | Discussions |
Runtime Labels
The runtime/* dimension describes how Agenta is started and orchestrated.
| Label | Issues | Discussions |
|---|---|---|
runtime/docker-compose | Issues | Discussions |
runtime/kubernetes | Issues | Discussions |
OLAP Labels
The olap/* dimension classifies the storage / analytics backend used by the setup.
| Label | Issues | Discussions |
|---|---|---|
olap/local | Issues | Discussions |
olap/postgres | Issues | Discussions |
olap/clickhouse | Issues | Discussions |
olap/tigerdata | Issues | Discussions |
Maintenance Labels
The maintenance/* dimension answers who is expected to do the work.
| Label | Issues | Discussions |
|---|---|---|
maintenance/internal | Issues | Discussions |
maintenance/community | Issues | Discussions |
Use this to answer:
- who is expected to fix issues
- who is expected to keep the setup current
- who is expected to drive follow-up work
Support Labels
The support/* dimension answers what level of promise the repository makes to users.
| Label | Issues | Discussions |
|---|---|---|
support/official | Issues | Discussions |
support/experimental | Issues | Discussions |
Use this to answer:
- whether users should rely on the setup as a recommended path
- whether the setup is best-effort or actively backed
- whether the surface should be treated as stable or exploratory
Current Source Of Truth
The repository-level matrix for current community projects lives in docs/community-topics.md in the repository.
When a setup becomes a first-class community project, update:
- the topic matrix
- the GitHub labels
- the relevant docs and ownership metadata
What Comes Next
This page is intentionally acting as the initial directory for community projects.
As community projects develop, this section can grow with project-specific pages, contribution guidance, and topic-specific documentation linked from the taxonomy above.