Evernet
The layer that makes two vendor systems behave like one product
Middleware over two vendor systems that adds what neither offers: a customer device portal, a staff fleet view, scheduled failover and order automation.
Built for a clientevernethosting.com
2
vendor systems behind one layer
6
customer portal sections
1 min
between active-hours checks
Before and after
Before
A billing vendor that knew the customer and a device vendor that knew the router, with nothing joining the two.
After
One server-side layer that ties each customer to the router on their counter.
Before
No view for customers of their own device.
After
A customer portal with a device manager, and the same device console for staff.
Before
No way to schedule when backup connectivity is active.
After
Active hours, enforced by an engine that checks every minute and verifies what the vendor reports.
What it proves
Two vendor APIs behind one server-side layer.
No secret ever reaches the browser, and a reseller-wide credential is made safe per customer, checked by an automated authorization test suite.
Vendor data corrected, not merely proxied.
Unsigned signal values, one metric reported in three units, a status label that misleads under substring matching, and success codes on refused writes are all handled.
A scheduling engine with written invariants.
It runs every minute with verification reads, an audit trail and alarms.
Change detection against a system that pushes nothing.
Polling with idempotent sends, so a customer hears about a change once.
Operable by staff.
Coupons, email switches and device assignment are changed by staff without a deploy.
The screens, running
Scheduled failover
Scheduled failover
Active hours
Active hours
Fleet by carrier
Fleet by carrier
Order tracking
Order tracking
Architecture
- Storefront and checkouttoServer-side layerorders
- Customer portaltoServer-side layerdevice settings
- Staff consoletoServer-side layerfleet, coupons and emails
- Server-side layertoBilling vendorsubscriptions and shipping
- Server-side layertoDevice vendorrouter state
- Active-hours enginetoDevice vendorscheduled failover
- Active-hours enginetoServer-side layeraudit trail and alarms
What it is, and what it is not
It makes no claim about scale beyond the fleet it runs today.
It sends no failover alert emails. Those are planned, not built.
Neither a refund nor a cancellation is issued in the app. Both are guidance that points the customer to the billing portal.
Automated shipping means address write-through, shipped detection and an email, not label purchase or carrier tracking events.
It has no message queue: changes are found by polling the vendors.
Where this lives in the catalog
Book a systems audit
Start with a systems audit.
We price a build after discovery, from the company's own invoices and a mapped order-to-cash process. That map is the specification.
Built in Grand Rapids, Michigan. Or write to dev@bravuramarketing.com.
Systems audit
Ready