assetwolf.com

What It Is

AssetWolf is an IoT device data portal from Tribal Ltd. It is not positioned as a simple MQTT broker, but as an integrated platform covering device ingestion, real-time processing, and customer-facing portal display. It supports data from LoRaWAN, WiFi, cellular, Ethernet, and HTTP/MQTT devices, and is suitable for aggregating sensor data such as temperature, vibration, motion, soap dispensers, and activity levels for alerts, reports, heatmaps, and operational analytics.

Core Capabilities

At the ingestion layer, AssetWolf supports LoRaWAN and mentions an included ChirpStack dashboard for device management. WiFi, Ethernet, or cellular devices can connect directly to the broker via MQTT, or submit data through REST GET requests. Supported data formats include LoRa base64, single-field requests, JSON, and XML. The platform can also periodically pull data from third-party platforms that provide APIs. Device schemas are used to define fields, metadata, and real-time calculated fields, with field types covering floats, integers, booleans, text, and geolocation coordinates.

The processing layer centers on the Phi IoT scripting language, which can be used for application-specific calculations, rule processing, metric computation, and data cleaning. Alerts can be based on simple thresholds or defined with more complex conditions using Phi scripts. The presentation layer includes real-time charts, activity heatmaps, custom dashboards, schematics, and B2B customer portals.

API, Documentation, and Pricing

The documentation is fairly extensive, covering REST, MQTT, Secure MQTT, QoS, two-way MQTT, timestamps, batch payloads, Arduino examples, alerts, MQTT Monitor, the Phi Cookbook, and more. The API documentation is mainly protocol-oriented, and no standalone SDK was found. One important point is that the documentation describes REST connections as currently password-less and non-SSL, recommending them only for development and testing; for production, Secure MQTT or additional security measures should be evaluated first.

Pricing is typically £2 per asset per month, with a minimum of £100/month. Implementation fees may apply, a limited-time trial may be available, and prices exclude VAT. Costs are predictable for small and mid-sized commercial projects, but it is not especially cheap for very small prototypes.

Pros, Cons, and Who It’s For

Its strengths are practical ingestion protocols, a complete feature set for IoT scenarios, engineering-oriented documentation, and built-in customer-facing visualization and alerting. The drawbacks are that key information such as open-source vs. closed-source status, self-hosting options, SLA, data residency, and payment methods is not disclosed, and security details also need to be confirmed during pre-sales. It is best suited to industrial IoT, building facilities monitoring, B2B device service providers, and system integrators. If you only need an open-source self-hosted solution, compare it with ThingsBoard, ChirpStack, or EMQX; if you are already in a cloud ecosystem, compare it with AWS IoT Core or Azure IoT Hub.

Access from China

The crawled text contains no information about access from mainland China, payment support, or local nodes, so the status is unknown. For deployment in China, it is recommended to test domain connectivity, MQTT port reachability, cross-border latency, and the GBP/VAT payment process.