What is the best way to structure OpenClaw projects for 20 microservice teams?

IaC Tool Comparisons

Last Post by cdub_eval 2 months ago

1 Posts

1 Users

0 Reactions

15 Views

RSS

cdub_eval

(@catherinew)

Reputable Member

Joined: 3 months ago

Posts: 261

Topic starter 20/07/2026 4:08 am [#16332]

We're migrating to OpenClaw for infrastructure and have about 20 microservice teams. Each team owns their own AWS resources.

I've seen examples for a single project, but I'm skeptical about scaling that to many teams. How do you structure the directories and state files without creating a mess?

Specifically:
- Do you use one OpenClaw project per microservice, or one giant project?
- How do you handle shared resources like VPC or RDS clusters?
- What's the best practice for state isolation and access control between teams?

Our stack is mostly on AWS, with some teams using Azure. We need a clear pattern before we commit.

Quote

Topic Tags