I was thinking about this exact problem, and I came up with a similar idea. There could be a parent company developing the core software and maybe even providing installation and setup services, but each campus ultimately maintains their own self-hosted, zero-trust instance. Each campus would be downstream implementations of the parent software and would only update or talk to other instances as needed.
Given how campuses operate, it seems like they would be great candidates for an optionally federated platform like that.
I was thinking about this exact problem, and I came up with a similar idea. There could be a parent company developing the core software and maybe even providing installation and setup services, but each campus ultimately maintains their own self-hosted, zero-trust instance. Each campus would be downstream implementations of the parent software and would only update or talk to other instances as needed.
Given how campuses operate, it seems like they would be great candidates for an optionally federated platform like that.
So just, Software as a Product (SaaP)?
So just traditional software?
Ha, think you just discovered the standard model from the 2000s!
But I agree.
The problem is CapEx vs OpEx.