White-label DSP vs own DSP: cost, lock-in and control

Three ways to have "your own DSP"

White-label DSP. A vendor runs its platform under your brand: you get the interface, the supply connections and the billing, and the vendor keeps the software. Epom's published terms state that "All right, title, and interest in the Software and any development efforts, updates, upgrades or modifications thereof … will remain the property of Epom or its licensors", and, in the same section, that "Epom is not granting Client any rights whatsoever in the Software source code".^[2] BidsCube's DSP terms give it "the sole and exclusive ownership of all right, title and interest in and to all the Platforms".^[6] The market also changes hands: smartyads.com/white-label-dsp answered HTTP 301 to teqblaze.com/white-label-dsp when checked on 2026-09-23, and TeqBlaze describes itself as "an independent AdTech company specializing in white-label programmatic platforms and custom technology development".^[5]

Bidder-as-a-service. The vendor runs the bidding infrastructure and you bring the logic. Beeswax, whose site says "Beeswax is now part of FreeWheel", sells "Bidder-as-a-Service™ (BaaS)".^[13] Reporting the 2020 acquisition, AdExchanger wrote that Beeswax differs from competing DSPs "because of that customizability – users can install their own algorithms"; FreeWheel's general manager Dave Clark called it "a customizable demand-side buying service that's designed to leave control in the hands of the users", and LUMA Partners' Terry Kawaja said Beeswax operates under "a SaaS business model, and that makes a big difference".^[14]

Own DSP. You own the bidder, the campaign manager, the reporting pipeline and the supply contracts. The open-source route exists on paper: RTB4FREE's bidder is Apache-2.0 and describes itself as "The OpenRTB 2.0 compliant bidder for RTB4FREE, the open source bidder / DSP", but the GitHub API, read on 2026-09-23, gives the latest commit on its default branch as 20 June 2019 and the last push to the repository as 16 November 2022.^[15] Treat it as reference code, not as a maintained product.

What the white-label vendors publish

For market ranges rather than list prices, BidsCube's own blog — written by a white-label vendor, not by a buyer — puts entry-level white-label DSPs at "$2,000-$5,000" a month, enterprise at "$15,000-$50,000+ or custom", revenue share at "7-12% of media spend" and onboarding at "$5K-$20K", and adds that "Third-party data segments and Universal ID licensing can add 15-30% to your effective CPM".^[9] Read them as one vendor's view of its own market.

White-label DSP vs bidder-as-a-service vs own DSP

Stay on a white-label DSP if…

1. 1.You are validating demand. Epom's entry plan is "5% of your ad spend or $250 per month, whichever is higher",^[1] so below $5,000 of monthly spend the flat fee applies. At that volume there is nothing to save by building.
2. 2.You need supply on day one. Epom's plans include "50+ premium SSPs" from the entry tier,^[1] and BidsCube's white-label ad exchange starts "from $300/month Starting price for 1 AdServer".^[8] Signing and integrating each exchange yourself is a separate workstream with its own calendar.
3. 3.Your edge is sales and service, not the bidding logic. If clients buy your account management and your brand, the platform is a cost of doing business, and a published price makes that cost predictable.

Consider leaving a white-label DSP if…

1. 1.Symptom: every new client raises your platform bill. A share of spend — 5% at Epom above the flat fee,^[1] or the "7-12% of media spend" one vendor's article reports as a market model^[9] — grows with every client you sign, on the same money your business earns from.
2. 2.Symptom: due diligence asks what you own, and the answer is a brand. Epom's terms grant "no rights whatsoever in the Software source code" and keep modifications of the Software with Epom or its licensors;^[2] BidsCube keeps "the sole and exclusive ownership of all right, title and interest in and to all the Platforms".^[6] A company valued as a technology business needs code it owns.
3. 3.Symptom: your bidding logic is the product, and it runs in someone else's bidder. Bidder-as-a-service moves the logic to you — AdExchanger reported that on Beeswax "users can install their own algorithms"^[14] — and an own DSP moves everything. See running a model inside the bid request.

When an own DSP does not fit: agencies buying many channels for many clients, advertisers whose spend is below what a bidder team costs, and teams without on-call engineers or their own SSP relationships. The rented platforms of the The Trade Desk and StackAdapt comparison are the cheaper answer for them.

A migration path in four steps

1. 1.Pull data continuously, not at the end. Epom erases account data within 30 days of termination and BidsCube may delete customer data 30 days after it,^[2][6] so archive reports and, where your plan includes it, bidstream data from day one — at Epom, bidstream data export sits on the Pro and Enterprise plans.^[1]
2. 2.Move supply into your own name. Separate the SSP connections the vendor pre-connected from the ones you negotiated, and sign direct contracts where you need them.
3. 3.Build and run in parallel. Put one exchange or one client on your own bidder, and reconcile spend, wins and impressions daily against the white-label platform's reporting.
4. 4.Cut over and time the notice. Notice periods on the terms checked here run from 30 days at BidsCube^[6] to 90 days for the customer in Adtelligent's white-label SSP terms,^[12] and Epom's published terms renew for twelve months unless notice comes 30 days before.^[2] The build-or-rent decision in more depth: your own DSP, ad exchange or ad network.

What drives the cost of building your own

These are the cost drivers, not a price. The published rent-side figures for the same job are on what a DSP costs.

• The bidder. It answers every request inside the exchange's timeout: OpenRTB 2.6 defines tmax as the "Maximum time in milliseconds the exchange allows for bids to be received including Internet latency to avoid timeout", and the specification's video example sets it to 120.^[17] Language and runtime matter here; see Rust and Go for RTB bidders.
• Traffic. Every request costs network and compute whether you bid or not, which is why rented plans meter it: Epom caps Light and Pro at "Up to 5 000 QPS".^[1]
• Campaign manager and reporting. The interface your clients use, pacing, budgets and a log pipeline you own.
• Supply integrations. Each SSP is a contract and an OpenRTB integration with its own testing.^[17]
• Data and verification. Audience data and fraud filtering are separate contracts; one vendor's article puts data and Universal ID licensing at "15-30% to your effective CPM".^[9]
• Consent. In the EU, TCF vendors apply for "an annual Vendor membership", "Retrieve and/or receive users' choices in real-time" and "Respect such choices".^[16]
• Operations. Round-the-clock cover, because a bidder earns only while it answers.

Disclosure: this page is published by amBrain. From amBrain's AdTech services: "DSP development, real-time bidding platforms, and ad exchange engineering." The third column of the comparison table is the kind of work amBrain does. Every vendor fact on this page links to its source. Epom, TeqBlaze, BidsCube, Adtelligent, Beeswax, FreeWheel and RTB4FREE are trademarks of their owners and are used only to identify the products discussed.