Why browsing works but a home server may not
When you browse, your device starts the connection and replies can come back through it. A person connecting directly to a server in your home needs a new incoming connection. Starlink’s default shared IPv4 service blocks that route. A camera which connects out to its own cloud service may work without a public address; check how your particular system works.
A different router does not remove CGNAT
Starlink’s routers do not provide configurable port forwarding or IPv4/IPv6 firewall rules. A third-party router can provide those controls, but Starlink’s upstream CGNAT still applies. For direct incoming IPv4 connections, Starlink says you need both a suitable third-party router and a plan with the public IPv4 option.
Public does not mean permanently fixed
Starlink reserves its public IPv4 address across reboots and periods switched off. Relocation or software changes can still change it. If an employer allows access only from one specified address, confirm that it accepts this arrangement. Buying a Priority plan does not turn the service into a guaranteed static-IP connection.
Where IPv6 helps
Starlink provides native IPv6 across its plans and kit versions. It can support a different route for remote access, but both ends of the connection need IPv6 support and the home firewall must allow the intended service. Starlink’s supplied router does not offer custom firewall rules, so IPv6 alone is not a complete home-server setup.
Check the application before changing plans
Ask whether the camera, server or work system needs a direct incoming connection or can establish its own outgoing connection. That answer determines whether you need public IPv4 at all. A company VPN which supports NAT traversal may already work on Residential service without an upgrade.
Send a correction if a source has changed or something needs updating.