Hotel
Room-based access with sessions limited to the length of stay. With front-desk integration, access opens at check-in and closes at check-out. The welcome page runs in the hotel’s branding and the guest’s language.
Guest networks for offices, hospitals, hotels and private companies: a solid firewall, correct configuration and lawful, protected logging. A setup that gives your guests internet without leaving your corporate network exposed.
Scope is narrowed or widened to suit the venue. Exactly which headings are included is written out, one by one, in the quote.
SMS, national e-government identity or social login. Which one fits is decided together, based on venue type and guest profile.
Who connected, when and from which device — every session is recorded with a timestamp and tied to the verified user identity.
Records are signed and stored so they cannot be altered afterwards. Integrity verification is what matters the moment a record is requested.
Records are kept for the period the regulation requires; the period, the responsibility and the access rights are defined in writing at setup.
A guest device cannot see the accounting machine, the printer or the server. Separation is built with a managed VLAN structure, not with physical cabling.
Which network may reach which resource is written rule by rule. The default is deny; every permitted path is documented with its rationale.
Device configurations are backed up and changes are versioned. When a rule changes, it is clear when, by whom and why.
Guest traffic is capped so it cannot affect corporate traffic. Critical applications get priority, and a single download cannot saturate the line.
Category-based filtering is applied according to your policy and venue type. Domains known to distribute malware are blocked separately.
Session lifetime, re-authentication interval and concurrent device limits are tuned to your venue — length of stay in a hotel, working hours in an office.
The welcome page carries your logo, colours and languages. Campaign announcements or internal notices can be delivered on the same screen.
How many access points are needed is calculated from floor plans, wall structure and concurrent user counts. Coverage gaps are identified before installation.
Alerts fire when an access point drops, the log stream stops or traffic looks abnormal. The point is to see the problem before a guest complains.
Four questions about the internet you hand to visitors. If nothing looks wrong, we will tell you that too.
In Türkiye, venues offering public internet access fall under Law No. 5651, which requires access records to be kept, retained for a defined period and protected against tampering. A consumer router’s guest network does not meet that obligation.
Verified user identity, connect and disconnect times, device identifier and session details. Access records are kept — not the content of the pages visited.
Records are stored timestamped and signed. The point is that a record can be shown, when needed, not to have been altered afterwards.
The people allowed to reach the records are defined in writing at setup. Access requests are themselves logged — it is clear who viewed a record.
For the period the regulation requires. The period and the retention responsibility are set out in the contract; if the regulation changes, the configuration is updated.
What you get at the end is not just working wifi but a written record of what is logged, how it is stored and who can access it. That document is exactly what an inspection asks for. For venues that want the whole network surface reviewed, a cyber security assessment is offered as a separate scope.
Each step has a defined output. When the work is done, you hold the map of your own network.
Floor plans, wall structure, existing cabling and concurrent user counts are mapped. How many access points are needed, and where they go, is settled here.
Guest, staff and any special device networks are split into separate segments. Which segment may reach which resource is defined in writing.
Rule sets are applied, the hotspot and captive portal go live, and bandwidth quotas and content filtering are configured. The welcome page is built to your brand.
The user verification method goes live; access logging, timestamping and signed retention are tested end to end. Access rights are defined in writing.
Access point health, log flow and traffic patterns are monitored and alert rules are set. Configuration changes are managed with versioning.
Guest experience leads in a hotel, device isolation in a hospital, protection of corporate resources in an office. The deployment is designed around that priority.
Hotel
Room-based access with sessions limited to the length of stay. With front-desk integration, access opens at check-in and closes at check-out. The welcome page runs in the hotel’s branding and the guest’s language.
Hospital
Patient, staff and visitor networks are kept apart, and the medical device network is isolated in its own segment. Clinical systems are unreachable from the guest side, and critical traffic is prioritised.
Office and private company
Staff device policy, visitor guest access and protection of corporate resources are designed together. File servers, accounting systems and printers are invisible from the guest network; staff access is defined by role.
Businesses that want to hand over network and systems as a whole combine this deployment with the outsourced IT support package: monitoring, alert handling and hardware maintenance all run under one roof.
Legal logging compliance is not a one-off installation but an obligation that has to run without gaps, so the service is delivered on a 12-month agreement: deployment, log retention, monitoring and maintenance scope are written into the contract, and the agreed fee does not change during the year. At year end, device count, log volume and scope are reviewed together and the agreement is signed again — nothing extends automatically, and continuing is your decision.
No. What is kept is an access record: verified user identity, connect and disconnect times, device identifier and session details. The content of the pages visited is not recorded. Where content filtering is applied, the blocked category may also be logged; that is agreed in writing at setup.
For the period the regulation requires, with integrity preserved. The retention period, the retention responsibility and who may access the records are defined in writing at setup. If the regulation changes, the configuration is updated accordingly.
SMS, national e-government identity or social login can be used. Which one fits depends on venue type and guest profile: SMS often suits a hotel with mostly international guests, while e-government identity is more practical for organisations working with the public sector.
It is not. Guest mode on a consumer device usually just shares a password; it does not provide verified identity, timestamped access records or tamper-evident retention. For venues offering public internet access, that is exactly what is required.
Most enterprise-grade devices are compatible. After the site survey and inventory, we report what can stay and what needs replacing due to capacity or lack of firmware support. We do not recommend hardware changes you do not need.
Bandwidth quotas and traffic prioritisation keep guest traffic from affecting corporate traffic. VLAN separation also means a problem on the guest side does not spill into the corporate network.
From a small office to hotel and hospital deployments with hundreds of concurrent users. Access point count and placement are calculated in the capacity plan from concurrent user density.
It depends on the state of the existing infrastructure. A firm schedule follows the site survey; most office deployments finish in a single day. In multi-floor hotel and hospital installations, cabling and coverage work drive the timeline.
Fill in the form and we will get back to you within 1 business day on the channel you choose. Your details are used only for this conversation.
For hotels, hospitals, offices and other public-access venues, giving guests internet is not only technical but a legal obligation. In Türkiye, Law No. 5651 requires access logs to be kept, retained for a defined period and protected against tampering.
A consumer router's guest network does not meet that. Our hotspot service sets up user verification, log recording, timestamping and signed retention together.
The guest network is separated from the corporate network with VLANs — a guest device cannot reach the accounting machine. Firewall rule sets and config management sit with us; bandwidth quotas, content filtering and session policies are tuned to your venue.
Room-based access with stay-limited sessions in hotels, patient/staff/guest separation in hospitals, and device policy in offices. The captive portal is branded to you.