Ad server comparison Revive is free to license and you run it yourself. Publishers move when maintenance starts costing more than the license, or when something breaks and no one is there to help. Find out what self-hosting actually costs, and how to move to a hosted solution like Epom.
95% renewal rate 
99.95% uptime 
13ms average response time 
Servers in Germany, the US and Asia Discover companies like yours who came off a self-hosted server and what they run on Epom today.
Ran Revive. Ad display accuracy sat at 79%, page load was slowing the site, and there was nowhere to escalate. On Epom accuracy runs at 99%, load speed improved by 137%.
“During our 6-year partnership with Epom ad server, we’ve moved away from technology challenges to effortlessly expanding our ad business, offering unique ad formats to our clients.
Came off self-hosted Revive. Runs display and native across a high-volume property, with the infrastructure and patching handled for them.
Revive’s license is free. The server, the monitoring, the engineering and the compliance work are not. The figures below are Epom’s published estimates for running a self-hosted server at scale.
Epom and Revive pricing as published, August 2026. Vendors change plans and add-on structures — confirm current rates on each provider’s pricing page.
Comparing more than two? Download the 12-platform ad server comparison.
Revive is a free script you install and maintain. Epom is managed infrastructure doing the same job with a support line attached.
Revive gave them the license for free — as their problem. Kosovo has no designated IP ranges, so their audience splits across Albanian and Serbian ranges, and 30 to 40% of readers sit outside Kosovo and Albania entirely. Revive could not combine language, geo and IP targeting to reach them.
Albanian-language targeting, Albanian and Serbian IP ranges combined with location data, and prioritization across more than 200 active advertisers with banner filtering, weighting and daisy-chaining. Custom formats — redirect, responsive and interstitial — built from no-code templates without a developer.
This is the most straightforward of these migrations. You own the MySQL database, so the export is a direct read rather than an API call.
Export and rebuild
~1–2 weeks
Configure and extend
~1 week
Test and switch
Per zone
Advertisers, campaigns, banners, websites, zones, the banner-to-zone links, delivery rules and stats.
Websites become sites. Zones become zones and placements, matched on size and type.
Image creatives re-upload, HTML and third-party tags port across. Geo, browser and day-part rules become Epom targeting.
Programmatic, automatic optimization and the fraud stack are new configuration rather than a migration.
Diagnostics and a test page, then keep the old instance serving alongside. It costs nothing to leave running.
Swap invocation tags zone by zone, then decommission. Keep the database dump.
Revive keeps websites and zones as separate objects, so the mapping is websites → Epom sites and zones → Epom zones and placements, matched on size and type. Advertisers, campaigns and banners map across by name. Revive invocation tags come in async JavaScript, iframe and local flavours; all three get replaced with Epom ad tags from Ad Tags & API. Delivery rules covering geo, browser and day-parting become Epom targeting rules and custom parameters. Statistics live in your own database — dump them before you decommission, because Epom does not import them. Revive has no OpenRTB module, so programmatic demand is configured fresh rather than migrated.
Yes, and it costs you nothing extra because you already own the server. Point one zone at Epom and leave the rest where it is for as long as you want.
The license is. The server, monitoring, engineering time and compliance work are not, and they scale with your volume rather than staying flat.
No. Check what each plugin does against Epom’s native features first — targeting and optimization in particular often have an equivalent.
Export them from your own database before you decommission. Epom does not import Revive historical data.
It gives you the source code and runs on your own hardware. If self-hosting is a requirement rather than a preference, Epom is not the answer.
On Epom, the provider does, automatically. On a self-hosted instance that is your team, on whatever timetable they have.
Point one zone at Epom for 14 days. Your own instance keeps serving everything else.
A registration has already been submitted from this page. Please try again in 10 minutes.
