CASE STUDY / XUREMI NET

Solving the MikroTik captive-portal DNS problem

Xuremi Net was built across 11 phases as a hotspot billing system for real-world, low-friction access control. The hard part was not just payments or billing logic; it was making the portal itself reachable before authentication, when normal DNS and routing assumptions break down.

THE PROBLEM

Portal reachability before login

The login page had to be served in a state where the client had not yet passed the captive portal. That meant the system could not rely on ordinary internet access, which is exactly why DNS resolution and page loading became unreliable in the first place.

THE FIX

Serve the portal from the router itself

The portal login page was served directly from the MikroTik router file system, with Walled Garden whitelisting used to keep the necessary assets reachable before auth. That removed the dependency on external resolution at the worst possible moment.

ENGINEERING JUDGMENT

Debugging the real constraint

The important move was to diagnose the actual failure mode instead of treating it like a generic frontend problem. Once the portal, the router, and the captive flow were aligned, the system became much more stable in production.

RESULT

A working billing flow under network constraints

The final system combined hotspot billing, payment handling, and router control in a way that held up in the field, which is why the project is useful as a proof of systems thinking rather than just a tech-stack list.

Back to home