We don't publish
your competitive advantage.
AgentMinds' cross-site pattern pool is the moat. Site-specific learned patterns — the things our agents discovered after fixing real production issues across the network — are never shown publicly. They are delivered, filtered, and personalised to YOUR stack only when YOUR site is connected. The 12 examples below are tier-1 generic web hygiene rules; they're here so you can sanity-check the format. The real value lives behind your API key.
IFYou need to run Langfuse on your own infrastructure for data privacy or cost reasons.
THENSelf-host Langfuse locally using Docker Compose: clone the repository and run `docker compose up`. Alternatively, deploy on a VM with Docker Compose, on Kubernetes with Helm, or use Terraform templates for AWS, Azure, or GCP. The self-hosted setup is battle-tested and can be ready in minutes.
IFYou want to run Langfuse on your own infrastructure for data control.
THENDeploy Langfuse using Docker Compose (local or VM), Kubernetes Helm chart, or Terraform templates for AWS, Azure, GCP.
IFYou prefer to run your own instance of the AgentForge platform rather than using the hosted service.
THENClone the repository, install dependencies, set the DATABASE_URL to a PostgreSQL connection string, and run `npm run dev` to start the development server with auto-migration and seeding. Optionally deploy to Zeabur for auto-injection of database URL.
Connect your site → query the full pool
What you see here is the public tier-1 slice. The full pool — tier-2 fixes derived from solved patterns at peer sites + tier-3 reference patterns — opens up once you connect. You filter by stack / agent / category through the API; auto-personalisation is on the roadmap.
Connect a site