A consistent first connection
Give users a clear access path aligned with the organisation, venue and service policy.
Subscriber productsIllustrative operational view · not live customer data
Neurix Captive Portal
Make the first connection clear, branded and operationally governed.
Create captive access journeys that connect brand experience, user acknowledgement, authentication and service policy across managed Wi-Fi environments.
Deployment and support scope are confirmed during discovery.
06Active portal journeys
02Draft changes awaiting approval
01
Portal presented
02
Acknowledgement recorded
03
Authentication handed off
04
Access result returned
What it is
Captive Portal
Neurix Captive Portal is the user-facing access layer for managed hotspot services. It helps organisations present an approved branded journey, collect the minimum required access information or acknowledgement, connect to supported authentication methods and pass the resulting context into hotspot operations.
Approved terms and data choices
Present the required acknowledgement or consent language for the agreed access workflow.
Portal context connected to support
Keep the access journey tied to the site, authentication method and managed session where supported.
Capability set
Built around the work operators need to complete.
Final coverage depends on the agreed environment, integrations, device support and delivery scope.
Branded portal journeys
Configure approved names, colours, copy and journey steps for relevant organisations, venues or tenants.
Terms and acknowledgement
Present the required acceptable-use, privacy or access acknowledgement before service is granted.
Authentication handoff
Connect the portal to supported voucher, account, RADIUS or approved identity workflows.
Site-specific experiences
Assign appropriate journeys to managed sites, service zones or tenant contexts.
Responsive access interface
Deliver a journey designed for common mobile, tablet and desktop browser sizes.
Operational change control
Govern who can publish portal content and policy changes across managed environments.
Operating model
A clear path from signal to action.
Neurix keeps each stage visible so different teams can work from the same operational context.
- 01
Design
Define the required journey
Agree branding, access steps, terms, data fields and the authentication outcome. - 02
Assign
Connect the journey to a service zone
Map the approved portal to the relevant gateway, site, tenant and hotspot policy. - 03
Access
Guide the user through authentication
Present the journey and hand the approved result to the supported managed-access workflow. - 04
Maintain
Review content and operational fit
Keep portal language, policy links and administrator ownership current as requirements change.
Who it helps
Shared context for the teams responsible for service delivery.
Enterprise and hospitality teams
Deliver an appropriate guest or managed-user access experience across sites and properties.
Brand and compliance owners
Review approved content, acknowledgements and data fields before publication.
Network and support teams
Connect the user-facing journey to the access and session context needed for support.
Deployment and fit
The portal is one stage of the complete network access flow.
Implementation confirms gateway redirection, TLS and domain requirements, authentication handoff, policy links, data fields, retention and the experience shown when access cannot be granted.
Scope considerations
- Brand and tenant variations
- Mobile-responsive journeys
- Approved authentication methods
- Governed publishing workflow
Legal language, consent requirements and privacy obligations must be reviewed by the customer for the jurisdictions and user groups in scope.
Product FAQ
Questions to answer before implementation.
Can each venue have its own branding?
Yes, site or tenant variations can be planned within an approved design system and administrator permission model.
Does the portal itself provide internet access?
No. The portal guides the user through the access journey. The gateway, authentication service and hotspot policy determine whether a managed session is established.
Can users accept terms before connecting?
An acknowledgement step can be included. The customer remains responsible for approving the legal language and determining whether additional consent or identity verification is required.
Can it connect to an existing RADIUS service?
Existing RADIUS and gateway integration can be assessed. Attribute mapping, redirect flow and session accounting must be validated for the target environment.
Plan the right scope