Self-hosted ad serving, honestly reviewed. No marketing fluff, just what you get when you run your own ad server.

TL;DR

What it is: GPL-2.0 licensed, open-source ad server for publishers, ad networks, and advertisers who want to serve, manage, and track ads without routing everything through Google [README].
Who it’s for: Publishers running their own sites or ad networks who are paying volume-based SaaS fees and want full control over their ad data and delivery rules. Also anyone getting kicked off a commercial ad platform who needs a fallback [3].
Cost savings: The software is free. A VPS to host it runs $5–20/month. Commercial ad server SaaS starts at $30+/month for low-volume plans and scales to hundreds — the math becomes obvious above ~2.5M ad requests/month [5][2].
Key strength: Mature, battle-tested software with over a decade of production use. Claims 6,000+ known self-hosted installations, and the hosted edition serves hundreds of millions of ads per month [4][2].
Key weakness: The codebase is old — some parts are over two decades old by the team’s own admission. PHP-based, requires MySQL or PostgreSQL, the UI has not kept pace with modern admin tooling, and the community forum is closing at end of May 2026 due to bot traffic overwhelming human engagement [README website][1].

What is Revive Adserver

Revive Adserver is an open-source ad serving system built for publishers and ad networks who want to manage advertising inventory without depending on Google, Meta, or other walled-garden platforms. You install it on your own server, paste a zone tag into your site, and it handles everything: selecting which ad to show, tracking impressions, clicks and conversions, applying targeting rules, and reporting results.

The project has a long history. It launched as “Revive Adserver” in September 2013, but the underlying software predates that by years — it was the successor to OpenX Source, which itself was one of the earliest open-source ad servers. When OpenX shut down its open-source program, and again when Adzerk shut down its self-serve tier in 2014, Revive was explicitly the recommended migration target [3]. That’s not a minor detail: it means the software has survived multiple rounds of commercial consolidation that wiped out competitors.

The current version is 6.0.6 (released March 18, 2026), compatible with PHP 8.2–8.5 after a major compatibility update in v6.0.0. The project sits at 1,435 GitHub stars — a modest number that understates actual usage, since the install base predates GitHub’s dominance and the team explicitly notes “probably many more we don’t know about” beyond the 6,000+ tracked installations [4].

The project is maintained by a small team (under 25 employees) operating as Revive Software and Services, a legal entity formed in 2015 to hold intellectual property and handle sponsorships. A Patreon program funds ongoing development [4]. This is a bootstrapped, community-sustained project — not VC-backed, not pivoting toward AI agents.

Why people choose it

The core reason is simple: you want to run ads on your own property without paying a percentage to a commercial intermediary, or without routing audience data through someone else’s servers.

The adpushup.com review [1] frames the use case clearly: Revive suits everyone on the supply and demand side — publishers, ad networks, advertisers, ad management platforms. The key differentiator is that it’s designed to run at scale; the team claims publishers have displayed over 1 billion ads per month through the platform, which obviously requires serious hardware, but the software architecture supports it [1].

Three specific situations where people switch to Revive:

Platform shutdown refugees. When OpenX killed its open-source edition and when Adzerk shut down its self-serve program, Revive was the explicit successor. Adzerk’s CEO personally recommended Revive as “their only recommendation for people looking for a self-hosted ad server solution” [3]. That pattern of commercial ad servers shutting down non-enterprise tiers keeps repeating, and Revive is the standing lifeboat.

Cost escape at volume. Commercial ad serving SaaS bills by ad requests. Aqua Platform’s hosted Revive service starts at $30/month for 2.5 million requests, with the CPM rate dropping below $0.003 above 500 million monthly requests [5]. If you’re serving at that scale through a commercial platform with a percentage model, the savings are substantial.

Data sovereignty. GDPR compliance is built into the software design — Revive’s code doesn’t transmit or store personal data, and you don’t need to sign up to download it [1]. For publishers serving European audiences or operating in regulated industries, keeping audience data on your own infrastructure is not optional.

Features

Based on the official documentation and third-party reviews:

Core ad serving:

Banner ads: image banners, HTML5 (including IAB-compliant with video and audio), third-party ad tags, rich media [1]
Zone system: define sites, create zones, get embed code for each zone [README]
Campaign types: contract campaigns, remnant inventory, override campaigns [1]
Internal and external ads (affiliate networks, Google AdSense as pass-through) [1]

Targeting:

Geographic location
Browser language
Visitor gender, education, age range (self-declared or inferred)
Date, day, and time targeting
Web browser targeting
Content category targeting
Frequency capping [1][README]

Statistics and reporting:

Impressions, requests, clicks, conversions tracked per zone and campaign [README]
Revenue, eCPM, CTR, conversion rates including basket value and item count [website]
Statistics updated once per hour (not real-time) [1][README]
v6.0 brought major speed improvements to statistics reports [website blog]

Infrastructure and integrations:

Runs on PHP (8.2–8.5 as of v6.0) with MySQL or PostgreSQL [1][website blog]
Designed to run on server clusters for horizontal scaling [1]
GeoLite2 geotargeting via MaxMind plugin (added in v5) [README]
Plugin architecture for extending functionality [merged profile]
New Mailer plugin added in v6.0 [website blog]

What it doesn’t do:

No programmatic/RTB auction support out of the box (this is a direct-sold or network-fill server, not a header bidding platform)
No real-time reporting (hourly updates only) [1]
Advanced reporting is explicitly noted as a gap: the adpushup review calls out that “Revive Adserver lacks advanced reporting features” [1]

Pricing: SaaS vs self-hosted math

Self-hosted (Download edition):

Software: $0 (GPL-2.0)
VPS: $5–20/month depending on traffic volume
Your time for setup, maintenance, and updates

Revive Adserver Hosted edition (their own managed cloud at revive-adserver.net):

$10/month as cited by the adpushup review [1]
Targeted at users who want the software without managing servers

Third-party managed hosting (Aqua Platform):

Starts at $30/month for up to 2.5 million ad requests/month
Below $0.003 CPM above 500 million requests/month [5]

Commercial ad server comparison:

Google Ad Manager: free at small scale, but you’re inside Google’s ecosystem by definition
Kevel (formerly Adzerk, the one that shut down its self-serve): enterprise-only pricing, no published rates
AdButler, OIO Publisher, and similar: typically $10–$50/month at entry, scaling by impressions

Concrete math for a mid-sized publisher:

Say you’re running a niche B2B site with 5 million monthly pageviews, 1 banner per page, 100% fill from direct-sold campaigns. That’s 5 million monthly ad requests. On Aqua Platform’s hosted Revive, you’d be on a mid-tier plan — probably $60–$100/month. Self-hosted on a Hetzner CX21 (2 vCPU, 4GB RAM, ~$6/month), you’d handle that volume without breaking a sweat at $6/month in VPS costs. The software is free. Annual difference: roughly $650–$1,100 saved against managed hosting, or negligible cost against an equivalent commercial ad server.

The caveat, as always: that $6/month doesn’t include your time. Setup, security patches, PHP version upgrades (the v6.0 push to PHP 8.2+ was non-trivial for users on old installs), and monitoring are real ongoing costs.

Deployment reality check

Revive is a PHP application that requires a web server (Apache or nginx), PHP 8.2+, and MySQL or PostgreSQL. It does not ship as a Docker container by default — you’re installing it the traditional LAMP/LEMP stack way, which means the installation process is closer to a 2015 WordPress install than a modern Docker Compose deployment.

The install path:

Download the release package from the official website (the README explicitly warns not to download the GitHub ZIP — it contains dev-only files and won’t work) [README]
Extract to your web server’s document root
Point a domain at it, configure PHP and database
Run the web installer

What you actually need:

Linux VPS with at least 2GB RAM (4GB if you’re running meaningful volume)
Apache or nginx with PHP 8.2–8.5
MySQL 8 or PostgreSQL
A domain and SSL certificate
SMTP setup for campaign notifications

What can go sideways:

The codebase “is more than 2 decades old” in some places — the team’s own phrasing in a November 2025 blog post about security fixes [website blog]. That’s an honest acknowledgment that security patches are ongoing.
The community forum closes at end of May 2026. The team cites “over 99% of traffic identified as automated bots” and “high licensing costs of the Invision Powerboard software” as reasons [website blog]. For a self-hosted tool where community support is the primary help resource, losing the forum is a real practical hit. Future support will need to come from GitHub issues or the documentation.
PHP version upgrades have historically been disruptive. The jump to PHP 8 support required a major version release (v5.3, then v6.0) and was an explicit project milestone [4][website blog].
No Docker Compose deployment means you’re managing a full PHP stack manually, not just running docker compose up.

Realistic setup time for someone comfortable with Linux and PHP: 2–4 hours to a working install. For someone following a guide without prior experience: a full day, including debugging PHP module issues and database connection problems that invariably appear.

Pros and cons

Pros

Genuinely free GPL-2.0 software. No commercial licensing required for any feature. Download, install, use, modify [README].
Decade-plus of production hardening. 6,000+ known installs, 1 billion ads/month claimed through the platform historically [1][4]. It works at scale because it’s been doing it for years.
GDPR-compliant by design. No personal data transmitted or stored by default, no sign-up required to download [1]. This is architecture, not marketing.
Broad targeting options. Geo, language, browser, time, content — this covers most direct-sold campaign requirements [1][README].
Multiple campaign types. Contract, remnant, and override campaigns means you can manage a full waterfall of inventory priority without hacking things together [1].
Hosted option available. If you want the software without server management, the hosted edition at $10/month is a low-cost entry [1][2].
Active security posture in v6. The team has been shipping security-focused patches quickly and is transparent about the reasons — they even wrote a blog post explaining the “flurry of releases” is a positive sign of open-source scrutiny [website blog].

Cons

Old codebase. The team says it themselves: some code is over two decades old [website blog]. That means technical debt, PHP-era architecture patterns, and ongoing security surface.
No Docker support out of the box. Manual PHP stack installation is a higher barrier than modern containerized tools. No docker compose up option [README].
Hourly stats, not real-time. If you’re used to GA4 or commercial ad platforms with real-time dashboards, the one-hour reporting lag is a step backward [1].
Weak advanced reporting. The adpushup review explicitly flags this: basic metrics are there, advanced analytics are not [1]. For optimizing complex campaigns you’ll need external tooling.
No RTB/programmatic. This is a direct-sold and remnant network server, not a header bidding platform. If you want Google Open Bidding, header bidding, or SSP connections, you need to build that layer yourself or use a different tool.
Community forum closing May 2026. The primary community support channel is being shut down [website blog]. GitHub issues and documentation become the only support path.
Small maintainer team. Under 25 people, Patreon-funded, no VC backing [1][4]. Sustainable so far, but the bus factor for a critical piece of ad infrastructure warrants consideration.
No modern API surface. The plugin architecture is the extension mechanism, not a REST API. Programmatic campaign management is limited.

Who should use this / who shouldn’t

Use Revive Adserver if:

You’re a publisher or small ad network paying per-impression fees to a commercial ad server and the math has turned against you.
You need to serve direct-sold campaigns across your own inventory and want full control of targeting and reporting without a Google dependency.
You’re in a market where data sovereignty and GDPR compliance are non-negotiable and you can’t trust a third-party ad server with your audience data.
You migrated off Adzerk, OpenX, or another shuttered platform and need a stable, proven replacement.
You have (or can hire) someone comfortable with PHP/MySQL stack administration.

Skip it (stay on Google Ad Manager) if:

You’re primarily running programmatic revenue through Google’s demand. GAM integrates directly with Google’s demand stack; Revive doesn’t.
You need real-time reporting and advanced campaign analytics. The hourly stats model isn’t suitable for active campaign optimization.

Skip it (use a modern containerized alternative) if:

Your team is Docker-native and the thought of manually managing a PHP stack on a VPS is a productivity tax you won’t pay.

Skip it (use AdButler or similar) if:

You want a hosted commercial ad server with a proper support contract and you’re willing to pay for it. Revive’s hosted edition is minimal; a proper commercial solution offers more hand-holding.

Skip it entirely if:

You’re a non-technical founder without someone to handle server administration. The setup process, ongoing PHP version maintenance, and now the loss of the community forum make this a tool for technically comfortable operators.

Alternatives worth considering

Google Ad Manager — free, deep Google demand integration, but you’re inside Google’s ecosystem and your data flows through their infrastructure. The default choice if you’re already running AdSense.
Kevel (formerly Adzerk) — the commercial successor to the platform that explicitly recommended Revive when it shut down its self-serve tier [3]. Enterprise-only now, no public pricing.
AdButler — commercial hosted ad server, $10–$100+/month depending on volume, more modern UI, managed service. Good option if you want Revive’s capabilities without the self-hosting burden.
OpenRTB-compatible stacks (Prebid Server, etc.) — if your use case is programmatic/header bidding rather than direct-sold campaigns, these are the right tools. Revive doesn’t compete here.
AdServer.online and similar PHP-based clones — various forks and alternatives exist, but Revive remains the most actively maintained open-source option in this category with the longest production track record.

For a non-technical founder, the honest answer is: Revive is not the right tool without technical help. If you need someone to deploy it for you, that’s a one-time cost. If you need ongoing support past May 2026 and the forum is gone, budget for GitHub issue responses or paid consulting.

Bottom line

Revive Adserver is a proven, free, GPL-licensed ad server with over a decade of production use and an honest team that acknowledges their codebase’s age while actively patching it. It’s the right tool for publishers and ad networks who want to escape per-impression SaaS billing, need GDPR-compliant ad serving, or have been burned by commercial platforms shutting down self-serve tiers. The trade-offs are equally real: no Docker deployment, hourly stats instead of real-time, no programmatic/RTB support, and a community forum that’s closing at the end of May 2026. This is not a tool you hand to a non-technical operator and walk away from — it requires someone comfortable maintaining a PHP application on a Linux server. But if that’s you, or you have someone like that, the software works, it scales, and it costs you nothing beyond your hosting bill.

If the server administration piece is the blocker, that’s exactly the kind of one-time deployment that upready.dev handles for clients.