Compact hardware for field integration.
A 90 × 30 × 10 mm enclosure with Micro-USB power and over-the-air configuration, designed for remote asset deployments.
90 × 30 × 10 mmMicro-USB poweredOTA configurationSatellite-ready IoT
Remote asset connectivity
Know what is happening beyond coverage.
GorillaLink combines compact field hardware with live location access and device-level visibility—so remote assets become part of an operational workflow, not another disconnected device.
Compact hardwareLive map accessDevice usage visibility
One practical deployment pathFrom the field asset to the team operating it.
ConnectCompact edge hardware
LocateLive map workspace
OperateDevices and monthly data
Track and manage remote assets from one connected service.
GorillaLink combines location tracking with device, activation and data-usage management—giving customers a clear operational view of their remote fleet.
See the asset in context.
Open the GorillaLink map workspace to view the location layer used by field teams.
Open Live Map ↗Manage the fleet behind the map.
Review device activation, status and monthly data consumption from a separate customer workspace.
Open Device Portal ↗Start with the operational problem.
Each deployment begins with the asset, its operating area and the decision the reported data needs to support.
Remote asset monitoring
Evaluate remote equipment visibility.
Use the pilot to determine which asset data is required, how often it must be reported and what operational decision it should support.
1Define the asset and required message
2Confirm installation and power constraints
3Measure reporting performance in the field
Pilot inputAsset type
Operating areaCustomer defined
Reporting cadenceTo confirm
Success metricDocumented
Maritime tracking
Test the reporting need offshore.
Define the vessel or equipment, operating area and reporting cadence before the pilot begins.
1Define the target vessel or equipment
2Map the intended operating area
3Agree the required tracking interval
Pilot inputVessel or equipment
Operating areaDefined during scoping
Tracking intervalConfigured per pilot
Success metricDocumented
Industrial IoT
Assess fit with the existing device.
The product sheet lists industrial IoT as a target use case. Interfaces, message format and production requirements are confirmed during technical discovery.
1Document the existing equipment interface
2Define the required data and cadence
3Confirm production constraints
Pilot inputDevice interface
Message formatTo confirm
PowerMicro-USB
ConfigurationOTA
Government deployments
Scope requirements before evaluation.
Procurement, security, certification and operating requirements are defined for each deployment.
1Document operational requirements
2Identify security and certification needs
3Agree the evaluation process
Pilot inputMission requirement
EnvironmentDefined during scoping
ComplianceReviewed per deployment
Success metricDocumented
Proof before scale
Make the pilot measurable.
Every deployment is different. Define success before installation and leave the pilot with evidence for the rollout decision.
Scope a pilot ↗Message success
Measure whether the required field message arrives under real operating conditions.
Installation effort
Track installation time, configuration steps and ongoing field workload.
Required output
Confirm the destination and format the customer's operational workflow requires.
Value per asset
Compare the evaluated connectivity cost with the operational problem being addressed.
A commercial path that matches the risk.
Start with a bounded evaluation, move to a fleet quote only after technical fit is demonstrated, and align ongoing service with the real data profile.
Pilot
One defined use case, a limited asset group, an agreed evaluation period and measurable acceptance criteria.
Priced to scopeDeployment
Hardware quantity, onboarding, configuration and rollout support are quoted for the approved fleet.
Volume quotationOperations
Connectivity, portal access and support are aligned with device count and the expected monthly data profile.
Recurring servicePILOT DECISION PACK
What the pilot decision pack contains.
A consistent report makes the move from evaluation to rollout easier to approve.
Field delivery evidenceInstallation and configuration recordMonthly data profileScale recommendation and open risks
Final pricing, service levels and commercial terms are confirmed in writing after technical discovery.
Why GorillaLink.
A focused path from a remote asset problem to a deployment decision—without hiding the questions that still need field validation.
01
One operating picture
Hardware, live location access and device-level usage are presented as parts of the same customer workflow.
02
A measurable pilot
Agree the asset, region, reporting need and success criteria before equipment goes into the field.
03
A clear scale decision
Use field evidence to assess technical fit, operating effort and value per asset before a wider rollout.
What is confirmed today.
Published product facts are separated from production requirements that must be approved for each project.
Product
GorillaLink Edge Dongle PUBLISHED
Product type
Satellite-ready IoT board PUBLISHED
Enclosure
90 × 30 × 10 mm PUBLISHED
Power
Micro-USB powered PUBLISHED
Configuration
Over-the-air configuration PUBLISHED
Production readiness
Interfaces, coverage fit, environmental requirements, security controls and certifications PROJECT-SPECIFIC
Before you deploy.
The first technical discussion is designed to answer the questions that determine whether a field pilot is worth running.
What is already defined?
The Edge Dongle is positioned as a satellite-ready IoT board in a 90 × 30 × 10 mm enclosure, with Micro-USB power and OTA configuration.
What does GorillaLink need from us?
The asset type, operating area, required message, reporting cadence, installation constraints and approximate fleet size.
What is confirmed during technical discovery?
Interfaces, environmental requirements, coverage fit, certifications, security expectations, availability, pricing and production service levels.
How is pricing structured?
The engagement starts with a scoped pilot. Fleet pricing then reflects hardware quantity, onboarding needs, device count and the expected data profile.
What should a pilot produce?
A documented result covering message delivery, installation effort, required output and the business value per connected asset.
Field evaluation
Bring us the asset problem.
Tell us what needs to report, where it operates and what decision the data should support. We will use that brief to frame a focused technical discussion.
1Define asset, region and reporting need
2Confirm hardware and deployment requirements
3Agree measurable pilot criteria