Case study
IdeaPlaces
A portfolio of products and services that itself runs on OneOps patterns. The meta-repository and workspace that ties everything together.
Context
The portfolio
A founder-led portfolio running dozens of products in parallel. Different cloud vendors, different identity providers, different vendors per vertical. The coordination problem was the product. OneOps became the answer.
Scope
What was compiled
- · Meta-repo pattern (ideaplaces-meta orchestrates all sub-repos)
- · Azure, Cloudflare, Google Workspace, GitHub all in Terraform
- · C3: remote Claude Code sessions with Discord and cron triggers
- · Cross-platform outreach (LinkedIn, Discord) as code
- · Monday.com to GitHub two-way sync
- · Shared PostHog analytics with multi-app super-properties
Numbers
Headline figures
Snapshot, not live
29
sub-projects in the meta-workspace
1
GitHub repo declaration per project
311691
shared PostHog project id
Zero
GitHub repos created via the UI
What it proves
OneOps keeps compounding as new integrations arrive.
Every new product in the portfolio plugs into the same cloud, identity, CI/CD, secrets, observability, and comms substrate. New integrations added in one place benefit everything already deployed. The catalog is the moat, not any individual integration.
Engage
Can we do this for your company?
If you have a multi-vendor stack that grew organically, the answer is almost always yes. The first step is Assess: a Console Debt Report that ranks what to compile first.