Request a quote WhatsApp

16 September 2026 · 8 min read

What Is a 5651 Logging Appliance? How to Choose the Right Solution

Compare physical logging appliances, virtual servers and cloud-managed services across deployment, maintenance, scalability, audit readiness and total cost.

When an organisation searches for a “5651 logging appliance”, it is rarely looking for a box alone. It needs an end-to-end evidence chain: identify the guest, associate the session with the correct person and device, collect network records, protect integrity, apply timestamping, retain data securely and export a clear package when required.

The decision should therefore not be based solely on CPU, disk size or purchase price. Network topology, site count, visitor volume, existing firewall and wireless vendors, retention policy, operational capacity and expected audit outputs must be assessed together.

This guide supports technical procurement and is not legal advice. Confirm your obligations and retention policy with qualified legal counsel.

What is a 5651 logging appliance?

The term covers several deployment models: a physical server or network appliance installed on-site, software deployed on existing virtual infrastructure, or a centrally managed service supported by a local collector. Regardless of form, a complete solution should address:

  • Guest or user authentication
  • Association of user, IP address, device and session time
  • Collection from firewalls, controllers and gateways
  • Integrity controls using hashes, signatures and timestamps
  • Protection against unauthorised alteration
  • Search by date, user, IP, location or device
  • Export of records for a selected period
  • Retention, capacity and service monitoring

A device that merely receives syslog and writes files to disk is not equivalent to a system that manages authentication, session correlation, signed archives and audit exports together.

Physical, virtual and cloud-managed options

CriterionPhysical applianceVirtual server / softwareCloud-managed service
Initial setupHardware, power and network connection on-siteExisting virtual infrastructure requiredCan start quickly with a local connection or collector
ScalingDisk or appliance replacement may be neededVirtual resources can be increasedService tier and retention can scale
UpdatesLocal team or maintenance agreementShared between customer and providerCentrally managed
Multiple sitesSeparate architecture may be required per siteCan consolidate centrallySuited to single-panel, location-based management
Connectivity lossLocal collection may continueDepends on architectureLocal buffering must be verified
Hardware failureReplacement and backup plan requiredDepends on virtualisation resilienceProvider continuity design must be assessed
Total costHardware, disk, warranty, power and maintenanceLicence, server resources and operationsSubscription, retention and local components

No model is universally correct. A single facility with limited connectivity may prefer local infrastructure. A chain managed by one team may prioritise central policy, delegated access and standardised reports. In every case, verify that records survive connectivity interruptions and transfer securely when service returns.

Twelve questions to ask before buying

  1. Which sources are supported: firewall, wireless controller, access point, DHCP, RADIUS and captive portal?
  2. Is integration verified for our exact models and software versions?
  3. How are users associated with sessions through SMS/OTP, room credentials, vouchers, sponsor approval or accounts?
  4. How are the portal, network equipment, logging system and time source synchronised?
  5. How do hashing, signing, timestamping, packaging and verification work?
  6. What happens when internet or central connectivity is unavailable?
  7. How is capacity calculated from actual daily event volume and retention policy?
  8. How quickly can staff search and export by date, IP, user, MAC address and location?
  9. How do role-based access, location separation and administrator audit trails work?
  10. How are backups, restore tests and disaster recovery handled?
  11. Who owns software updates, certificate renewal, integration changes and incident response?
  12. Which items—installation, SMS, timestamping, storage, additional sites and custom integrations—are priced separately?

Capacity planning

Storage cannot be estimated from user count alone. Two organisations with the same visitor count may generate very different volumes because of firewall policy and event detail. A practical estimate includes site and internet gateway count, daily unique and concurrent users, session length, source event types, peak-hour volume, retention policy, signed archive and backup copies, and growth allowance.

The strongest approach is to sample the real network, measure daily volume and include a peak-period margin. Low-season data alone can be misleading for hotels, exhibition centres and marinas.

What should an audit-ready export answer?

A strong system should answer:

  • Which user was connected at the requested date and time?
  • Which IP address was assigned?
  • Through which location, SSID or gateway did the session pass?
  • When was the record collected and archived?
  • How can archive integrity be verified?
  • Who searched for or exported the record?

During a demonstration, select a random date and user and run this workflow end to end. The result should be readable, exportable and verifiable by an authorised person.

Authentication is part of the decision

Network records lose operational value when they cannot be matched to the correct user and session. Captive portal and logging should not be assessed as disconnected products. Depending on the organisation, authentication may involve SMS one-time codes, national identity plus SMS, PMS room number and surname, reception-issued vouchers, employee or sponsor approval, API + OTP through a mobile application, or a recognised returning user.

Marketing consent should be handled separately from actions required to access the network. See the privacy notice and consent guide for further detail.

Verifying network compatibility

A generic “works with every vendor” claim is not enough. Document the wireless controller or access point model and version, firewall model and version, RADIUS/syslog/API/captive portal redirect/CoA support, VLAN and SSID design, DHCP location, NAT source and high-availability topology.

HotSpot can be integrated, depending on project scope, with wireless environments such as Ruckus, Cisco, Aruba and Meraki and firewall ecosystems such as Fortinet, Palo Alto, Sophos and MikroTik. Exact model and version compatibility is confirmed during technical discovery. See the current integrations page.

Total cost of ownership

The lowest appliance or licence price is not always the lowest total cost. Compare subscription or licence metrics, hardware and warranty, installation and network work, updates and monitoring, SMS and timestamp services, custom integrations, growth, backup and data-exit requirements over a three-year period.

Cost areaWhat to check
Licence / subscriptionPer user, location, device, traffic volume or storage?
HardwareAppliance, disk, backup power, rack space and warranty
DeploymentRemote setup, on-site survey, network changes and testing
OperationsUpdates, monitoring, backups and capacity management
External servicesSMS, timestamping, email and private connections
IntegrationPMS, database, mobile app or API work
GrowthNew sites, longer retention and peak-season capacity
Exit planStandard data export and service transition

HotSpot pricing is provided in writing according to site count, active users, log volume, retention needs and integration scope. Review the pricing scope or request a proposal based on your environment.

  1. Discovery of sites, internet exits, network equipment, authentication methods and volume.
  2. Architecture covering local, virtual or central deployment, interruption and redundancy.
  3. Pilot on one site or a limited SSID.
  4. Validation of time synchronisation, IP correlation, signed archive and sample export.
  5. Rollout using standard templates and delegated access.
  6. Handover of permissions, operating procedures, backup and support responsibilities.
  7. Periodic testing for missing events, capacity, time sources, certificates and exports.

Do not declare the pilot successful merely because the portal opens. Validate the chain from the test user's login through to search in the signed archive.

Quick decision summary

Before choosing a physical appliance or managed service, confirm in writing that the solution collects required records from existing equipment, correctly correlates identity/IP/device/location/time, documents integrity and timestamping, tests interruption/backup/capacity/export scenarios, and makes the full three-year cost visible.

Explore the HotSpot 5651 logging workflow or request a demonstration and proposal for your current network.

Frequently Asked Questions

Is a physical appliance mandatory for 5651 logging?

No. A solution can be physical, virtual or centrally managed. What matters is a working chain for collection, integrity, retention and authorised access that matches the organisation's architecture and obligations. Confirm legal scope with counsel.

Is firewall logging alone sufficient?

A firewall is an important source, but authentication, IP/session correlation, integrity, timestamping, retention, search and audit export must be assessed together. Technical discovery determines which parts the current firewall covers.

Will cloud-managed logging lose records during an outage?

That depends on design. A local collector can queue events and transfer them when connectivity returns. Buffer capacity, retry behaviour and loss alerts should be tested.

What determines price?

Site count, concurrent users, daily event volume, retention, integrations, SMS and timestamp use, resilience and support scope all affect price. A written proposal based on real network data is more reliable than a generic package.

Must existing access points and firewalls be replaced?

Not necessarily. Compatibility depends on model, software version, protocols and topology. Discovery identifies which existing components can remain.

What should we test in a demo?

Authenticate a real test user, verify user/IP/device/location/time correlation, search the signed archive and export the selected period. Also ask about connectivity loss, incorrect time and capacity-alert scenarios.

Let’s simplify your guest Wi-Fi journey

Keep your existing infrastructure and bring access, engagement and 5651 records into one panel.

Request a Free Demo

We use cookies for visit statistics. Cookie policy