Limited public documentation
Customer-controlled deployment is scoped case by case.
Oxaide does not maintain this as a standalone public product page. When a live engagement needs a tighter deployment boundary, the operating pattern is scoped after Verify or alongside Horizon.
Typical trigger
A site already has a real review or monitoring need and the customer boundary requires on-premise, isolated, or otherwise controlled deployment.
What happens next
We scope the boundary, data handling, and operating model around the live requirement rather than present it as a separate front-door sales story.