Is this a pattern anyone else is using?

Hi all, i feel like I've discovered a new pattern of development, but I also know that everything's been done a million times already, so I'm wondering if there is a different name for this...

We have a product that, due to customer and product limitations cannot be containerized.

Therefore I built a plug-in architecture Microservice builder library. It contains an IMicroserviceConfiguration and IHostConfiguration. The general idea is that you import package libraries via NuGet that each have one IMicroserviceConfiguration implementation.

In that way our IHostConfiguration is somewhat like a docker container in that it has what we can "refer to" as a gac, but for the microservices imported into the host. And whe. The host starts up the microservices start up. And we can technically spin up multiple instances of a host. Although our current infrastructure requires they be on different virtual environments. So obviously not nearly as powerful as containers, but in theory, one day we can have a single microservice per host, and containerize that host, so it's just an extra layer of abstraction.

I'm kind of really proud of it but we're also going live with it soon and I'm looking for advice on things that can go wrong, and gotchas. Is this a pattern, the idea of packaging application logic into standalone NuGet packages, to be imported into a miniservice, that anyone else recognizes, and if you have dealt with similar (not even necessarily same), I'd love to hear advice?