Catalog

Every row has an evidence path.

Only tools with deployed evidence in the IdeaPlaces repos are listed. If it is not in this table, it is not yet orchestrated. The catalog grows as new integrations land.

CategoryToolPatternEvidence path
Cloud & InfrastructureAzureTerraform azurerm providerideaplaces-devops/infrastructure/terraform/azure/
Cloud & InfrastructureCloudflareTerraform cloudflare providerideaplaces-devops/.../shared/cloudflare.tf
Identity & WorkspaceGoogle WorkspaceTerraform googleworkspace providerideaplaces-devops/google-workspace/
Source ControlGitHubTerraform github provider, repos + branches as codeideaplaces-devops/github/main.tf
SecretsAzure Key VaultTerraform-declared, app secrets vaultedideaplaces-devops/infrastructure/terraform/azure/
CI/CDGitHub ActionsPipelines per repo, failure notifications to Discordper-repo .github/workflows/
Mobile CI/CDFastlane + TestFlightSecrets in GitHub Actions sourced from Key Vaultideaplaces-devops/github/main.tf
ObservabilitySentryPython manager wrapping Sentry APIideaplaces-devops/sentry/sentry_manager.py
AnalyticsPostHogShared project with app + environment super-propertiesideaplaces-devops/posthog/
CommsDiscordWebhook setup + CI/CD failure notifierideaplaces-devops/discord/
TicketsPlaneCLI wrapperideaplaces-devops/plane/plane.sh
TicketsMonday.comGitHub Actions secrets + two-way syncideaplaces-devops/github/main.tf, monday2github/
CalendarCal.comCLI wrapperideaplaces-devops/cal.com/cal.sh
PaymentsStripeCLI setup scriptideaplaces-devops/monday2github/stripe-setup.sh
AI OrchestrationClaude (via C3)Remote sessions, cron triggers, Discord notificationsc3/

Evidence paths are relative to the IdeaPlaces meta workspace.

Engage

Need a pattern that is not in the catalog?

Most catalog modules started as a one-off for a specific customer, then graduated into reusable patterns. If your stack has a tool that needs to be brought into code, that is a good place to start.