Bricks versus Oxygen: License Structure and Update Documentation for Developer-Heavy Workflows
Choosing between Bricks and Oxygen for WordPress development means weighing two fundamentally different approaches to licensing, updates, and long-term maintenance. Both builders target developers who want clean output and granular control, but their business models and release philosophies diverge sharply. This wordpress builder review examines the documented license structures, update transparency, and workflow constraints that matter most for technical teams.
License Structures: Subscriptions Versus Lifetime
Bricks: Tiered Plans with Evolving Site Limits
Bricks operates on a tiered subscription and lifetime model. The vendor’s official pricing page lists annual plans and a one-time lifetime option, with the ability to restrict license activation to specific sites through whitelist and blacklist URL features.
The structure includes Starter, Business, and Ultimate tiers. A vendor community forum announcement detailed changes effective January 2024: the Starter lifetime license was retired for new customers, and an Ultimate plan for unlimited sites was introduced at a one-off payment of $599. The vendor’s official pricing page confirms that local and staging sites do not count against license limits.
A significant 2024 forum post announced the removal of the 1000-site limit for Bricks Ultimate license holders. The post stated: “We removed the 1000 site limit for all Bricks Ultimate license holders.” This change applied retroactively to existing customers.
| Plan | Site Coverage | Billing Model | Key Documented Feature |
|---|---|---|---|
| Starter | Limited (specific count not stated on official pricing page) | Annual or lifetime (lifetime retired for new customers in 2024 per forum) | Entry-level access to builder core |
| Business | Expanded (specific count not stated on official pricing page) | Annual or lifetime | Mid-tier for growing operations |
| Ultimate | Unlimited sites (per 2024 forum announcement) | One-off $599 lifetime payment | Whitelist/blacklist URL control |
The vendor’s official pricing page notes that subscriptions renew yearly until canceled, while lifetime plans require only a one-time payment. Applicable taxes are added at checkout based on location.
Oxygen: Single Lifetime, Unlimited Sites
Oxygen’s license structure is deliberately simple. The vendor’s official pricing page lists a single lifetime license at $99, with no tiers, seat counts, or renewal dates. The page states: “Buy Oxygen once and use it on every site you build, for as long as you build them.”
Key documented terms from the official pricing page:
- Lifetime License: $99 (reduced from a previous price point, per the same page)
- Unlimited sites: No site limit for the single license
- No renewals: One-time payment with perpetual access
- 60-day refund window: Full refund available within 60 days of purchase
The vendor’s official pricing page also addresses existing customers from earlier pricing eras: “If you already own Oxygen: Nothing changes for you. Your lifetime license remains valid. You’ll continue to receive all updates and new features.”
| Aspect | Bricks | Oxygen |
|---|---|---|
| Pricing model | Tiered (Starter/Business/Ultimate) | Single tier |
| Site limits | Unlimited at Ultimate tier (per 2024 forum) | Unlimited (official pricing page) |
| Payment structure | Annual subscriptions or one-time lifetime | One-time lifetime only |
| Historical price changes | Starter lifetime retired 2024 | Reduced from a higher price to $99 |
Update Documentation: Changelog Transparency and Release Pacing
Oxygen: Maintenance-Focused Releases with Versioned Archives
Oxygen’s update documentation follows a clear pattern in its release archive. The vendor distinguishes between feature releases and maintenance releases, with explicit labeling.
Feature releases: Oxygen 4.9 introduced a right-click context menu and new Advanced Query builder options, per the release archive. These are accompanied by dated announcement posts with detailed changelogs. The 4.9.6 release carried a date stamp in its announcement.
Maintenance releases: Oxygen 6.1.3 is explicitly labeled “a maintenance release focused on stability” in the release archive. Similarly, Oxygen 6.1.1 was described as “a maintenance release focused on stability” that “clears out a set of regressions reported after 6.1.” These releases address specific bug fixes without introducing new capabilities.
The release archive provides download access directly from the vendor’s customer portal, with in-place updates available through WordPress. Changelogs for maintenance releases are concise and bug-specific. For example, Oxygen 6.1.3 fixed a “‘Stylesheet is missing’ error on the WordPress Themes page in 6.1.2.”
However, the documentation structure shows a gap: backward-compatibility notices for template or design-set changes are not prominently featured in the maintenance release announcements. Teams relying on third-party design sets or custom implementations must test against each release rather than relying on explicit compatibility statements.
Bricks: Continuous Changelog Approach
Bricks takes a different approach to update documentation. The vendor provides changelogs through its account portal and builder interface, with version history accessible to license holders. The official documentation emphasizes that there is no downloadable version of the builder; updates are delivered through the WordPress dashboard or the online sandbox environment.
The vendor’s official pricing page notes that users can try the latest version online for free, suggesting that documentation and feature previews are tied to the current release rather than archived versions.
Critical workflow note: Neither builder’s public documentation provides extensive backward-compatibility guarantees for custom code, third-party integrations, or design sets. Published third-party coverage notes that “a decent amount [of extensions] have abandoned [Oxygen] since the announcement of Breakdance,” which creates practical compatibility concerns beyond what either vendor’s changelog addresses.
Developer Workflow Constraints
Bricks: Evolving Limits and Ecosystem Considerations
The 2024 removal of the 1000-site cap for Ultimate holders represents a significant shift for agency workflows. The vendor community forum announcement framed this as removing a barrier: “If the 1000 site limit was holding you back from getting Bricks, we’ve got good news for you.”
However, Bricks imposes other constraints relevant to developer workflow tools:
- No downloadable version: The official pricing page explicitly states “There is no downloadable version.” This requires active license validation for installations and updates.
- URL management overhead: The whitelist/blacklist feature, while granular, adds administrative steps for teams managing many client sites.
- Staging site rules: Local and staging sites do not count against limits, but the forum reveals edge cases (e.g.,
stage.xxxx.xxxsubdomains) that may require manual classification.
Published third-party coverage highlights Bricks’ workflow strengths: one review states that “Bricks is awesome because of the workflow it requires, you will always build solid stuff with it.” Another notes that “Bricks has caught up and can currently do everything Oxygen can, except faster and easier.” These are qualitative assessments of workflow efficiency, not measured performance claims.
Oxygen: Stability-Focused Pacing and Extension Dependency
Oxygen’s maintenance-release pacing creates distinct workflow constraints. The vendor’s release archive shows a pattern of stability-focused minor releases (6.1.1, 6.1.3) interspersed with feature releases (4.9.x series). This prioritizes reliability over rapid feature iteration.
For teams requiring frequent feature updates, this pacing may feel restrictive. The release archive explicitly states the philosophy: “By keeping releases hyper-focused, we’re able to regularly deliver new features, quality of life improvements, and important bug fixes without any major delays.” The emphasis on “hyper-focused” releases means individual updates contain fewer changes but arrive with predictable cadence.
The extension ecosystem presents another constraint. Published third-party coverage reports that “Oxygen does have a massive library of extensions built for it (although a decent amount have abandoned it since the announcement of Breakdance, with developers switching to Bricks because of Oxygen’s wish-washy transparency).” This creates uncertainty for teams dependent on specific third-party tools.
Critical Workflow Step: Back Up Before Any License or Builder Change
Before any irreversible configuration change—including license migration between tiers, builder switching, or major version updates—back up first. This applies to:
- Migrating from a Bricks annual subscription to a lifetime plan
- Transferring Oxygen licenses between client projects
- Switching between Bricks and Oxygen entirely
- Applying major version updates (Oxygen 4.x to 6.x, or significant Bricks releases)
Use a complete WordPress backup solution that captures the database, uploads directory, themes, plugins, and builder-specific content. Test restoration procedures on a staging environment before touching production sites.
Who Each Tool Is Wrong For
Bricks May Not Suit Teams Needing Extensive Third-Party Ecosystem Guarantees
The documented removal of the 1000-site limit and the unlimited-site Ultimate tier address scale concerns, but Bricks’ relative youth in the market means its third-party ecosystem is still developing. Teams with heavy investments in specific plugin ecosystems or design set libraries may find integration coverage incomplete. The vendor’s official documentation does not provide exhaustive compatibility matrices for third-party tools.
Additionally, teams uncomfortable with annual subscription models or requiring downloadable, air-gapped installations will find the “no downloadable version” policy incompatible with their security or deployment requirements.
Oxygen May Not Suit Teams Requiring Frequent Feature Updates or Uncomfortable with Maintenance-Release Pacing
Oxygen’s stability-first release philosophy, documented in its maintenance release labeling, means feature updates arrive less frequently than some competitors. Teams accustomed to rapid feature iteration or requiring cutting-edge builder capabilities on short timelines may find this pacing frustrating.
The documented extension abandonment noted in published third-party coverage creates additional risk for teams relying on specific third-party integrations. Teams unwilling to maintain custom solutions or absorb ecosystem uncertainty should weigh this carefully.
Furthermore, Oxygen’s single-tier, lifetime-only model—while simple—offers no lower-cost entry point for evaluation or small projects. The $99 lifetime commitment, though modest, is non-subscription and non-refundable after 60 days.
Version History and Long-Term Maintenance
Both builders provide version history access, but formats differ:
| Aspect | Oxygen | Bricks |
|---|---|---|
| Archive access | Public release archive with download portal | Account-based, no public archive |
| Release categorization | Explicit “maintenance” vs. “feature” labels | Continuous changelog |
| Version numbering | Semantic (4.9.6, 6.1.3) | Semantic (implied by update mechanism) |
| Dated announcements | Yes (specific dates noted in announcements) | Not publicly dated in provided material |
| Backward-compatibility notices | Limited; test-driven validation required | Limited; test-driven validation required |
Neither vendor’s documentation provides explicit long-term support commitments for specific version branches. Teams maintaining sites across multiple builder versions must plan for testing rather than relying on documented compatibility windows.
Conclusion
This wordpress builder review of license structure and update documentation reveals two valid but divergent approaches. Bricks offers tiered flexibility with evolving site limits, documented through forum announcements and official pricing pages. Oxygen provides radical simplicity with a single unlimited-site lifetime license, documented through its official pricing page and release archive.
For developer workflow tools evaluation, the choice between them hinges on tolerance for subscription management versus one-time purchasing, preference for rapid feature iteration versus stability-focused maintenance releases, and comfort with each ecosystem’s third-party trajectory. Both require proactive backup practices before any license or builder migration. Neither provides comprehensive backward-compatibility guarantees in their public documentation—testing remains the developer’s responsibility.
Check Beaver Builder’s current pricing
Check Elementor’s current pricing
This post contains affiliate links. If you purchase through our links, we may earn a small commission at no extra cost to you.
