What Is Prebid Server and How Does It Work

Prebid Server is an open-source, server-side header bidding platform maintained by Prebid.org that moves the auction process off the user's browser and onto a server, enabling publishers to run real-time bid requests to multiple demand partners simultaneously without the page latency that comes from client-side JavaScript execution.

Why server-side matters

Client-side header bidding, the kind powered by Prebid.js, runs directly in the browser. Every time a page loads, the browser fires bid requests to each demand partner, waits for responses, and then passes results to the ad server. This works, but the tradeoff is real: each additional bidder adds weight to the page, and mobile web and app environments handle JavaScript execution poorly. Prebid Server moves that work upstream. The browser or app sends a single request to a server, the server fans out to all configured bidders in parallel, collects the responses, and returns a consolidated set of bids. The client side barely notices.

For a detailed comparison of when to use each approach, see our Prebid.js vs. Prebid Server breakdown.

How Prebid Server works, step by step

The request flow has five stages.

A user loads a page or app. Instead of the client firing individual bid requests to each SSP or exchange, it sends one request to Prebid Server — either via a Prebid.js S2S configuration on web or directly from an SDK on mobile.

Prebid Server receives that request and fans it out simultaneously to all configured bid adapters. These are server-side equivalents of the client-side adapters you may already be familiar with from Prebid.js, and Prebid.org maintains hundreds of them.

Each demand partner returns a bid response. Prebid Server collects those responses within a defined timeout window (typically 200 to 300 milliseconds), discards any that arrive late, and assembles the results.

The server returns the winning or all eligible bids back to the client, depending on how the integration is configured. The client then passes them to the ad server as key-value pairs, just as it would with standard header bidding.

The ad server makes the final decision, running those bids against direct-sold and other demand in a unified auction.

Go and Java: the two implementations

Prebid Server exists in two official implementations: one written in Go (the original, hosted on GitHub as prebid-server) and one in Java (prebid-server-java). Both are maintained by the Prebid.org community, both support the same bid adapters and feature set, and both are production-ready. The Go version tends to be the more widely deployed of the two, but the Java version is a fully supported alternative for teams whose infrastructure already runs on the JVM.

Key components to understand

Three components matter most when evaluating or configuring Prebid Server.

Stored requests are pre-configured auction setups kept server-side rather than passed in full with every ad call. They reduce request payload size and let publishers manage bidder configurations centrally without touching client-side code for every change.

Bid adapters are the server-side modules that translate Prebid's standardized request format into each demand partner's proprietary API format, then translate the response back. Adding a new demand partner means adding (or enabling) its adapter — not rewriting your page integration.

Analytics modules connect Prebid Server to data pipelines, giving publishers visibility into bid rates, timeouts, win rates, and revenue by demand source. Without analytics, you are running blind.

Open-source project vs. hosted managed service

This distinction is worth being explicit about. Prebid Server the open-source project is free software anyone can deploy. The Prebid.org community publishes the code, documents the APIs, and reviews adapter contributions. Deploying it yourself, however, means standing up and maintaining server infrastructure, configuring adapters, managing updates, and monitoring uptime. That operational burden is not trivial, especially for publisher teams without dedicated engineering resources.

A hosted or managed Prebid Server is a commercial offering where a vendor runs that infrastructure on your behalf. You get the demand access and performance benefits of server-side bidding without owning the maintenance overhead. Aditude's Prebid Server product is a managed version of this: the open-source engine, operated and optimized at scale, with support included.

The two are related but not the same. When evaluating your options, the question is not just whether to use Prebid Server — it is whether you want to run it yourself or have someone run it for you.

Is Prebid Server right for you?

Server-side header bidding is the right direction for publishers who are hitting the ceiling on client-side performance, running mobile apps where Prebid.js isn't an option, or scaling to a volume where JavaScript-based auctions create measurable latency problems. It is not a replacement for Prebid.js in all cases — many publishers run both in a hybrid configuration — and setup complexity is higher than dropping a script tag on a page.

If you are at the evaluation stage, the next logical step is understanding what implementation actually looks like. See our guide to setting up Prebid Server for a practical walkthrough.

Ready to skip the infrastructure work? Run Prebid Server without the overhead — see Aditude's solution.