Skip to main content

Community Projects

If you want to help Agenta run well in more environments, community projects are the place to contribute.

Community projects give deployment work a clear home. They help contributors understand:

  • which setup or environment the work is about
  • who is expected to maintain it
  • what level of support users should expect

Where Contributors Can Help Today

The source of truth for the current matrix lives in docs/community-topics.md in the repository.

Use the official OSS quick start as the reference deployment surface. Community projects extend Agenta to additional environments beyond that baseline.

SurfaceRoleSupport expectationStart here
Local OSS with Docker ComposeOfficial baseline and reference point for new deployment worksupport/officialQuick Start
Railway OSSCurrent community-managed deployment surface for Agenta OSSsupport/experimentalDeploy on Railway

How To Contribute

  1. Pick a tracked deployment surface and read the matching guide before changing scripts or docs.
  2. Use the label families in the appendix to find the right GitHub issues and discussions for that setup.
  3. When you improve a tracked surface, update the docs, scripts, and ownership or support metadata together.
  4. If you want to propose a new deployment surface, open an issue or discussion first and describe the provider, platform, runtime, OLAP backend, maintenance owner, and support level.

When A Deployment Surface Becomes A Community Project

Update these items in the same change:

  • docs/community-topics.md
  • .github/.labels.yml
  • CODEOWNERS
  • the relevant setup docs and README files

Appendix: Label Taxonomy

Each tracked deployment surface is described with a small set of dimensions:

DimensionLabel familyMeaning
Providerprovider/*Who provides the infrastructure or hosting environment
Platformplatform/*The deployment target or environment shape
Runtimeruntime/*How Agenta is run or orchestrated
OLAPolap/*The storage or analytics backend classification used by the setup
Maintenancemaintenance/*Who is expected to keep the setup working
Supportsupport/*The level of promise made to users

Use maintenance/* to understand who is expected to fix and update a setup. Use support/* to understand whether a deployment surface is official or best-effort.

Provider Labels

LabelIssuesDiscussions
provider/localIssuesDiscussions
provider/railwayIssuesDiscussions
provider/hetznerIssuesDiscussions
provider/awsIssuesDiscussions
provider/azureIssuesDiscussions
provider/gcpIssuesDiscussions

Platform Labels

LabelIssuesDiscussions
platform/localIssuesDiscussions
platform/vpsIssuesDiscussions
platform/k3sIssuesDiscussions
platform/eksIssuesDiscussions
platform/aksIssuesDiscussions
platform/gkeIssuesDiscussions

Runtime Labels

LabelIssuesDiscussions
runtime/docker-composeIssuesDiscussions
runtime/kubernetesIssuesDiscussions

OLAP Labels

LabelIssuesDiscussions
olap/localIssuesDiscussions
olap/postgresIssuesDiscussions
olap/clickhouseIssuesDiscussions
olap/tigerdataIssuesDiscussions

Maintenance Labels

LabelIssuesDiscussions
maintenance/internalIssuesDiscussions
maintenance/communityIssuesDiscussions

Support Labels

LabelIssuesDiscussions
support/officialIssuesDiscussions
support/experimentalIssuesDiscussions