
Choose Starlink service around the project's permitted use, monthly traffic and busiest operating hours, then match the terminal and local network to the site. Fixed rural business projects should evaluate Local Priority first; household and temporary travel needs lead to different choices. Wireless bridges carry the connection between buildings, while outdoor access points for shared rural WiFi provide coverage where people use their devices.
A farm, campsite and subscriber network can all use satellite connectivity, yet their buying decisions differ. A family wants dependable access at home. A campground needs usable coverage and fair sharing. A wireless internet service provider, or WISP, also needs an authorized service model, customer support and a network that can grow without losing control of cost.
Treat the subscription, Starlink hardware and local distribution equipment as three separate purchasing decisions. Prices are U.S. dollar examples from the U.S.-display service pages, checked October 14, 2026; aviation figures follow Starlink's published USD tables. Availability, taxes, hardware charges and account offers vary by location. Examples describe proposed designs, not customer installations or measured product performance.
1. What Kind of Rural WiFi Project Are You Buying For?
Start with the people and business activities the connection must support. That decision matters before choosing the largest data allowance or the newest antenna.
1.1 A household farm and a commercial farm have different needs
A family using internet at its registered rural home can compare the Residential options available at that address. A working farm adds another set of requirements: office access, staff devices, equipment buildings, livestock monitoring and sometimes accommodation. Those activities deserve a separate service and network assessment, especially when connectivity becomes part of daily operations.
List the tasks that must continue when the site is busy. A grain store uploading camera footage and an office processing orders create different demands from occasional browsing in a farmhouse. Give each task an owner and a location on the property map. This makes it easier to decide which traffic needs dependable capacity, which can wait, and whether a business-oriented service should be evaluated for the actual use.
1.2 Guest WiFi and selling household broadband are separate projects
A campsite offering internet to guests and a WISP selling connections to independent households should not begin with the same commercial assumptions. Their users, support duties and contracts differ. A technically working bridge between buildings establishes connectivity; the right to sell that connectivity comes from the applicable agreement and local operating requirements.
Before quoting a paid service, document the country, account holder, customer relationship and intended charging model. Have the applicable Starlink terms and any required permissions reviewed for that exact model. Priority service is a relevant starting point for shared business access, but purchasing it alone does not establish blanket authorization for every form of resale. This is one of the few checks that belongs before equipment purchasing, because it can change the entire project design.
1.3 Separate the internet source from the distribution network
Think of Starlink as the upstream connection into the property. The terminal communicates with the satellite network; a router or gateway then hands that connection to the local network. A gateway is the device that controls traffic between networks. Switches connect wired equipment, bridges reach remote locations, and APs provide local wireless access.
For the underlying path from space to a user's device, see how Starlink connects satellite internet to local networks. Keep the buying decisions for each part of that path separate. A faster satellite subscription cannot move an AP into a metal workshop, and a stronger AP cannot increase the subscription's monthly data allowance. Treat each part as a separate purchasing line with a clear job, then check that the complete path supports the intended applications.
1.4 Build the project map before counting hardware
Mark the internet entry point, reception or office, occupied buildings, camera positions and outdoor activity areas. Add actual separation distances, possible mounting positions and available power. Record whether an installer can reach both ends of a proposed wireless path throughout the year. Trees, machinery and occupied vehicles can change a path that appears clear during an initial visit.
Next, label each location by service requirement: local Ethernet, local WiFi or both. A remote camera pole may need only a bridge and compatible camera power. A worker building usually needs backhaul plus an AP. The practical farm WiFi planning guide helps turn a property map into coverage zones. This approach keeps equipment quantities tied to real locations rather than an assumed radius around the Starlink router.
1.5 Define what the customer will actually receive
Write the service promise in plain language before setting a retail price. Specify the areas covered, supported applications, operating hours, support contact and treatment of heavy traffic. For a campground, that may mean general guest access in designated zones while reception systems receive separate protection. For a subscriber network, it means a clearly described service to each customer.
Avoid building the promise around a single best speed-test result. Busy-hour performance, upload demand and the remote distribution path all affect the experience. An AP's advertised connection count is also a poor substitute for a service target. A useful project requirement describes what active users can do and how the operator responds when something fails. It gives procurement, installation and support teams the same definition of success.
2. The Starlink Plan Directory: Current Families and Regional Variants
Read the directory by service family first. A complete list includes regional names and specialized services without suggesting that every option can be purchased everywhere.
| Service family or route | Current plan names | Main buying question |
|---|---|---|
| Residential | Residential 100 Mbps, Residential 200 Mbps, Residential Max, Residential, Residential Lite | Is this fixed household use at an eligible address? |
| Roam | Roam 50GB in some markets; Roam 100GB, Roam 300GB, Roam Unlimited | Is the connection temporary or portable, and what travel rules apply? |
| Local Priority | 50GB, 500GB, 1TB, 2TB presets plus configurable recurring data | What does a land-based business need each month? |
| Global Priority | 50GB, 500GB, 1TB, 2TB presets plus configurable recurring data | Does the project need the broader land or ocean scope? |
| Aviation | General, Business, Commercial and Government offerings | What aircraft service and approved installation are required? |
| Community Gateway | Project-specific service arrangement | Is this a larger provider partnership requiring a tailored proposal? |
| Standby and pause options | Account-dependent service states | How should an inactive or seasonal connection be maintained? |
Directory sources: Starlink service-plan pages, Residential and Roam support descriptions, Aviation pages and the 2025 progress report; checked October 14, 2026. Standby is a service state, and Community Gateway is a project route rather than a normal retail data tier.

2.1 A plan name is only the beginning of a quotation
For procurement, record the exact plan name alongside its country, service address, monthly charge, included data, additional-data treatment and permitted use. Add the quoted terminal and account type. Without those fields, two offers with similar names can represent different purchasing decisions.
Keep the subscription line separate from installation and local networking. A service page showing a monthly amount does not establish the price of a mast, outdoor cable route, AP network or support contract. It may also display an address-specific offer that another buyer cannot obtain. Saving a dated, location-specific quotation gives the project team something concrete to compare. It also prevents a later hardware substitution from quietly changing the service assumptions used in the original budget.
2.2 Regional names belong in the inventory, with regional limits
Residential and Residential Lite remain important names outside markets using the newer speed-tier labels. Roam 50GB also appears in market-specific support material. Including these options helps readers recognize a real local offer; assigning them a single worldwide dollar price would make the comparison misleading.
An address-based quotation is the correct next step for those variants. Record what the local offer includes and how it treats congestion, travel and data use. Do the same when a current account presents an option missing from a general marketing page. The goal is a complete purchasing framework, not a claim that the global catalogue is identical at every checkout. An installer working across countries should maintain separate country sheets rather than reuse one price list for every project.
2.3 Compare current offers with current offers
Older quotations can contain Priority 40GB, larger legacy Priority allowances, Mobile Priority or Business Jet names. Those documents may explain an existing bill, but they are not a reliable catalogue for a new installation. An old low-cost plan can also become an unfair benchmark when its replacement has different data or operating conditions.
Ask for the current service description associated with an existing account or transferred terminal. Compare the replacement plan's monthly cost and usage rules with the project's actual traffic. Keep historical names in a migration note rather than mixing them into the main selection table. That makes the proposal easier for a buyer to follow and prevents a distributor from recommending a retired label simply because it remains visible in an old article or equipment advertisement.
3. Residential and Roam: Household, Travel and Temporary Access
Residential and Roam cover useful rural situations. Their intended use and data rules matter more than whether the monthly headline price looks attractive.
| Plan | U.S. monthly example | Data or speed structure | Project interpretation |
|---|---|---|---|
| Residential 100 Mbps | $55 | Unlimited data; download capped at 100 Mbps | Fixed household use with a lower download ceiling |
| Residential 200 Mbps | $85 | Unlimited data; download capped at 200 Mbps | Fixed household use needing a higher ceiling |
| Residential Max | $130 | Unlimited data; highest Residential network priority | Higher-demand household option |
| Residential | Obtain local quote | Regional fixed-home offering with unlimited data | Use the local service description |
| Residential Lite | Obtain local quote | Regional household offering with unlimited data | Assess local priority and pricing conditions |
| Roam 50GB | Obtain local quote | Market-specific 50GB option | Read its own excess-data rules |
| Roam 100GB | $55 | High-speed allowance, then unlimited low-speed data | Occasional portable access |
| Roam 300GB | $80 | High-speed allowance, then unlimited low-speed data | More frequent portable use |
| Roam Unlimited | $175 | Unlimited Roam data, subject to service conditions | Sustained travel use rather than a fixed-service assumption |
Price source: Starlink personal service plans, supplemented by official Residential and Roam support descriptions; checked October 14, 2026. These are U.S.-display examples, not a global tariff or a complete hardware quotation.
3.1 Residential 100 and 200 Mbps set download ceilings
The two numbered Residential plans cap download speed at their stated levels. That is useful when comparing household budgets, but a ceiling is different from a continuously delivered rate. The site's actual experience still depends on the satellite connection, local conditions and distribution network.
For a farmhouse, begin with the applications used together: calls, downloads, streaming and work systems. A lower ceiling may be acceptable when heavy activities occur at different times. A higher tier can make sense when several activities overlap, provided the local WiFi and wired connections support them. Keep this decision tied to eligible household use. Extending the connection to another structure on the property is a network design question; changing who receives or pays for service creates a separate contractual question.
3.2 Residential Max does not replace project capacity planning
Residential Max offers the highest priority within the Residential family. It can be relevant to a demanding household, but that label does not turn a home subscription into a dedicated business circuit. The operator still needs to understand actual busy-hour performance and the service's intended use.
A buyer considering Max should also examine where devices connect. Upgrading a plan while leaving users behind a weak wireless hop can produce little improvement at the far end. Begin by testing a wired device near the internet entry, then compare the same workload in the rooms or buildings that matter. If the local path is the limiting factor, correct it before expecting a subscription change to solve the problem. This keeps the spending decision focused on the part of the system that needs attention.
3.3 Residential and Lite need a local comparison
Where Residential and Residential Lite are the available labels, use the local descriptions to compare price and network-priority treatment. The lower-cost option can be attractive for an eligible household with flexible demands. A home office depending on calls during busy hours may value the stronger option differently.
Do not map Lite directly onto a numbered plan from another country. A shared word such as “Residential” does not establish identical pricing, equipment benefits or expected performance. For a distributor, the useful comparison is the customer's available offer against the customer's workload. Keep marketing bundles, installation benefits and any additional terminal offer on separate quotation lines. A promotional inclusion should not become a permanent design assumption when the same project is repeated at a new address.
3.4 Roam 50, 100 and 300GB serve different local offers
A portable connection can be valuable during site surveys, construction or initial commissioning. Roam 100GB and 300GB provide different high-speed allowances before the lower-speed continuation applies. Roam 50GB remains a regional option whose own excess-data treatment must be read separately.
For a temporary installation, estimate the expected active days and applications rather than assuming that a larger allowance is automatically necessary. Downloading software images, uploading inspection video or sharing access with a work crew can change the estimate quickly. Assign the allowance to a defined task and person responsible for usage. This makes a portable subscription a managed project tool. It also helps the team recognize when a temporary arrangement has become a permanent service requiring a different plan and support model.
3.5 Roam Unlimited still has a defined operating scope
Roam Unlimited removes the need to size a fixed high-speed allowance in the same way as the limited tiers. It remains a travel-oriented service with rules covering geography and operation. “Unlimited” describes data treatment; it does not settle cross-border eligibility, ocean access or the right to sell service.
A permanently occupied campground should therefore compare the relevant fixed business options alongside any portable proposal. Its busy season is a shared-network operating problem, even if the owner also travels. For deployment teams, Roam Unlimited can be evaluated as a portable resource when usage is sustained. Record who moves the terminal, where it will operate and how it returns to service after storage. Those practical responsibilities matter as much as the advertised monthly allowance.
3.6 Seasonal closure needs a service-state plan
Standby and account-specific pause options can help manage a connection that is temporarily inactive. They are not a substitute for the normal service needed when guests, staff or subscribers return. Eligibility, charges and available functions depend on the plan, account and offer.
A seasonal operator should record the reopening procedure as part of the handover. Include who changes the service state, who checks the first bill and how the local equipment is powered and tested before customers arrive. Keep stored configurations and administrator access available during closure. A network that worked at the end of one season can still return with expired credentials, changed vegetation or damaged outdoor cabling. Planning reopening as a small commissioning job reduces avoidable surprises on the first busy weekend.
4. Which Priority Plan Fits a Rural Business Network?
For a fixed inland business project, Local Priority is the first business family to evaluate. Choose Global Priority when its broader operating scope is required, then size data from the workload.
| Priority preset | Local monthly U.S. example | Global monthly U.S. example | Allowance to budget |
|---|---|---|---|
| 50GB | $55 | $250 | Low-volume or backup use to assess |
| 500GB | $155 | $650 | A measured moderate-usage starting point |
| 1TB | $280 | $1,150 | Higher recurring monthly traffic |
| 2TB | $530 | $2,150 | Larger recurring traffic; further blocks available |
The Starlink business plan page lists these presets and configurable recurring blocks. Local additions are $25 per 50GB or $125 per 500GB each month; Global additions are $100 per 50GB or $500 per 500GB each month. Checked October 14, 2026. These recurring-block prices should not be substituted for a one-time Top-Up quote.

4.1 Local Priority addresses the normal inland business decision
A rural office, commercial farm or campground should evaluate the Local Priority offer available for its permitted use and service location. Its relevance is the business service structure and inland operating scope, rather than the idea that buying a business label eliminates every source of congestion or interruption.
Start with the critical operating period. Reception may need stable access when guests are also streaming, and a farm office may depend on uploads while cameras are active. Document those overlaps before selecting the allowance. Then consider the local traffic controls needed to protect operations. Priority on the satellite network and priority inside the property are separate decisions. A business subscription does not automatically classify guest traffic, isolate cameras or schedule large downloads on the customer's gateway.
4.2 Global Priority solves a scope requirement, not a status upgrade
Global Priority is relevant when the service needs the broader land or ocean operating scope described by Starlink. A fixed inland farm should have a specific reason to pay for that scope. Selecting it because the name sounds more capable can increase cost without addressing the actual coverage or capacity problem.
For organizations operating across locations, record where each service line will be used and what the account permits. Do not turn a multi-location purchasing arrangement into an assumption that data, terminals or capacity can be pooled freely between unrelated sites. If the project includes vessels, travel or multiple countries, make those requirements explicit in the service quotation. The local AP and bridge design still follows the users and buildings at each site, regardless of the global reach of the subscription.
4.3 Pick 50GB, 500GB, 1TB or 2TB from usage
A small allowance can be suitable for a genuinely low-volume task or an infrequently used backup. It becomes a poor budget assumption when the same connection carries continuous cloud video or unrestricted guest activity. The largest preset is also not a complete answer if the underlying workload exceeds it.
Build an estimate from active users, operating hours, downloads and uploads, then compare it with a representative billing period when service is available. Separate predictable baseline traffic from seasonal demand. This helps decide which usage belongs in recurring blocks and which is exceptional. The allowance is a monthly volume, not a promise about user count or busy-hour speed. A site can consume little data overall and still have an intense short peak that needs careful sharing and application priorities.
4.4 Automatic Top-Ups change the cost-control decision
Starlink's Managing Priority Data guidance states that service lines default to automatic 50GB Top-Ups after the recurring allowance is exhausted. If additional Priority Data is disabled, exhaustion instead leads to limits of up to 1 Mbps download and 0.5 Mbps upload. These are different operating outcomes.
For a shared network, assign someone responsibility for that setting and for the resulting bill. Automatic additions can preserve service while allowing costs to rise; disabling them contains that particular expense but can sharply reduce usable capacity. Choose deliberately, document the decision and enable the relevant usage notifications. The current rules are described in Starlink's Priority Data management guidance, checked October 14, 2026. Account settings should be part of the operational handover, not left as an unnoticed default.
4.5 Recurring increases and one-time additions serve different needs
The current data-management guidance allows recurring data in 50GB or 500GB increments. It also describes applying a recurring increase immediately to the current cycle, while increasing the monthly amount going forward. One-time Top-Ups apply within the current cycle, and unused Priority Data does not roll over.
Translate that into a seasonal budget. If the same extra traffic appears every month, the recurring allowance deserves adjustment. An isolated event may justify a one-time addition instead. Record the billing-cycle boundary when comparing the options: buying capacity just before the cycle ends has a different value from adding it near the beginning. Have the operator approve both the current-cycle consequence and the future recurring charge. That prevents a temporary busy weekend from silently becoming a permanent budget change.
4.6 Public IP, support and SLA need their own requirements
Starlink describes public-IP and business-support features for Priority service. A public IP makes an address reachable in a different way from carrier-grade NAT, or CGNAT, where the provider shares public addressing among customers. It does not automatically mean a fixed address or permission to expose every device.
Specify the remote-access method separately: an authenticated management platform, a secured outbound tunnel or another approved approach. Keep camera and administration access protected. Likewise, a service-level agreement, or SLA, describes the provider's commitments within stated conditions; it does not cover every local bridge, AP, power supply and cable. The project should define its own responsibilities and recovery process around the upstream service. Use the actual account terms and eligible hardware to establish the service commitment offered to the customer.
5. Specialized Services, Legacy Plans and Larger Provider Projects
Specialized options belong in a broad inventory, but a rural WISP should distinguish relevant land service from aircraft, maritime and tailored provider arrangements.
| Specialized offering | Published USD monthly example | Data or quotation basis | Hardware and scope distinction |
|---|---|---|---|
| General Aviation Local 50GB | $200 | 50GB | Aircraft-specific service; eligible Mini use follows aviation rules |
| General Aviation Global 50GB | $1,000 | 50GB | Broader aircraft coverage; aviation activation requirements |
| Aviation Regional 25GB | $4,000 | 25GB | Regional aircraft operations and approved installation |
| Aviation Regional Unlimited | $12,500 | Unlimited | Regional aircraft service |
| Aviation Global Unlimited | $20,000 | Unlimited | Highest advertised performance requires the Aviation Performance antenna |
| Commercial Unlimited | Obtain proposal | Fleet-specific | Commercial aircraft arrangement |
| Government Unlimited | Obtain proposal | Mission-specific | Government aircraft arrangement |
Sources: Starlink Aviation overview and Business Aviation support update dated July 2026; checked October 14, 2026. Aviation prices are published USD figures, not rural land-service alternatives. Request an account-specific quote for additional General Aviation data.
5.1 Aviation hardware is not interchangeable with a farm kit
Aircraft service has its own activation, installation and regulatory requirements. Starlink's Mini aviation guidance includes identity and aircraft verification, and treats the Mini as a carry-on device rather than an airframe-mounted installation. An aviation service name therefore cannot be paired casually with a ground-project bill of materials.
The Aviation Performance antenna is also distinct from the ground Performance Gen 3 terminal. Keep those names separate when reading speed claims or supplier quotations. A WISP working only on land can usually remove aviation options from its shortlist after recognizing their purpose. Including them in the inventory helps avoid an incomplete catalogue, but they should not dominate the buying decision for a farm, campsite or village network. The correct comparison remains the service and terminal approved for the actual operating environment.
5.2 Maritime and land mobility describe operating applications
Starlink presents maritime and land-mobility buying routes, with relevant Priority options behind those applications. They should not automatically be counted as extra universal data plans alongside Local and Global Priority. The important questions are where the terminal operates and which service conditions cover that operation.
For a fixed rural project, avoid paying for mobility features merely because a terminal could be moved physically. A contractor who needs internet while traveling has a different requirement from a campground whose equipment stays mounted throughout the season. Where one organization has both needs, quote them separately and identify the account and hardware used for each. This keeps travel convenience from becoming the controlling assumption for a permanent network, while still allowing the deployment team to maintain a suitable portable connection.
5.3 Community Gateway is a project conversation
Starlink has described Community Gateway in its public reporting as a provider-oriented project route. That makes it relevant when a larger operator needs to discuss connectivity beyond a normal small-site subscription. It is not a reason to copy historical project prices or capacities into a current retail quotation.
Prepare a provider brief before requesting such a proposal. Include service territory, customer model, demand forecast, existing infrastructure, power, maintenance access and the intended last-mile network. Ask which responsibilities belong to Starlink, the local operator and other suppliers. A tailored upstream arrangement still needs customer access equipment and operations. Treat the proposal as a project with explicit commercial and technical boundaries, rather than assuming that a particular gateway purchase creates a complete WISP business or grants automatic authorization to serve subscribers.
5.4 Legacy labels require a migration check
Older Priority, Mobile Priority and Business Jet names can remain in historical documents. Starlink's July 2026 Business Aviation update, for example, explains replacement of the Business Jet labels by newer regional offerings. Those records are useful for understanding migration, not for treating every historical tier as currently purchasable.
The same discipline helps when buying a used terminal or taking over an existing site. Obtain the current account and activation information before pricing the network around an inherited subscription. Check whether the buyer can obtain the plan being quoted and whether its intended use matches the new project. Keep any transition cost separate from the regular monthly budget. That gives procurement a fair comparison between keeping existing equipment and ordering a new terminal with a clearly documented service arrangement.
6. Which Starlink Hardware Matches the Plan and Site?
Match the exact terminal and supplied router to the available service. A recommendation for a project role is not a worldwide activation guarantee.
| Kit or terminal | Router and Ethernet handoff | Plan-matching approach | Useful project role |
|---|---|---|---|
| Standard 4 X | Router 3; two LAN ports; supported bypass path | Official guidance covers Residential, Business and Roam use contexts; confirm the offered service | Fixed site or appropriately permitted portable setup |
| Standard 4 | Router Mini; one WAN and one LAN; Dual PoE supply | Confirm the specific kit and service in the order | Fixed site with a defined Ethernet handoff |
| Starlink V5 | Router Mini; one WAN and one LAN | Select-area availability; confirm the offered fixed-home service; not intended for in-motion use | Eligible home installation |
| Mini | Integrated WiFi and Ethernet; dedicated bypass guidance | Roam/Priority availability and some Residential markets; confirm the exact current activation offer | Survey, temporary access or a separately assessed small site |
| Performance Gen 3 | No router included; Ethernet data handoff through its supply | Confirm Priority service and hardware eligibility in the proposal | Remote business project using its own gateway |
| Enterprise | Ethernet handoff for a third-party router; identify actual bundle | Confirm current business offer and availability | Fixed business network with its own gateway |
| Standard Actuated with Gen 2 router | Ethernet Adapter required for wired handoff; supported bypass route | Official guidance covers Residential, Business and Roam contexts; check current activation | Existing installation or reuse assessment |
| Standard Circular / older Performance kits | Version-specific AUX or power-supply handoff | Identify hardware before confirming service and accessories | Existing-site support rather than a default new-project choice |
Hardware sources: Starlink kit-identification, router-identification, setup and third-party-router support pages; checked October 14, 2026. The table distinguishes supported connection methods from the service offer actually available to a buyer.

6.1 Standard 4 and Standard 4 X are different bundles
The names are close, but the included router and connection layout differ. Starlink's Standard 4 setup guide identifies Router Mini and a Dual PoE power supply. Standard 4 X uses Router 3. That difference affects the handoff diagram, available local ports and accessories an installer needs to order.
Ask procurement to record the full kit name and photograph the supplied components when accepting delivery. A generic line reading “Standard Starlink” is too vague for a repeatable deployment package. Keep spare cables and instructions associated with the correct kit. This is especially helpful when several sites are installed at different times and shipments contain different bundles. The goal is a reproducible installation that a technician can recognize without guessing which generation a previous quotation intended.
6.2 V5 belongs in the inventory with a narrow use boundary
Starlink's V5 documentation describes select-area availability, a supplied Router Mini and a terminal that is not intended for in-motion use. It belongs in a current hardware overview, particularly for eligible home buyers. Those facts do not establish a universal business-plan pairing or identical availability in every country.
For a rural project, use the actual offer to decide whether V5 is relevant. If the project is a fixed household installation, compare the offered kit and accessories with the mounting and Ethernet needs. If it is a business or subscriber network, obtain an explicit service-and-hardware proposal rather than assuming the newest household kit is the preferred commercial terminal. This keeps the hardware selection aligned with the account's real operating conditions and avoids treating product novelty as a design requirement.
6.3 Mini is a portable tool, with integrated WiFi
Unlike a full-size terminal paired with a separate router, Mini includes WiFi within its compact unit. It also provides an Ethernet connection and has dedicated official guidance for connecting a third-party router. This distinction matters when explaining where WiFi starts: the function is integrated in Mini, while other kits use a separate router or downstream AP.
Mini can be considered for surveys, temporary working areas and other modest deployments. Evaluate the actual applications, mounting, power and activation offer. Older compatibility lists do not always name newer Roam tiers, so they should not be turned into either a universal approval or an automatic rejection. For a permanent shared network, compare the whole operating requirement with other eligible hardware. Portability alone does not decide the best terminal for the busiest service period.
6.4 Performance and Enterprise need an intentional gateway choice
Performance Gen 3 does not include a router in its standard kit, according to Starlink's setup guidance. A Router 3 package is a separate option, and the Ethernet data handoff can serve a third-party gateway. Enterprise also needs the actual bundle and handoff identified rather than an assumption that a household router is included.
These arrangements can suit a project that already needs independent traffic control and management. Select the gateway by routing workload, security policies, required interfaces and operational support. Keep Starlink's proprietary power arrangements separate from third-party device power: the Performance Advanced Power Supply cannot power ordinary APs or bridge equipment through its proprietary feed. A data cable connecting two systems does not establish that their power protocols match. Show both data and power paths in the installation drawing.
6.5 Bypass assigns routing responsibility to your gateway
Where the kit supports it, bypass allows the third-party gateway to take the main local routing role. That can simplify a managed project compared with running a second router behind the Starlink router. Double NAT means traffic passes through two local address-translation layers; it can complicate certain applications and troubleshooting.
Choose one clear design and document it. Record which device supplies local addresses, which holds firewall rules and how an installer restores access after a reset. Bypass does not create public addressing, extra satellite capacity or additional service permissions. Those remain separate account and service matters. An existing Gen 2 installation may require the Ethernet Adapter before the wired path is available, whereas newer routers have Ethernet ports. Buy accessories from the identified hardware layout rather than using a universal adapter checklist.
6.6 Quote terminal hardware separately from the local network
A Starlink kit price should sit beside, rather than hide, the cost of the gateway, switches, APs, bridges and installation. The local network can represent a substantial part of the practical work even when the satellite equipment is straightforward to activate.
Request a bill of materials showing quantities, cable routes, mounting parts, power supplies, enclosures and service access. Include spare items appropriate to the distance from technical support. Specify who owns each account and which party handles warranty or replacement requests. A low initial terminal offer is less useful if a failed power supply leaves the operator without a recovery route. Comparing complete project quotations makes the tradeoffs visible and keeps procurement from judging a deployable network solely by the price of the satellite box.
7. Capacity and Cost: Turn Applications into a Buying Budget
Size busy-hour bandwidth and monthly data separately. One controls how the network feels at a particular time; the other controls allowance consumption and cost.
| Budget input | What to record | Why it changes the choice |
|---|---|---|
| Active guest or subscriber demand | Simultaneous applications and their measured traffic | Determines busy-hour sharing needs |
| Camera upload | Configured or measured bitrate and upload duration | Can dominate monthly data and upstream use |
| Local recording | Storage location and remote-viewing pattern | Separates LAN traffic from internet traffic |
| Recurring service | Plan, data blocks, additional-data settings and fees | Establishes operating cost |
| Installed infrastructure | Terminals, gateway, bridges, APs, power and labor | Establishes the deployable system cost |
| Maintenance and recovery | Support visits, spares and backup connectivity | Establishes the cost of keeping service usable |
The calculations below are author-created planning examples dated October 14, 2026. Their assumed bitrates are not camera specifications, typical-user statistics or measured Starlink results.

7.1 Count active demand rather than registered devices
A phone connected to WiFi may be idle, while another device uploads a large file. Counting both equally gives little insight into the workload. Begin with activities that overlap during the busiest operating period, then identify which require protection and which can tolerate reduced speed.
As a hypothetical example, twenty active users averaging 3 Mbps each create 60 Mbps of aggregate demand at that time. This is an arithmetic assumption, not a recommended user limit for an AP or subscription. Replace it with measured applications and realistic concurrency for the property. Include upstream activity as well as downloads. The resulting estimate gives the gateway policy a purpose: protect defined operations while sharing the remaining capacity among users, instead of trying to maximize every speed test independently.
7.2 Continuous camera uploads can consume an allowance quickly
Assume one camera sends a continuous 2 Mbps stream to the cloud. Over a 30-day month, the calculation is 2 × 86,400 × 30 ÷ 8 ÷ 1,000 = 648 GB. Four such streams total 2,592 GB, or 2.592 decimal TB, while continuously using 8 Mbps of upload capacity.
These are deliberately stated assumptions, not a typical camera bitrate or an observed installation. Actual traffic depends on encoding, scene changes, audio, recording schedule and service behavior. Obtain the configured and measured rates from the camera system before selecting a plan. The example explains why a modest-looking video stream can outweigh ordinary office browsing in a monthly budget. It also shows why evaluating cameras only by download speed misses the direction that matters for continuous cloud recording.
7.3 Keep local video local when the application allows it
A local network video recorder, or NVR, can retain footage on the property instead of sending every stream continuously through Starlink. Remote viewing and approved cloud backups still use internet upload, but their timing and volume can be managed separately from local recording.
Decide this with the person responsible for security evidence. Retention, event visibility and off-site protection may be more important than reducing a data bill. Do not silently lower video quality to make a smaller subscription appear adequate. A remote camera link may also carry video entirely within the local network, so its bridge capacity matters even when satellite traffic is limited. Draw both paths: camera to recorder, and recorder or camera to remote viewer. That makes the local hardware requirement and internet allowance easier to size correctly.
7.4 Translate the busy period into a monthly estimate
Using the earlier hypothetical 60 Mbps aggregate load for two hours every day produces 60 × 7,200 × 30 ÷ 8 ÷ 1,000 = 1,620 GB over 30 days. That calculation assumes the same average traffic throughout those hours; real usage may be lower or higher.
Build several explicit scenarios rather than pretending the first estimate is a forecast. Separate normal occupancy, the busiest season and unusual events. Add updates, staff activity and remote camera access where relevant. After commissioning, replace assumptions with measured billing-period data. Keep the original estimate so the team can explain why the budget changed. This turns allowance selection into a controllable operating decision and makes it easier to distinguish expected growth from an application or configuration that is generating unexpected traffic.
7.5 Compare installed cost and operating cost together
A useful proposal contains an installation budget and a recurring budget. The first includes the terminal, local hardware, mounts, cables, protection, power and labor. The second includes service, expected data additions, backup connectivity and support. Add a separate allowance for realistic recovery work rather than hiding it inside an optimistic headline price.
For a growing property, show which equipment can remain when another building is added and which part must expand. A new AP may be inexpensive compared with creating a safe powered mounting point. A second satellite connection also adds recurring cost and management work. Compare alternatives by the service they can support and the maintenance they require. This gives an owner a more useful decision than a bare list of devices whose combined installation requirements remain unknown.
8. WISP Deployment Choices and COMFAST Hardware Roles
A bridge transports the network to a remote area; an AP provides WiFi there. Gateway policy and compatible power distribution make those links manageable as a shared service.
| Scenario | Local network approach | COMFAST candidates by role | Distance input | User or traffic input | Power input |
|---|---|---|---|---|---|
| Yard beside the main farm building | AP with wired backhaul | WA933 AP | Actual coverage zone and cable route | Busy-hour users and work devices | Supported PoE or local DC |
| Detached barn or staff building | Point-to-point bridge, then AP where needed | E319A V3 bridge pair; WA933 AP | Surveyed path and mounting heights | Remote building's aggregate traffic | Power at both ends; matched bridge supplies |
| Campground with several occupied zones | Gateway, PoE switch and distributed APs; bridges for remote zones | AC50 gateway candidate; SG181P switch; WA933 APs; E319A V3 for suitable dedicated links | Zone map and each remote path | Busy-season active users by zone | Verified switch budget and endpoint supplies |
| Remote camera or gate | Bridge and wired connection; AP only if local WiFi is needed | E319A V3 for suitable path; appropriate camera power equipment | Endpoint visibility and access route | Upload schedule and local video traffic | Remote endpoint power and camera compatibility |
| Paid multi-household WISP | Authorized upstream service, validated backhaul and subscriber management | Assess these products for individual roles; select the required operator gateway/platform separately | Each service path and future expansion area | Subscriber service targets and concurrency | Maintainable power at every network node |
This is a selection framework, not a promise of model-specific range or user capacity. The distances, loads and power requirements must come from the actual site survey.

8.1 Draw one complete path to each service area
The basic layout is Starlink, the correct power and data handoff, a gateway, then a switch feeding APs and remote links. At a distant building, the bridge endpoint connects to local Ethernet equipment or an AP. Backhaul means the path carrying a local area's traffic back to the main network.
Keep the drawing readable enough for the owner and technician to use together. Show the device responsible for routing, each powered endpoint and the final access method. If a device has several possible operating modes, record the chosen mode on the drawing. This avoids a common procurement gap in which the proposal contains all the right product categories but no clear connection between them. Each service location needs a continuous data path and an independently understood power path.
8.2 Use a dedicated bridge for a suitable detached-building path
For an isolated barn or workshop with a usable wireless path, a point-to-point bridge can carry the local network between two locations. The CF-E319A V3 Gigabit directional bridge is a candidate for this role; its product specification lists a Gigabit Ethernet interface. That interface does not establish measured end-to-end wireless throughput.
Survey visibility, obstructions, mounting stability, interference and power at both endpoints. The guide to long-range Starlink farm bridge paths develops that property-level assessment. Use the bridge's matched power arrangement: a stated 48V supply is not proof of compatibility with every standards-based PoE switch. At the far building, add an AP only when users need WiFi. Wired cameras, recorders or office devices may instead connect through an appropriate local switch.
8.3 Multiple buildings need a topology decision
Several remote buildings can be connected through separate point-to-point paths or a suitable point-to-multipoint system. Point-to-multipoint, or PtMP, means a central radio arrangement serving several remote endpoints. Its shared radio capacity and supported client arrangement need to fit the intended system.
Do not assume a product sold for a point-to-point link is automatically a sector base station for many subscribers. Dedicated links may be preferable when buildings face different directions or require different traffic allocations. A validated PtMP design can be useful when the central location and remote paths suit it. The Starlink multiple-building topology guide explains that layout decision. For either approach, account for traffic returning through the central gateway and upstream connection; adding remote endpoints does not create extra satellite capacity.
8.4 Place APs where users need service
An AP should cover a defined occupied zone, such as reception, a work yard or a group of campsite pitches. It should not be expected to act as both a long-distance building link and a universal coverage source. Backhaul brings usable network capacity to the zone; AP placement determines how devices access it locally.
The CF-WA933 WiFi 6 AP for shared outdoor areas is a candidate to assess. Its product table lists a Gigabit WAN port, two Gigabit LAN ports and 802.3af/at PoE support, with 12V DC also listed. Choose the installed quantity from the zone layout and active workload. Do not turn an advertised radio rate or client count into a service guarantee. Test at the places where guests and staff actually work, including coverage edges and obstructed areas.
8.5 A subscriber service needs more than outdoor radios
A paid WISP also needs customer provisioning, access policy, support records and a way to manage congestion. Subscriber authentication identifies who may use the service. Billing and account suspension are commercial workflows that need suitable software and gateway integration, rather than functions to assume are built into every bridge or AP.
Specify those requirements before accepting a hardware package. If guest portals, VLANs or remote management are required, map support across every relevant gateway, switch, bridge mode, AP and platform. A VLAN is a logical separation within a network; its usefulness depends on the complete path handling the design correctly. Ask for a configuration demonstration using the proposed firmware and platform. This produces an operating system the WISP can support, rather than a collection of radios with an unspecified customer-management layer.
8.6 Select the gateway by confirmed functions and workload
A gateway should fit the number of active sessions, traffic policies, security needs and management process. For projects considering COMFAST routing and AP management, the CF-AC50 for routing and AP management has Gigabit interfaces listed on its product page. Its power specification is 12V/1A, and the page lists no PoE function.
Confirm the proposed firmware and compatibility with the exact AP models before using centralized management as a purchasing reason. Treat required subscriber billing, authentication, network separation and backup behavior as specific functions to demonstrate. Select AC50 against functions demonstrated with the quoted firmware. Where a project needs a separate operator platform or gateway, include it explicitly in the proposal. The local gateway should be selected for the service to be operated, not simply because its enclosure sits beside the Starlink equipment.
8.7 Match PoE distribution to each endpoint
Power over Ethernet, or PoE, carries compatible electrical power and data over an Ethernet cable. It simplifies suitable AP installations, but compatibility depends on the equipment's power requirements and supported standard. A matching voltage alone is insufficient for a safe purchasing assumption.
The CF-SG181P Gigabit PoE switch for multiple APs lists eight Gigabit PoE ports, two additional Gigabit RJ45 ports and 802.3af/at support. Obtain the confirmed total power budget for the quoted hardware and compare it with all planned endpoints. Use the confirmed power budget for the quoted hardware revision. Keep the E319A V3 bridge's matched supply separate unless compatibility is confirmed. Also specify the installation environment and enclosure; an industrial product label is not an outdoor weatherproofing specification.
9. How Should a WISP Test, Operate and Expand the Network?
Accept the complete service at the places people use it. Separate satellite, backhaul, access and power checks so failures can be located and corrected.
9.1 Survey satellite visibility and ground paths separately
The Starlink terminal needs an appropriate view of the sky, while a bridge needs a suitable path toward its partner radio. Those are different directions and different installation problems. The best terminal location may be a poor bridge hub, and the most convenient equipment room may be far from both.
Inspect the proposed routes before making them final. Include roof edges, trees, terrain, movable machinery and safe cable access. Record seasonal conditions that cannot be observed on installation day. If the bridge hub must sit away from the gateway, include the intervening cable or fiber path and its power requirements. This prevents the installer from forcing every device onto one convenient pole and then discovering that either satellite visibility or the local distribution path has been compromised.
9.2 Test applications through the busiest service path
A speed test beside the main router establishes only a limited view of performance. Test a wired connection at the entry, each remote backhaul and each important access zone. Then run the applications the customer depends on while representative competing traffic is present.
Record the conditions alongside the results: location, active load, connection method and time. Assess upload behavior for cameras and calls, and responsiveness for transactions or work systems. Agree the acceptance conditions and required application behavior before installation. Use findings to separate the problem layers. If the wired entry performs well but a remote AP does not, investigate the local path before changing the satellite subscription. A repeatable acceptance process gives the operator a useful reference when later complaints or capacity changes appear.
9.3 Protect operations through demonstrated network policy
A campground can have guest traffic alongside reception, staff and camera systems. A farm may combine office work, accommodation and monitoring. Give those groups the access and traffic treatment the project requires, using hardware and software that actually support the design.
Guest isolation, portals, VLANs and bandwidth controls may involve several components. Confirm how the chosen gateway, APs, switches and management platform work together, then demonstrate the intended behavior. For example, show whether a guest can reach an operations device and whether a heavy upload affects a critical transaction. Document the accepted configuration. A feature name on an AP's marketing page is less useful than a working policy across the installed network. This keeps security and service management tied to observable behavior rather than an unsupported list of capabilities.
9.4 Design recovery around shared failure points
A second connection can improve options during an outage, but its value depends on what fails and how the gateway reacts. Two satellite terminals may still share power, mounting exposure or upstream conditions. Multi-WAN equipment also does not automatically combine two links into one faster download or preserve every active session during switching.
Describe the recovery behavior the customer needs, then test it using the selected gateway and services. Include loss of local power, a disconnected backhaul and an unavailable upstream connection where those checks are appropriate. Decide which applications restart automatically and which need staff action. Provide instructions that can be followed by the person on site. A practical recovery procedure is often more valuable than a redundancy diagram whose shared dependencies have never been examined.
9.5 Expand from operating evidence
Keep a record of busy-hour usage, monthly consumption, support incidents and the zones needing improvement. Use those observations to decide whether the next purchase should be more recurring data, another AP, a different backhaul path or another upstream service. Each solves a different constraint.
Maintain configuration backups, device labels, administrator ownership and an up-to-date diagram. Record who can approve changes to data settings and customer policy. When adding a building, repeat the path, power and workload assessment instead of copying the previous installation blindly. This gives expansion a clear basis and makes the network easier for another technician to support. A growing WISP needs a repeatable operating process as much as it needs spare ports and mounting space.
10. Conclusion: Buy the Service and the Local Network as One Project
A sound rural Starlink project starts with permitted use and the actual service location. Compare the available plan's operating scope, monthly data and cost, then identify the terminal, router and Ethernet handoff. For fixed business access, evaluate Local Priority first; use broader or portable offerings when the project requires them.
The local network completes the service. Bridges reach detached buildings, APs serve users within each zone, gateways enforce supported policies, and compatible switches distribute wired access and power. Size the system from applications and operating evidence, with a clear plan for support and expansion. This produces a quotation that an owner can understand, an installer can build and a WISP can operate.
11. Frequently Asked Questions
Provide the country and service location, operating model, building map, measured distances, busy-hour users, camera upload requirements, available power and management needs. COMFAST can discuss the relevant networking products and project requirements with installers, distributors and OEM buyers.




