Prebid Server

Prebid Server is the open-source, server-to-server home of header bidding. It runs real-time programmatic auctions across your demand partners on behalf of your Prebid.js and Prebid Mobile clients, moving the auction server-side to cut page weight, reduce client CPU, and let you add more bidders without slowing the page.

Key features

• OpenRTB 2.x server-to-server auction endpoint (/openrtb2/auction) for web and app
• Large catalog of built-in demand adapters (bidders), configured server-side
• Cookie-sync and user-ID handling done on the server, off the browser
• Built-in /status health endpoint and a landing page, ready on first boot
• Runs the official, unmodified ghcr.io/prebid/prebid-server-java container
• No web console and no credentials to manage: a pure JSON auction API

Use cases

• Move header-bidding auctions server-side for a publisher or ad network
• Run a self-hosted Prebid Server for web (Prebid.js) and mobile (Prebid SDK)
• Keep auction logic, bidder config, and user data on infrastructure you control

Why run it on the NetActuate edge Hosting Prebid Server in a PoP near your users shortens the round-trip for the auction call and the demand partners, trimming auction latency (which directly affects fill and revenue) while keeping your bidder configuration and user-sync data on your own servers.

Deployed from the NetActuate marketplace, Prebid Server boots pre-configured from a sane default config: the auction API, the built-in landing page (/) and the health endpoint (/status) answer on HTTP port 80 as soon as the instance is up. Seed an optional HTTP port and public external URL, then add your demand partners and stored requests via the standard Prebid Server configuration. Put a TLS-terminating proxy in front before exposing it on an untrusted network.