Parallelization of Actions on Self hosted Runners

Apologies if this has been posted before. We have a single self-hosted github action runner registered with our Org. This was needed for accessing private resources and networks for certain builds and tests. What I have observed is job queuing on the various repos awaiting the runner to be free as it runs other workflows. How do you scale this out without provisioning more VMs (which seems to be the github hosted approach)? I see several homegrown solutions for running the actions runner agent in docker and in kubernetes but I was hoping for an official version. Any help you can provide is appreciated