[jpc0]

Not something I've looked deeply in to but would it not make sense to just have a single instance of these SaaS products across your entire range of products?

If you are seperating them for accounting reasons, maybe chat to an actual accountant just need to do it like once a year about that and they may have a different solution for you. There may even be an accountant in your niche that could recommend a different product stack for account that might suit your needs better.

I could think of a few ways to handle that creatively but would want to check with a professional, like spin up a seperate company whose only purpose is to sell those SaaS products to you at exactly cost...

Same with the DB, maybe look at an older idea, like sticking a Postgres DB on a cloud, or even using a managed postgres DB. There's generally a reason people converge on a single cloud and that is egress fees.

A single managed DB instance in GCP or Amazon with all your services in the same cloud means you are not paying egress fees and you are not paying whatever markup Supabse us adding.

[HopperSpeaker]

In the past yes, but today most of the tools are designed to focus on one project/project domain. For example you cannot filter session replays by website so you just have a jumble from a bunch of projects if you put them on one subscription and some analytics tools price with "1 site", "3 site" on different price points etc.

The accounting thing - yes maybe I should look at that.

You're absolutely right about DB and other aspects like that. We should do that for postgres.