Delivery day · 00 of 20 adopted
Twenty boxes land on a Monday. Somebody has to adopt each one, put it on the right VLAN, push firmware and write down which port feeds which room — before the office opens on Wednesday.
Rezolva has designed, supplied, installed and managed tp link omada networks for Singapore offices, shops and small chains since 2012. This page is the part nobody quotes for: the adoption run, and the controller decision behind it.
Adoption decides whether the estate is manageable a year later. Done properly it is boring; done on the floor with people waiting, it is why nobody remembers which access point serves meeting room 4. An omada tp link estate that skipped this step still works; it just cannot be changed without a site visit.
The only choice on this page that is expensive to reverse: it is tied to how many sites you run, how many devices you will own, and who logs in.
In every case the omada controller manages configuration, not traffic, so the network keeps forwarding if it disappears.
| Controller | Runs on | Published device capacity | Where it fits |
|---|---|---|---|
| Software controllerFree on-premises install | A Windows or Linux machine you own and keep awake | [NEEDS VERIFICATION: TP-Link official spec] | One site with in-house IT who will patch and back up the host |
| OC200Hardware appliance | Itself — 802.3af/at PoE or micro-USB, fanless, two gigabit ports | Recommended for managing 25 Omada devices | A single office, shop or restaurant, controller solved once |
| OC300Hardware appliance | Itself — rack or desktop, USB auto-backup | 500 access points, 100 gateways, maximum 100 switches | A larger site or a small chain run from head office |
| OC400Hardware appliance | Itself — rack mount | 1,000 access points, 100 gateways, maximum 200 switches | Multi-floor campuses and estates that keep growing |
| Cloud-based controllerCloud Essentials or Cloud Standard | TP-Link’s cloud — no appliance, devices adopt over the internet | Described as unlimited devices across one or many sites | Multi-outlet retail, F&B and hospitality |
The software controller is a free download and Cloud Essentials is listed as lifetime free cloud management; you pay for hardware, plus Cloud Standard for MSP mode. An omada controller can cost nothing on a small site and still needs an owner. Budget an omada tp-link estate on the hardware and the hours, because the licence line is the small one.
We specify the appliance for one site: powered over Ethernet from the switch already there, no operating system to forget. Cloud is for chains, where a branch nobody visits has to stay reachable. Whichever omada controller you land on, write down the estate it will manage first.
The wrong physical format costs more than the wrong Wi-Fi generation: format decides the cabling, and cabling decides what changes later.
Every tp-link omada access point below is fed over Ethernet, so the switch budget and the cable category are one decision. A tp link omada access point is only as good as its drop.
| Format | Where it goes | Typical brief | What decides it |
|---|---|---|---|
| Ceiling mount | Accessible grid, or a slab bracket | Open-plan offices, restaurant floors, retail | One drop per position, two if the ceiling closes after fit-out |
| Wall plate | Replaces an existing outlet inside the room | Hotel rooms, serviced offices, dormitories | Reuses the room’s data point; add a port for wired devices |
| Desktop or compact | On a shelf or behind a counter | Small shops, temporary sites, back offices | Cheapest to deploy, worst placement — a stopgap |
| Outdoor | Sheltered external walls and covered walkways | Car parks, yards, alfresco dining | Surge protection on any run leaving the building |
Wi-Fi 6 covers almost every SME brief we survey in Singapore. A Wi-Fi 7 tp link omada access point earns its premium in dense venues, but only on a multi-gig uplink: a tri-band radio on a one-gigabit port is throttled first. The order for every tp-link omada access point is mount, cable, radio.
A wall-plate tp link omada access point in a hotel room is a per-room decision: twenty rooms, twenty adoptions. On a refurbishment the existing data point usually carries it, and each tp link omada access point is one more line on the run.
Most shop units up to roughly 200 square metres take one or two units, but the number is set by the wall build, the ceiling material and how many devices are awake during service. Stainless-steel kitchens, mezzanines and glass shopfronts change it, so we survey before quoting a tp-link omada access point count.
Two numbers size a switch, and port count is only one. The other is the power budget, shared across access points, cameras, door readers and phones — and it runs out before the ports do.
| Site | Switch shape | Power budget to plan for | Why |
|---|---|---|---|
| Shop or cafe, 1–2 access points | 8-port PoE, desktop or wall | 60–80 W | Two access points and a camera fit; fanless matters in a customer-facing room |
| Office, 3–6 access points | 24-port PoE, rack mounted | around 180 W | Desks, access points and a few cameras on one switch |
| Two floors, or a heavy camera load | Two 24-port, or one 48-port PoE | 380–500 W | Cameras alone can consume more than the wireless — split the load |
| Backbone between racks | Aggregation switch with fibre uplinks | not applicable | Copper stops at 100 m; fibre carries the riser |
A managed tp link omada switch is where the VLANs live. Guest wireless, point of sale, cameras and staff traffic are separated on the switch or not at all, whatever the wireless configuration claims — the most common gap we find on a takeover. On an omada tp link estate that separation is written once into the site settings and inherited by every switch adopted afterwards.
Size the power budget for the estate you will own, not the box you have today. A floor getting four cameras next quarter needs those watts now, or a second tp link omada switch bought in a hurry. We plan a third of headroom, and every tp link omada switch we quote carries it on the drawing.
Uplinks are checked last and hurt first. A tp link omada switch feeding six Wi-Fi 6 access points on one gigabit uplink is a bottleneck you built, so we specify the uplink with the access point count. The same check applies at the edge: a tp-link omada router with a one-gigabit WAN port caps everything leaving the floor, whatever the switch underneath can carry.
The gateway sits between your network and the internet: most likely inherited, and its firmware most needs to be current.
| Brief | Gateway shape | What it buys you |
|---|---|---|
| Single site, one fibre line | Entry wired gateway | Firewall, VLAN routing and controller adoption — for a small office that can tolerate an outage |
| A site that cannot go offline | Dual-WAN gateway | A second line on failover, so card terminals keep trading when the primary drops |
| Several branches | Multi-gig gateway with VPN | Site-to-site links between branches, with headroom to keep inspection on at line rate |
Two notes about a tp link omada router at the edge. Dual WAN is only failover if the second line follows a different carrier path: two services through the same riser fail together. And its firmware must never sit two years out of date. A tp link omada router honours neither unless somebody configured it.
A tp-link omada router also carries the site-to-site VPN on a small chain, cheaper than a managed WAN service. TP-Link’s newer controllers add a multi-site connectivity mode needing gateways that support it, so the model is chosen with the branch plan — a tp link omada router picked that way survives the second branch.
We replace an inherited tp-link omada router only for a reason: end of support, a WAN requirement it cannot meet, or a throughput ceiling under inspection. Otherwise we adopt it and bring the firmware current — a tp link omada router bought by the client is adopted, not rejected.
One last check on a tp-link omada router: was the WAN handover tested under load? A failover never proven is a line item, not a safeguard.
We specify this platform when the money is better spent on more access points than fewer, dearer ones, and the estate is many small sites.
The briefs below are where an omada tp link design wins on merit, not price. An omada tp link build stays a value play only while the design underneath is right.
Count everything the controller manages: gateways, switches and access points sit under the same ceiling. TP-Link publishes controller capacity per device type, so a tp-link omada access point, a switch and a gateway each spend one slot against the tier you buy.
Step the number and the band shows which tier your omada tp-link estate lands in against TP-Link’s figures. Sizing an omada tp-link estate on today’s device count is how you outgrow a controller.
The platform is the middle decision. The cable underneath and the support around it decide whether the estate is manageable in year three.
TP-Link publishes the Omada Software Controller as a free on-premises controller for a Windows or Linux machine you already own, and Omada Cloud Essentials as lifetime free cloud management. The paid parts are the hardware — gateways, switches, access points, an OC-series appliance — plus Cloud Standard for MSP mode, IPS/IDS and expanded VPN. The software can cost nothing; the network cannot.
TP-Link’s business networking line plus the controller that manages it, so gateways, switches and access points are configured once and run as one estate. A Singapore SME picks tp link omada for the second site: once a template exists, the next branch is a copy.
For most single offices the hardware appliance, because it removes the host machine. TP-Link publishes the OC200 as recommended for managing 25 Omada devices, which covers an ordinary floor of access points, a couple of switches and a gateway. Choose the software controller only if you already run an always-on server.
No. The controller manages configuration, not traffic, so the gateway, switches and access points keep forwarding on their last known settings. What stops is central management: the dashboard, guest-portal logins, device adoption and batch firmware. That is why an omada controller on a sleeping laptop is a bad design.
TP-Link publishes the figures per device type. The OC200 is recommended for managing 25 Omada devices; the OC300 lists 500 access points, 100 gateways and a maximum of 100 switches; the OC400 lists 1,000 access points, 100 gateways and a maximum of 200 switches; the cloud controller is described as unlimited devices across one or many sites. TP-Link notes the stated capacity comes from laboratory testing.
We deploy both. Many small sites on a hard capital budget point to the omada tp-link route: lower cost per access point, and a cloud tier built for estates nobody visits. One growing site that will want cameras, door access and phones on one console points to UniFi — compared on our Ubiquiti Singapore page.
No. We resell this hardware, and we design, install and manage the network around it. We are not a distributor and we do not run a shopfront. If your procurement requires an authorised supply chain, buy the hardware that way and bring us in for design, installation and management.
On a site whose cabling has been tested the adoption is the short part: devices are pre-staged against a template before they leave us, so the on-site window is mounting, patching and verification. The day runs long when the cabling was never certified, the PoE budget was sized for today, or nobody wrote down which port feeds which room.
Send the floor plan and the device list — or just the number of rooms — and you get the controller tier, the access point count, the power budget and the VLAN plan in writing.
