Plugin to Product relationship (one-to-many or one-to-one)

I have a few questions on how we should approach designing plugins for the web client.

If a customer deploys multiple instances of my company's product, lets say, Chassis-A, Chassis-B, Chassis-C, etc.

One-to-one

1. Should each Chassis have its own web plugin?
2. If they should, will they conflict with each other even if they have different keys? It would become difficult to distinguish them.

One-to-many

1. Should one plugin serve multiple Chassis?
2. Is there a recommendation on how to keep track of Chassis registered? Or should we be deploying an external service for that?

Thanks