# Scaling with Proxy Nodes

**URL:** <https://community.sonatype.com/t/scaling-with-proxy-nodes/12126>\
**Category:** Sonatype Nexus Repository\
**Tags:** nexus-repository\
**Created:** [February 21, 2024, 7:42pm UTC](https://community.sonatype.com/t/scaling-with-proxy-nodes/12126 "2024-02-21T19:42:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![stevda86](https://avatars.discourse-cdn.com/v4/letter/s/82dd89/32.png) [@stevda86](https://community.sonatype.com/u/stevda86)\
**Post date:** [February 21, 2024, 7:42pm UTC](https://community.sonatype.com/t/scaling-with-proxy-nodes/12126/1 "2024-02-21T19:42:39Z")

</div>

I have a few questions about setting up the proxy nodes as described here: [Scaling with Proxy Nodes](https://help.sonatype.com/en/scaling-with-proxy-nodes.html)

Is this a Pro Feature?

How do I best implement this? I already have a Nexus that has an internal maven repo as well as a public proxy repo and combines them in a group. What do I then set up on the proxy node? the same group name and below it 1 proxy that points to the main node?

Is there a way to simply use all requests that come to this proxy node as a proxy? or do I have to set this up for each repo that exists on the master node?