SPECIAL DOMAIN

WiFi platforms & captive portals

Captive portal → RADIUS stack → authentication → payment integration → multi-site aggregation. Specialist area, twenty years deep.

WiFi authentication for train stations, ports and city centres — from the captive portal UI to RADIUS aggregation across multiple sites.

When this pattern fits

Three pain points where the effort pays off.

  1. Standard captive portals cover the mass use case — special situations need deep intervention.

  2. FreeRADIUS and friends hit their limits as soon as multi-site roaming, sub-contracting or custom tariff logic come up.

  3. Hardware stacks and customer branding should not collide — and operations should stay with the network partner.

How the pattern is built

Five steps, from input to filing.

  1. Captive portal

    Branded, multilingual, locally adapted.

  2. RADIUS stack

    Custom aggregator where needed.

  3. Authentication

    VIP classes, vouchers, roaming.

  4. Payment

    Card, voucher, tariff logic.

  5. Multi-site

    Seamless transition between sites.

Live example

From real operations.

Customer Deutsche Bahn AG WIFI & CAPTIVE PORTALS

Surfing on the ICE on the move, then carrying on in the station WiFi at the next stop without signing in again — under the hood that's a RADIUS aggregator we built for Deutsche Bahn, and it works where standard RADIUS servers (FreeRADIUS and friends) hit their limits.
See the case

What is deliberately out of scope

Three places where we leave it to a person.

  • Custom hardware. We deliver adaptations on existing infrastructure, not a second server stack.

  • Operations 24/7. The network partner runs the service; we develop and hand over.

  • A generic SaaS WiFi platform. Every pattern is tailored to your site — by design.

What the pattern covers

From the login screen to multi-site aggregation.

  • Captive-portal interfaces with site-specific branding and multi-language support.

  • RADIUS authentication — custom stacks where FreeRADIUS and friends hit their limits.

  • Payment and tariff logic embedded into the portal, integrated with existing billing systems.

  • VIP and class differentiation for transport operators and hospitality.

  • Multi-site aggregation: seamless roaming between train, station and city centre.

  • Operations hand-over to the network partner — no second hardware estate.

Why evanto

Twenty years of captive-portal experience — from Regensburg to Dakar.

WiFi authentication is not a field one picks up on the side. We have been building captive portals for hospitality, transport operators and city centres since the early 2000s — from Deutsche Bahn through Monaco Telecom to TER Dakar in Senegal. Where standard stacks hit their limits, we know the way through.

Typical project scope

Discovery → pilot → rollout.

  1. Discovery

    One to two weeks. We understand your concrete bottleneck, look at the available sources and decide together whether the pattern is really the right answer here.

  2. Pilot

    Four to eight weeks. A scoped variant on real data, with a small user group. Dry-run before every write, clearly defined success criteria.

  3. Rollout

    From two months onwards, fluid. Extension to further sources, teams or sites. Hand-over to operations with documented architecture and training for those responsible.

Talk to us

Two doors, one address.

Specific bottleneck?

Let us talk for 30 minutes about your use case.

No obligation, no cost, with concrete next steps at the end.

Book a 30-minute call

Your own AI platform?

See CompanyWizard live in action.

Demo with your own data is possible. We bring the pseudonymisation set up and ready.

Request a demo