OpenRTB
2.4 / 2.5 / 2.6 configuration
Connect exchange and demand partners with version selection, auction settings, bid floors and timeouts in the RTB module.
OpenRTB specificationWhite-label advertising platform
Build an advertising business that looks and works like yours. Nexus provides the platform foundation; you define the brand, partners, channels and commercial model.
Explore your white-label platform ↗For ad networks, publishers and performance businesses.
Across the Nexus suite
2.4 / 2.5 / 2.6 configuration
Connect exchange and demand partners with version selection, auction settings, bid floors and timeouts in the RTB module.
OpenRTB specificationVideo ad serving
Manage video channels and VAST tags. Review starts, quartiles, completions and URI diagnostics in the video module.
VAST specificationA structured interface for AI clients
Connect compatible assistants to discover tools and work within authenticated, domain-scoped operational boundaries.
Explore AI + MCPYour brand. Your domains.
Build your partner-facing experience around your identity, enabled products and agreed deployment requirements.
Explore white-labelProtocols apply to the relevant Nexus modules. Supported versions, player compatibility and partner interoperability are confirmed for your integration. References to IAB Tech Lab standards do not imply certification or endorsement.
More than a logo change
White-label brings the customer-facing identity and the underlying operation together. Agree on the exact branding, integrations and service scope before launch.
Present the platform under your own identity, with agreed branding and domain configuration. Your customers work with your business, not a generic shared marketplace.
Organize supply, demand and operator access around the way your network works. Keep each account within its assigned platform scope.
Configure supported bids, margins, caps and routing policies for each channel. Keep the delivery decisions connected to your business model.
Integrate feeds, OpenRTB, VAST, postbacks and APIs where supported. Add custom development when the standard workflow needs to go further.
Plan domains, services, data stores, monitoring and support responsibilities together. Choose the deployment scope before committing to a rollout.
Full MCP support gives compatible AI clients a structured interface to Nexus. Connected operations retain identity, domain scope, permissions and audit history.
Choose what you need to run
Start with the advertising workflow you need. Additional products, capacity and custom work are scoped separately as your business develops.
Before you launch
A professional platform needs more than a polished login screen. Your proposal should make the delivery and ongoing operation understandable.
Confirm domains, visual identity, partner access and the screens or workflows that need custom development.
Map environments, data stores, connected partners, monitoring and migration requirements. Define who operates each part.
Agree on acceptance checks, onboarding, maintenance windows, support coverage and escalation contacts before production.
Share your channels, expected volume and current stack. We will help separate platform requirements from optional services.