Enhance oauth structure

Hey everyone,

I'm working on a project that needs oauth implementation for multiple VCS providers and hosting providers to list the user's servers and repos.

The problem is, I want to make it as simple as possible to add new providers in the future...

The first idea I came with was to add two table, vcs_providers and hosting_providers, both containing a class attribute referencing a surcharged class. This class would surcharge the VcsProvider (or HostingProvider) eloquent model, and implements methods such as server(), repositories()...

Here's a simple class diagram I just made: https://i.imgur.com/IFh5Lqa.png

I think this idea is odd... I don't know why, but I think there's a way better architecture to enhance this, but what would it be ?

Many thanks!