This denotes your apps processes to run on separate Heroku dynos, Puma on a web dyno, Sidekiq on a worker dyno. Dynos are isolated containers, not “servers” as such, they likely won’t even be running on the same underlying machine.
To translate that to Render nomenclature, those dynos would become a Web Service for Puma & a Background Worker for Sidekiq.
We have examples to run Rails & Sidekiq in the docs:
Getting Started with Ruby on Rails on Render
Deploy a Sidekiq Worker
Multi-service deployments (including Postgres & Redis services, which you’d probably also need) can be configured in a render.yaml blueprint, so that your infrastructure can be defined in your code, more on this here: Infrastructure as Code (IaC)
With regards to wicked_pdf, as far as I’m aware the only dependency is wkhtmltopdf, which is easiest installed with the wkhtmltopdf-binary gem.