[rogerkirkness]

Always build customer specific work outside the API. The API stays generic, the customer code in another repo. Avoid the single tenant thing, super painful to do ops in the future unless seven figures. Use WorkOS for SSO. If it's six figures it's worth enterprise level CS. This is how a lot of great companies start.

[singleauroa]

Interesting! My product is very frontend-heavy actually when it comes to the customizations (except the SSO and ok... yes the database) Could you elaborate a bit more? I am struggling to understand.

[unraveller]

What he suggests makes hotfixes less risky for all but I don't know if totally separate codebases for every new client w/ customisations is such a great idea for a one man show. With a multi-tenant architecture you anticipate many customers having mostly the same separation concerns, but you can still easily extend the DB model separately for each. The downside being that others inspecting your universal front-end might get wind of advanced features and want them too!

Checkout something like FaunaDB where multi-tenancy is a first-class citizen and is very much designed for social frontends that run on disperse company networks with tricky auth/role escalation. In fact, if a backend is really not needed much at ALL it is the perfect DB as it can work without one. But I'm bias since I want to work with it more.