Ask HN: Multi-tenancy for Markdown-based agentic systems

So I've been looking at how companies are building their agentic setups - OpenClaw, Claude Code type systems. And one thing I keep seeing is everyone is storing memory/config/state as markdown files on disk instead of a proper database. OpenClaw literally keeps conversations, memory, skills all as .md and YAML files. Claude Code has this whole CLAUDE.md hierarchy thing where it reads markdown at the start of every session.

For single user this makes total sense - you can git track it, grep it, read it in any editor. Super clean.

But what happens when you're doing this for multiple clients? Like if you're running an agency or building a SaaS on top of this pattern?

Should we be doing one folder per client and calling it a day? What about when memory files keep growing and your context window is getting stuffed? How do you make sure Client A's stuff doesn't accidentally leak into Client B's session?

For anyone who's actually doing this in production — what's working? Separate workspaces? Containers? Some hybrid thing? Or did you just give up on markdown and go back to a database?

Genuinely curious, not finding much real-world experience on this.