Backup internet, built for restaurants.

Yes. We sit a layer below the POS, at the network level, so there's nothing to integrate and nothing to break. Toast, Square for Restaurants, Clover, Lightspeed Restaurant, TouchBistro, SpotOn: if it runs on ordinary internet, it runs on ours. The useful part is prioritization, which keeps a busy guest network from starving your card readers and ticket printing.

They keep flowing. Online orders reach you over the internet, whether they come through your own site, your POS, or marketplace tablets from DoorDash, Uber Eats, and Grubhub. When your primary line fails, that traffic moves to the cellular path automatically, so orders keep landing and the tablets stay online.

Without a second path, this failure is quiet. Tablets drop offline, the marketplaces can pause your menu, and you find out from the missing orders rather than from an alert.

From the dining room, ideally nothing. Traffic moves to the surviving connection on its own, and anything bonded, payments, POS, and tickets included, was already traveling both paths when the failure hit. The alert lands with our team, who are usually investigating before anyone in the building has looked up from a table.

Plenty for a full house. POS, tickets, online orders, music, cameras, and guest Wi-Fi together are a light load by internet standards, and most of it runs at the native speed of your healthiest connection.

The bonded path is the one exception: it trades top speed for resilience and tops out around 200 Mbps. That ceiling is the hardware doing the encryption, not a cap we've set, and it applies only to traffic in the bonded lane. A card transaction weighs a few kilobytes, so payments will never come close to it.

One account, one point of contact, centralized billing, and a separately preconfigured unit for every address. After go-live, we watch each location around the clock and only escalate the things that need a decision from you.

Monitoring runs 24/7. Our team is staffed from 6am Eastern to 9pm Pacific, which covers service at just about every restaurant we work with.

There's deliberately no customer dashboard. Monitoring is part of what you're paying us to do, so we do it, and we get in touch when something needs action.

A Core Router configured for your specific location, with 5G built in and the SIM already seated. Where a design calls for extra cellular capacity or another network, we add an Add-On Modem. All of it is commercial-grade Peplink equipment meant to run around the clock. If your building needs unusual mounting or antennas, we work that out with you before anything ships.

About a week, and most of that is shipping. We spend a day or two on configuration before the unit goes to the courier for 3 to 5 days, and the install at your end is measured in minutes. Groups can bring locations online in parallel; the pace is usually set by each restaurant's schedule rather than by anything on our side.

If an address looks like it will need an antenna survey or custom mounting, we say so before you order, not after.

The certification stays yours to hold, as it does with any internet provider; nothing about us changes your merchant obligations. Where we help is the networking underneath. Payment traffic can live on its own VLAN, away from guest Wi-Fi, and the Core Router supports the configurations most PCI-DSS checklists ask about. Bring us your audit requirements and we'll go through them line by line.

Yes, as long as they can reach your Wi-Fi. Handhelds, tableside readers, and kitchen tablets connect to your local network, and Waveform keeps that network connected to the internet. During an outage, the handheld talks to the same Wi-Fi it always does; its traffic just leaves the building over cellular instead of the failed line.

The one thing bonding can't fix is power. If you want payments to survive a power cut too, put the router and your access points on a small UPS. Ask us and we'll tell you what to plug in where.

Failover is sequential. One connection dies, another takes over, and there's a gap while that happens, which is how most backup products behave.

Bonding removes the gap by running connections simultaneously. We bond selectively, reserving it for traffic where an interruption costs money, like payments, POS, tickets, and calls, and let everything else fail over intelligently instead.

No. Configuration happens here before we ship, and the physical install is antennas, two cables, and a wall outlet. Anything that needs adjusting later, we adjust remotely. Nobody on your staff has to become the network person.

It's a reasonable product for what it is: one 5G connection that steps in after your ISP fails, at a lower price than ours. If a brief gap during the switch is tolerable and nobody needs to be watching it for you, it may well be enough.

We're built for the restaurants where the gap is the problem. Multiple connections running at once, bonding on the critical traffic, hardware and SIM included, monitoring around the clock and a team on the other end of it. The extra cost buys the difference between a spare tire and a second engine already running.

SD-WAN platforms mostly assume ingredients you already own: a second connection installed, compatible hardware, and someone comfortable writing and maintaining failover policy. We show up with all of it in the box: connection, plan, router, configuration, monitoring, support.

If you have an IT team that wants to run the stack, SD-WAN done well is a fine route. If you'd rather buy the outcome than assemble the parts, that's what we're for.

Yes, there are primary tiers built on cellular. Most restaurants shouldn't start there, though: if a workable wired line already exists, keeping it and adding an active cellular path gives you two kinds of infrastructure instead of one, which is the whole idea. Primary earns its place where wired options are bad, late, or missing entirely, like rural sites and new builds still waiting on fiber.

Often better than in a city, since rural wired service is exactly where reliability runs thinnest. We test cellular coverage against your street address before anything ships and tell you plainly what to expect. If the signal looks borderline, an external antenna can go in the kit.

Yes, happily. A dish can be one of the connections we manage, and for truly remote restaurants it's often the right architecture. Satellite and cellular fail independently, where two wired providers often hang from the same pole down the road.

No overage fees, ever, and everyday traffic carries no cap at all. The bonded path is the only thing we meter: 250 GB a month on Smart. Because only payments, POS, tickets, and calls travel bonded, restaurants rarely get near it.

If you do go over, we'll usually just cover it. If it becomes a monthly habit, we'll come to you about a bigger allowance rather than let it turn up on a bill.

Send everything back inside the first 30 days for a full refund, hardware included, with no restocking fee and no one making it awkward. It doesn't happen often, because coverage gets checked at the address before we ship, but the exit stays open.

No. The service is month to month; leave whenever you like. Hardware works one of two ways: buy it upfront and it's yours from day one, or rent it monthly for as long as you're a customer and send it back when you stop. And the first 30 days work like a trial: if it's not the right fit, everything goes back for a full refund.

Usually, yes. We slot in upstream of your current router and take over the multi-WAN decisions, and everything behind it keeps working exactly as it does today. Networks with more moving parts, like VLANs, VoIP phones, or kitchen printers pinned to fixed addresses, get a design review with us before anything ships.