Xpresso · 1 slot
Run UAC for guest access or a dedicated monitoring role, one at a time. Both role options are included.
NetCollab solutions
Find the right approach
for your network.
A better guest experience. A fairer way to share connectivity. A clearer starting point for troubleshooting. Explore how NetCollab fits your situation.
01
Cafés & restaurants
Welcome guests with branded access, time limits and vouchers that fit their visit.
Explore this solution 02Event venues
Prepare access plans before arrival, welcome guests, and learn from the event’s traffic.
Explore this solution 03Satellite & remote
Prioritize useful access and offer different tiers when connectivity is limited or shared.
Explore this solution 04IT troubleshooting
Use traffic evidence, targeted reports and active tests to decide where to investigate next.
Explore this solution01 For owners and operators
Guest Wi-Fi with boundaries that fit your business.
Give customers a useful connection while keeping complimentary access fair. Build the Wi-Fi offer around your service, your guests and the bandwidth you have.
Make the first connection feel like your venue
Welcome guests through a portal with your logo, colors and access choices. Present the offer clearly before they connect.
Set a fair complimentary allowance
Combine access duration, speed and data limits with application policies. Offer 30 or 60 minutes of free access, for example, rather than leaving every session unrestricted.
Let access follow the visit
Provide a voucher with a purchase, or offer additional paid access through Stripe. Your team can issue vouchers as part of service; no checkout-system integration is assumed.
What fits this setup
Use the Guest Wi-Fi & Captive Portal role (UAC). NetCollab manages access policies; your access points and internet connection still determine coverage and available capacity.
02 For venues and event teams
Guest Wi-Fi planned around your event.
A wedding, winery gathering or conference brings different expectations to the same network. Prepare a clear access offer before the event, then use the available reports to understand how it was used.
Before: build the offer
Create plans with durations, allowances and policies suited to the event. Prepare portal branding and vouchers, and size the deployment around expected simultaneous users.
During: make access straightforward
Show guests the plans available to them through the portal. Offer complimentary access, vouchers or paid upgrades as appropriate, and review available activity in Central.
After: use the evidence
Review traffic and application reports to inform the next event’s plans. Separate access-policy decisions from changes needed in Wi-Fi coverage or internet capacity.
What fits this setup
Start with UAC for guest access. If you also need dedicated observation points, size the monitoring roles and slots separately. Event capacity depends on hardware, access points and the upstream connection.
03 For remote venues, camps and maritime operators
Make shared bandwidth go further.
When one connection serves many people, the access offer matters. Give guests a practical starting point, limit bandwidth-heavy activity where needed, and make broader access a deliberate choice.
Start with essential everyday access
Create a complimentary tier for supported messaging and map services. Choose the permitted applications and categories around the needs of your users.
Match each tier to the connection
Combine speed, data-volume and time allowances. Restrict software updates, ads or streaming where they would consume capacity needed by other guests.
Offer more access on clear terms
Offer broader access or higher allowances through another tier. Use the reports to refine your policies as demand changes.
What fits this setup
Place NetCollab’s access role in the local network serving your access points. Local policies manage usage; they do not increase provider capacity or remove satellite latency, weather effects or provider restrictions.
04 For SMB IT personnel
Turn “the network is slow” into a focused investigation.
Start with the affected facility, time and traffic path. Use a transparent L2 monitoring node to analyze the traffic crossing that point, then explore the resulting statistics and diagnostics in Central.
Place the observation where it helps
Monitor between a router and switch, between segments, or before a web, email or ERP server. The bridge sees traffic crossing that link; choose placement around the problem.
Narrow the investigation
Inspect applications, response behavior, TCP indicators and QoX. Schedule a detailed report for a selected node and time window, filtering by protocol, category, IP or MAC to keep the evidence manageable.
Add active tests and node health
Use ICMP, DNS or UDP tests to examine the relevant path. Check node telemetry alongside the results to understand resource and processing pressure before drawing conclusions.
What fits this setup
Use a monitoring role plus Central for reporting and diagnostics. NetCollab generates statistics from packet analysis; it does not retain packets or export PCAP files. Measurements guide investigation rather than guaranteeing a root cause.
Build around your needs
One platform. Choose the roles and room you need.
Guest access and dedicated monitoring are both included with NetCollab hardware. Slots determine which roles you can run at the same time; Central is a separate management and reporting product.
Pro · 4 slots
Confirmed examples: one UAC with three monitoring roles, or four monitoring roles for different observation points.
Central · cloud or local
Bring management, APIs and reporting together. Each node purchase includes three months of Central Cloud and technical support. Ongoing Cloud plans include support; private Central deployments are quoted separately.
A few practical questions
Can my business fit more than one solution?
Yes. A remote café may need both fair guest access and policies for a constrained connection. Use the sections together, then choose the node roles and slots for your deployment.
Does NetCollab replace my Wi-Fi access points?
No. It works in the network around your access infrastructure. Plan radio coverage and upstream capacity alongside access policies and monitoring.
Will I need separate software purchases for the two node roles?
Both role options are included with the appliance. Hardware slots govern concurrent use. Central is separate; discuss its cloud or local offer for your needs.
Start with your situation
Tell us what your network needs to do.
Bring your use case, expected users and connection constraints. We can discuss the roles, hardware and Central deployment that fit.