Developing a Shelter Communications Partnership Program

Full report

On this page

Executive Summary

The strongest evidence-based path is not a single monolithic offering, but a two-track shelter communications program: a LoRa-first fixed infrastructure package for most shelter projects, plus a goTenna-enabled premium operator layer for customers that can legally and operationally support professional VHF/UHF deployments. That recommendation follows from three hard facts in the source set: the current official AnarchyShelters site does not yet publish substantive product, process, or dealer information; current goTenna Pro X2 and EdgeRelay products are professional systems operating in VHF/UHF bands that may require FCC Part 90 licensing in the United States; and LoRaWAN itself is a standardized star-of-stars LPWAN, not a mesh, while custom/proprietary LoRa can be used for mesh-like topologies when the use case really needs them.

Commercially, the most pragmatic launch sequence is a referral-first pilot, then a selective resale/white-label expansion after the pilot proves attach rate, install repeatability, and frequency-compliance workflow. goTenna itself actively markets a tech partner program and integration program, and its Pro X2m is explicitly positioned for integration partners, OEMs, resellers, and distributors; that makes a channel relationship feasible, but the incomplete public state of AnarchyShelters.com argues against jumping immediately into a broad bundled resale motion.

Technically, the most resilient architecture for shelters is a three-layer stack. The fixed layer handles telemetry, alarms, environmental status, and low-rate automation over LoRaWAN or a custom LoRa mesh. The mobile/team layer uses goTenna Pro X2 and, where needed, EdgeRelay for local situational awareness and short-burst messaging. The reach-back layer uses optional LTE, Starlink Mini, or goTenna + EVERYWHERE depending on whether the requirement is broadband IP backhaul or low-bandwidth command-and-control data. That stack separates low-power sensors from mobile operator traffic, which is exactly where the source material suggests each technology performs best.

The core regulatory caveat is important enough to state plainly: if the target buyer is a pure consumer/homeowner, public launch of a goTenna-based VHF/UHF operator package should be delayed until outside FCC coordination counsel confirms the licensing model. FCC materials describe Private Land Mobile Radio as serving companies, local governments, and other organizations, and FCC history for the Industrial/Business Pool says anyone engaged in commercial activity is eligible; those facts support builder-, association-, ranch-, industrial-, and security-operated deployments much more cleanly than ordinary residential consumer use. For the broadest civilian market, the default offer should therefore be LoRa-first, with goTenna sold as an optional professional-use add-on for customers that meet licensing and operating prerequisites.

Evidence Base and Assumptions

The official source base is unusually uneven. On the one hand, goTenna publishes substantial current material: current Pro X2, Pro X2m, EdgeRelay, partner-program, support, warranty, and product-catalog content; LoRa Alliance and Semtech publish clear primary-source material on LoRaWAN topology, relay, security, and proprietary-protocol flexibility; the FCC and eCFR provide the controlling U.S. spectrum rules; and RAK and Starlink publish current gateway and backhaul pricing/specifications. On the other hand, the official AnarchyShelters site presently appears to be a default WordPress installation with a “Hello world” post and sample page rather than a populated commercial site. That means this report can rigorously design the partnership model and technical stack, but it cannot validate current AnarchyShelters positioning, market copy, construction standards, or dealer footprint from its own official website.

The second major limitation is pricing transparency. Current goTenna public product pages for Pro X2, Pro X2m, and EdgeRelay route buyers to request pricing, rather than publishing list pricing. By contrast, RAK and Starlink do publish public prices. For that reason, exact goTenna figures used below are planning assumptions, not quoted vendor list prices. The margin and P&L sections are therefore suitable for business planning, partner negotiation, and internal target setting, but not for issuing customer quotes without vendor confirmation.

The financial examples below use these working assumptions:

The choice to segment the offer this way is driven primarily by the official site constraints and the licensing posture of goTenna’s current U.S. products.

Partner Structure and Commercial Models

The partnership has three distinct value propositions, and each should be reflected in product packaging and contract language. AnarchyShelters gains a differentiated resilience upgrade, a way to raise average project value, and a recurring-revenue attachment without having to build radio engineering, NOC, or field-service capability from scratch. Your company gains early access to the construction lifecycle, which matters because conduit routes, antenna penetrations, rooftop or mast mounting points, UPS locations, and battery spaces are far cheaper to design into a shelter shell than to retrofit later. The end customer gets a single design authority for bunker construction plus communications, which is especially valuable when RF exits, grounding, solar/battery integration, and external mast siting must all be coordinated tightly. The fact that goTenna actively encourages integration partnerships and sensor/network-device integrations makes that channel strategy more credible.

The recommended commercialization sequence is shown below. It deliberately starts with the lowest-friction structure and only graduates into wider channel commitment after proof of close rates, install repeatability, and compliance workflow.

These are recommended economics, not legal norms or market averages. They are designed around the facts that goTenna itself says the mesh network has no required recurring network OPEX, while your real recurring value comes from monitoring, support, backhaul management, preventative maintenance, and periodic refresh services.

The most defensible launch recommendation is Referral → Selective Resale → White-label only if attach rates and compliance justify it. That sequence reduces risk because the partner can begin selling immediately with minimal inventory, while your company learns the true shelter construction workflow, power environment, below-grade RF constraints, and customer qualification pattern before locking in broader dealer commitments. That caution is especially justified because AnarchyShelters’ current public web presence is not yet a usable sales asset, while goTenna already has a formal partnership intake and integration framework.

flowchart TB
    A[Partner interest] --> B[Mutual NDA and commercial fit review]
    B --> C[Use-case qualification]
    C --> D{Customer and use case Part 90 eligible?}
    D -->|Yes| E[Dual-layer offer: goTenna + LoRa]
    D -->|No or unclear| F[LoRa-first offer only]
    E --> G[Frequency coordination and compliance review]
    F --> H[LoRa architecture and site survey]
    G --> I[Sales certification and collateral pack]
    H --> I
    I --> J[Pilot deployment]
    J --> K[Acceptance review and KPI check]
    K --> L{Pilot successful?}
    L -->|Yes| M[Execute referral or reseller agreement]
    L -->|No| N[Revise offer, targeting, or architecture]
    M --> O[Launch quarterly business reviews]

A simple but effective commercial rule should govern opportunity qualification: if the communications sale depends on a fast legal path or a retail homeowner buyer, default to LoRa-first; if the buyer is an entity engaged in commercial activity, private security, operations, association governance, or organized site management, then qualify the goTenna layer. That rule is grounded in the FCC’s treatment of PLMR and the official goTenna licensing language.

Technical Architecture Options

The most robust shelter communications design is a layered architecture, not a single-radio bet. goTenna’s Aspen Grove network is optimized for mobile, short-burst, off-grid messaging and situational-awareness traffic; goTenna says Pro X2 supports text/location-style communications rather than voice, and its catalog emphasizes tactical data, mapping, and operator awareness. LoRaWAN, by contrast, is a standardized LPWAN where gateways bridge end devices to a network server in a star-of-stars topology. Semtech also states that LoRa as a physical layer can be used in different topologies, including proprietary protocols, which is why a custom LoRa mesh can make sense for sparse bunker-to-bunker alarm/status traffic when a standard LoRaWAN topology is not ideal.

Product and architecture choices

Source basis: goTenna official datasheets and product pages, LoRa Alliance official specifications, and Semtech official FAQs and product pages.

The strategic conclusion is straightforward. For most shelter projects, use LoRaWAN for all fixed telemetry and reserve custom LoRa mesh only for site-to-site cases where relay geometry or sparse links defeat a simple star topology. Use goTenna only where the customer’s mission profile really needs human-carried/mobile situational awareness, elevated relay persistence, or tactical-style data sharing. That reduces both cost and regulatory complexity while preserving a premium upsell path.

Gateways, backhaul, power, and antenna planning

Source basis: official RAK store and documentation, official Starlink pages/specs, and official goTenna product catalog.

A practical power design rule follows from those published numbers. If a shelter needs only a solar LoRaWAN relay/gateway, the vendor-bundled solar gateway is the cleanest answer. If the site also needs Starlink Mini, power planning changes materially: Starlink Mini alone averages roughly 20–40 W, so at a 30 W planning midpoint it consumes about 720 Wh/day; RAK’s smaller backup product implies a gateway load of roughly 5 W under moderate use, so a gateway plus Starlink site is a reasonable ~35 W average-load planning case, roughly 840 Wh/day before losses. In practice, that points to a much larger battery-and-solar package than a LoRa-only site—typically a 200+ Ah class battery equivalent and 300–600 W solar depending on autonomy target and climate. The precise number should be finalized from local irradiance and seasonal duty cycle, but the key business point is clear: broadband backhaul is the main power cost driver, not LoRa itself.

For site planning, the most important rule is to treat the bunker as an RF-hostile enclosure and move the radio horizon above grade. goTenna itself recommends UHF primarily for body-mounted use and VHF primarily for fixed or vehicular antennas, and its field catalog shows dramatically better performance with elevation, relays, and even tunnel-to-above-ground geometry. For bunker work, that translates into these engineering defaults: above-grade mast or pole mounts, sealed feedthroughs to a shielded equipment space, antenna separation between LoRa and goTenna systems, single-point bonding/grounding, lightning/surge protection, and a site survey that prioritizes elevation and Fresnel clearance over raw transmitter count.

flowchart LR
    subgraph A[Site A Shelter]
        A1[LoRa sensors\n environmental / intrusion / power]
        A2[LoRa node or controller]
        A3[goTenna Pro X2 handhelds]
        A4[EdgeRelay or elevated Pro X2 relay]
        A1 --> A2
        A3 --> A4
    end

    subgraph R[Relay / High Ground]
        R1[Outdoor LoRa gateway\n or custom LoRa relay]
        R2[EdgeRelay\n persistent goTenna relay]
    end

    subgraph B[Site B Shelter]
        B1[LoRa sensors]
        B2[LoRa node or controller]
        B3[goTenna Pro X2 handhelds]
        B4[EdgeRelay or elevated Pro X2 relay]
        B1 --> B2
        B3 --> B4
    end

    A2 --> R1 --> B2
    A4 --> R2 --> B4

    R1 -. optional IP backhaul .-> C[Starlink Mini / LTE / Fiber]
    R2 -. optional TAK reach-back .-> D[goTenna + EVERYWHERE]

Operations, Commissioning, and Service Levels

The delivery model should be treated as a managed infrastructure discipline, not as an accessory install. goTenna’s current software stack already supports remote relay-health visibility—battery charging status, transmit antenna performance, receive signal-strength context, hop count, message load, and temperature—while RAK’s current gateway family supports remote management and monitoring through WisDM/WisGateOS on supported products. Those published capabilities make a real managed-service layer commercially credible.

A best-practice deployment process has five gates. First comes site qualification: structure drawings, line-of-sight assessment, antenna location plan, energy budget, and frequency/compliance screening. Second comes pre-build staging: firmware baselines, serialized asset record, encryption/config template, battery prep, pre-terminated cable sets, and acceptance test plan. Third comes field installation: mast/antenna install, grounding and surge protection, power and battery integration, and gateway/relay mounting. Fourth comes commissioning: end-to-end test messages, telemetry test, below-grade/above-grade RF test, relay-health baseline, failover test, and documentation handoff. Fifth comes steady-state support: monitoring, periodic maintenance, spares swap, firmware/config changes, and annual recommissioning. goKit 2 is a useful training and staging asset because the official materials describe it as a portable off-grid command-and-deployment kit for up to 30 users and as flight-ready for travel.

A commissioning package should always leave behind a frequency plan, a network topology diagram, a serial-numbered asset register, site photos, antenna/grounding record, battery and power worksheet, baseline RSSI/SNR or packet-delivery record, and a customer acceptance certificate. Those documents matter commercially because they convert a hard-to-defend “radio install” into a measurable infrastructure asset with a service history.

A practical SLA menu can be simple and still sell well:

Those timeframes are recommended commercial templates, not vendor guarantees. They should be adjusted upward or downward based on travel radius, spares policy, satellite dependence, and whether the customer expects winter-weather or disaster-response coverage.

gantt
    title Pilot-to-launch deployment timeline
    dateFormat  YYYY-MM-DD
    section Program setup
    NDA and commercial scoping          :a1, 2026-06-02, 7d
    Compliance and frequency workflow   :a2, after a1, 14d
    Sales collateral and quoting model  :a3, after a1, 14d
    section Pilot engineering
    Site survey and RF plan             :b1, after a2, 10d
    BOM freeze and procurement          :b2, after b1, 14d
    Bench staging and configuration     :b3, after b2, 7d
    section Field work
    Install and power integration       :c1, after b3, 5d
    Commissioning and acceptance        :c2, after c1, 7d
    section Scale-up
    Partner training and launch pack    :d1, after c2, 10d
    Referral or reseller launch         :d2, after d1, 7d
    First quarterly business review     :d3, after d2, 45d

Compliance, Safety, Supply Chain, and Contracting

Spectrum and licensing

This is the report’s highest-risk topic. Official goTenna materials state that Pro X2 is designed for professional use in VHF 142–175 MHz and UHF 445–480 MHz, and that operation in the United States may require an FCC Part 90 license. FCC materials describe Private Land Mobile Radio as serving companies, local governments, and other organizations, and FCC rulemaking history for the Industrial/Business Pool says that anyone engaged in commercial activity is eligible, along with educational, philanthropic, and ecclesiastical institutions. That is compatible with builder-operated, association-operated, ranch-operated, security-operated, or otherwise entity-operated systems; it is much less clean for direct homeowner-consumer retail without an entity-based licensing model. Accordingly, any public U.S. launch that includes goTenna as a standard consumer shelter option should be preceded by frequency-coordinator and communications-counsel review.

For LoRa in the United States, the relevant baseline is very different. Unlicensed devices under Part 15 must not cause harmful interference and must accept interference received, and 47 CFR 15.247 governs operation for spread-spectrum and digitally modulated devices in the 902–928 MHz band. The LoRa Alliance regional-parameter documents define U.S. LoRaWAN behavior for US915. In business terms, this means a LoRa-based shelter offer is easier to sell broadly because it does not need user licensing, but it is also more exposed to noise-floor uncertainty, neighbor interference, and non-exclusive spectrum conditions.

Antenna compliance deserves explicit process controls. The filed goTenna user guide states that the Pro X2 antenna shall not exceed +8.15 dBi gain, and it warns that unauthorized modifications can void authority to operate. For field practice, that means the partner program should only use approved antenna SKUs and documented mounting configurations for goTenna systems. The same governance principle applies to any custom LoRa product program: if you productize a custom mesh, use pre-certified modules or certified end-products where possible to avoid avoidable FCC test and filing cost. Semtech’s LR1121 launch materials specifically noted a pre-certified Murata module path for faster time to market.

Antenna structures, grounding, and electrical safety

OSHA’s antenna rules require masts and supporting metal structures to be permanently and effectively grounded, and FCC/FAA marking and registration obligations can apply to taller structures, especially those above 200 feet or near airports. Most bunker installs will stay well below those thresholds, but the program documentation should still include a tower-height and airport-proximity check so a sales rep never accidentally promises a mast plan that triggers a permitting surprise.

Battery and ESS safety should be treated as part of the communications scope whenever the project includes UPS, solar, or remote power. NFPA 855 exists specifically for stationary energy-storage installations, and OSHA’s lithium-ion safety guidance highlights ventilation, cool/dry storage, monitoring for flammable or toxic gases in larger storage locations, adherence to manufacturer guidance, and designated recycling/disposal pathways. That is directly relevant for bunker communications rooms because the communications layer often becomes the excuse for adding the site’s first always-on battery system.

Transport and export

Portable and remote communications kits usually involve lithium batteries, power banks, or integrated batteries. FAA PackSafe states that spare lithium batteries and power banks must be carried in the cabin, not checked, and PHMSA treats lithium batteries as hazardous materials under DOT rules when shipped in commerce. That matters both for field teams traveling with demo/maintenance kits and for RMA/warranty returns. goKit 2’s airline portability is commercially useful, but shipping and travel SOPs still need explicit lithium-battery handling instructions.

For exports, BIS states that many encryption products can move under License Exception ENC, but only after the exporter handles the applicable classification and reporting requirements, and some destinations or end uses still require licenses. Because goTenna and LoRaWAN deployments both involve encryption, and because goTenna products are increasingly defense-adjacent, the partner program should require vendor ECCN confirmation, destination screening, and restricted-party screening before any international sale.

Supply chain, warranty, returns, and contract structure

Vendor risk is manageable but should not be ignored. Current goTenna pages display a Forterra acquisition banner, and Forterra announced the acquisition in late 2025. That does not automatically create a problem, but it does mean partner contracts should verify support continuity, assignment rights, pricing continuity, and roadmap contacts under the current parent company.

goTenna’s public terms say products can be unavailable or backordered; current U.S. site returns are accepted within 30 days for eligible items in new condition; and the hardware warranty is a limited one-year replacement warranty, with the customer generally responsible for return shipping unless otherwise notified. Those terms should be flowed through in reseller paperwork and should shape your spares policy. In practice, that argues for a program-level spare pool rather than relying on manufacturer turnaround for critical sites.

A concise commercial/legal split looks like this:

Every reseller form should include, at minimum, clauses on frequency-law compliance, permitted use, no unauthorized antenna substitutions, battery shipping rules, RMA workflow, field-safety responsibilities, subcontracted installation standards, customer data handling, parent-company assignment/change-of-control notice, and who owns the monthly managed-service contract.

Go-to-Market, Financial Scenarios, and KPIs

The current public state of AnarchyShelters.com means the partnership should not rely on the existing website as its primary conversion tool. Instead, the fastest credible route is a co-sell launch pack: one joint one-pager, one premium package sheet, one technical site-survey checklist, one customer-facing “communications during grid-down” explainer, one builder/installer playbook, and one pilot case study as soon as the first deployment is commissioned. The shelter-construction sale is already a long-consideration purchase; communications should be sold as a resilience subsystem, not as a gadget add-on.

The best target segments are those where the compliance and value proposition line up cleanly: remote compounds, ranches, industrial retreats, association-run preparedness sites, private security operations, and customers who already think in terms of infrastructure resilience rather than retail electronics. For the broad residential preparedness audience, the default messaging should emphasize LoRa-based telemetry, environmental awareness, and hardened off-grid monitoring, with the goTenna operator layer framed as a higher-tier option subject to professional-use qualification. That segmentation follows directly from the Part 90 issue and the technology fit of each radio layer.

Reference package and cost guidance

Public cost anchors in these ranges include current RAK gateway pricing, RAK solar gateway bundle pricing, and current Starlink Mini kit/service pricing. All goTenna-specific dollar amounts inside these package ranges are planning assumptions because current Pro X2, EdgeRelay, and Pro X2m pricing is quote-based.

Three-year P&L scenarios

The following P&L scenarios are modeled from your company’s perspective, using internal planning assumptions rather than published goTenna list prices.

Model assumptions

These figures are planning assumptions, but they are anchored to the current reality that goTenna pricing is quote-only while gateways and satellite backhaul do have public price anchors.

Referral-first model

This model is the most attractive near-term launch because it minimizes contracting friction and inventory exposure while still giving the partner meaningful incentive. It also creates the cleanest path to learning true attach rate and support burden before committing to broader channel complexity.

Bundled resale model

This model becomes superior only when the partner can consistently create higher volume through construction-time bundling. In other words, the resale model is a scale play, not necessarily a better day-one play.

KPI set

A partnership program like this should be managed with a small, hard KPI set:

The most important reporting habit is to split the business into upfront project margin and recurring service margin. goTenna itself states that its standalone network does not inherently create monthly OPEX; if your reporting does not separate support, monitoring, and backhaul economics from hardware economics, you will not know whether the partnership is creating a durable service business or just moving hardware.

Open questions and limitations

The open issues that remain are not minor:

• AnarchyShelters commercial readiness is not verifiable from its official site right now. The site currently presents placeholder WordPress content, so assumptions about volume, positioning, and trust signals remain open.
• Current goTenna pricing is not public. Exact goTenna numbers in this report are planning assumptions pending vendor quote.
• The goTenna layer for ordinary U.S. consumer/homeowner use needs outside licensing review. The Part 90 fit is much clearer for entity-operated use than for generic consumer retail.
• Export classification is vendor-specific. BIS ENC guidance is relevant, but exact ECCN and destination restrictions still need vendor and counsel confirmation.

The practical recommendation, therefore, is to launch the partnership around a LoRa-first managed infrastructure offer, keep goTenna as a premium qualified-use add-on, and use a referral-first commercial structure until the first pilots produce real attach-rate, install-time, and regulatory-learning data. That is the tightest fit to the current evidence.