A licensed software stack, ewusOS, running across several hardware tiers, for PGs and hostels, coaching institutes, small businesses and regional internet providers. Nothing here is on sale yet.
Most PG and hostel owners, coaching institutes and small businesses run whatever router their ISP handed over. That device is usually locked down: no configuration control, no local‑language support, and if it fails there is little to do beyond calling the ISP and waiting. Separately, most managed WiFi platforms sell software on top of someone else's hardware. We design the hardware specification and the software together, as one stack, sourced through OEM and ODM partners we hold to it, for the segment stuck between “ISP box you cannot touch” and “enterprise gear you cannot afford.”
How long a device keeps getting updates, stated plainly rather than left vague.
The eighteen‑month figure reflects the industry pattern most consumer networking gear is abandoned within. Ten years is our own update commitment, detailed further down this page under “What we commit to.”
The connectivity engineering discipline underneath everything else on this page: designing, configuring and supporting the network itself, not just selling a box.
Per‑room or per‑floor control, without needing an IT person on site.
Guest and staff networks kept separate, with visibility into what is actually happening on the network.
CPE that can be configured and supported at scale, instead of a black box shipped once and never touched again.
ewusOS is the single gateway operating system that runs across every hardware tier we ship. What changes segment to segment is which module is licensed on top of that same core, not the underlying software. Full technical depth lives at ewus.io/platform.
The Home segment product, built on the same ewusOS core as every other tier.
One product serving both segments: per‑resident identity for property, role‑based access for campus.
The Business segment product, for networks that need threats stopped early.
The Provider segment product, for regional ISPs running subscriber‑scale networks.
Every gateway we ship talks to one backend, EWUS Cloud, for resolved configuration, policy and telemetry. It is what makes the “fails open, never shut” commitment possible: the gateway keeps the last good configuration and keeps enforcing it locally, so if EWUS Cloud is ever unreachable, the customer sees paused cloud features, never a dead connection. This is our own product infrastructure, built to run the gateways we sell. It is a different thing from the cloud deployment work we do for Technology Services clients on their own AWS, Azure or GCP accounts, see Cloud Deployment and DevOps for that.
We do not manufacture hardware ourselves. Devices are sourced through OEM and ODM partners, and certification is a requirement we hold every one of them to before a device ships under an EWUS product name, not something we claim on their behalf.
