Skip to content

Evernet

Two vendor systems, working as one product

It adds what neither vendor offers: a customer device portal, a fleet view for staff, scheduled failover and automated orders.

Built for a SIM hosting clientevernethosting.com

  • 2

    vendor systems behind one layer

  • 6

    customer portal sections

  • 1 min

    between active-hours checks

Where they started

A billing vendor knew the customer and a device vendor knew the router, with nothing joining the two. Customers couldn't see their own device, and there was no way to schedule when backup connectivity was on.

What we built

  • One server-side layer that ties each customer to the router on their counter.

  • A customer portal with a device manager, and the same device console for staff.

  • Scheduled active hours for backup connectivity.

Highlights

  • Two vendor systems behind one layer

    No secret ever reaches the browser, and a reseller-wide credential is made safe for each customer, checked by automated authorization tests.

  • Vendor data corrected before anyone sees it

    Unsigned signal values, one metric reported in three units, misleading status labels and success codes on refused changes are all handled.

  • A scheduler with written rules

    It runs every minute with verification reads, an audit trail and alarms. The vendors push nothing, so changes are found by polling, and a customer hears about each one once.

  • Run by staff, without a developer

    Staff change coupons, email settings and device assignments themselves, with no deploy.

Screens

  • Scheduled failover

  • Active hours

  • Fleet by carrier

  • Order tracking

How it fits together

  1. Storefront and checkouttoServer-side layerorders
  2. Customer portaltoServer-side layerdevice settings
  3. Staff consoletoServer-side layerfleet, coupons and emails
  4. Server-side layertoBilling vendorsubscriptions and shipping
  5. Server-side layertoDevice vendorrouter state
  6. Active-hours enginetoDevice vendorscheduled failover
  7. Active-hours enginetoServer-side layeraudit trail and alarms

Worth knowing

  • It makes no claim about scale beyond the fleet it runs today.

  • It sends no failover alert emails yet. Those are planned, not built.

  • Refunds and cancellations aren't issued in the app. It points customers to the billing portal.

  • Automated shipping means address updates, shipped detection and an email, not buying labels or carrier tracking.

Get started

Start with a free systems audit.

We map how orders, stock and money move through your company today, and every place your team types the same thing twice. Then we turn that into a phased plan with a fixed price for each phase.

Based in Grand Rapids, Michigan. Or email dev@bravuramarketing.com.

Systems audit

Ready

No https:// needed.

Optional. One sentence is plenty.

Two required fields. · Or write to dev@bravuramarketing.com.

CUSTOM ERP AND CRM SOFTWARE · ONE SYSTEM YOU OWN · THE SOFTWARE DIVISION OF BRAVURA MARKETING