Download websites that use Oxygen

About Oxygen

Detection is harder for some technologies than for others, and Oxygen is a good illustration of why. A Page builders plugin for WordPress written in PHP and sold by Soflyy since 2016, it does not sit inside a theme, it replaces the theme outright and renders pages from its own components, and the markup it produces is deliberately lean.

As of October 2026 we detect the builder on 19,264 sites, and the honest framing of that number is a floor rather than a census. A tool whose selling point is output without bloat is a tool that leaves fewer traces to match on, and sites that are aggressively cached or served through an optimisation layer can lose the traces that remain. Every site in the list is confirmed. An unknown number of others run the same plugin invisibly.

The buyers are worth describing, because the product self selects for them. Anything that discards the theme layer entirely gets bought by people comfortable with markup, CSS and dynamic fields, which in practice means freelance developers and small agencies producing custom client sites. The Proprietary model reinforces the pattern, since access is purchased rather than downloaded, and somebody paying for a builder is usually somebody billing for the work it does.

United States accounts for 7,111 of the detections and .com is the suffix that recurs across the base, describing the English speaking WordPress professional market where the product was sold and discussed. Agency clustering shows up in the same data, because a builder plus a host plus a familiar set of supporting plugins, repeated across many unrelated domains, usually means one shop built them all.

The reason to want the whole population rather than a single answer is that this is a market of practitioners, not of brands. Hosts want to know which sites carry a builder that punishes cheap infrastructure. Plugin and template authors want the sites whose owners already pay for tooling. Competing builders want the same names for displacement. None of those questions can be answered domain by domain, because the unit of interest is the agency behind the sites, and an agency only becomes visible once its work can be seen side by side.

The file is evidence rather than a headcount. Presence is verified where we report it, absence is never proven, and the stack detected alongside each domain is usually more informative than the builder on its own.