What AVAS replaces, in Elementor terms
The vendor's own summary puts the claim first: a Theme Builder is included and Elementor Pro is not needed. On a normal Elementor build, headers, footers, archive templates and a set of Pro-only Advanced tab controls are what push an agency toward the paid plugin. AVAS lists substitutes for most of that surface — Theme Builder templates, custom headers and footers, Sticky and Custom CSS modules, an Internal URL dynamic tag, and inline editing controls modelled on Pro's document switching.
That changes who has to buy what. If your sites are built on free Elementor and the Pro licence sits with whoever set the project up, AVAS moves the site's structural editing into software you already have running. Read the vendor's claim as scope, not as equivalence: it says the workflow exists outside Pro, not that every Pro feature is present under a different name.
One related detail is worth knowing early. The vendor states that all demos are built with the free version of Elementor, so what you see in the demos is what you can reproduce without buying anything else from Elementor.
Editing a whole site from inside one Elementor preview
The 1 June 2026 release, version 7.0, is where the editor experience became concrete. Elementor's preview gains Edit Header and Edit Footer controls that switch documents in the same tab rather than opening a second one. A separate Edit Page overlay appears on hover over the page content region so you can travel back from a template to the page. The overlays are colour-coded — header, footer and page each get their own treatment — so you can tell which document you are about to change before you click.
That sounds cosmetic until you have spent an afternoon hopping between browser tabs to check whether a nav change broke a page's hero spacing. Same-tab switching keeps the page and its template adjacent, which is the condition where you actually notice the conflict.
Template duplication, added on 21 January 2026 in 6.9.4, belongs to the same workflow. It clones a theme-builder template along with its Elementor content, widgets and settings, and the copy appears in the template list straight away. For a site with a header that needs one variant per campaign, starting from a duplicate rather than from an empty document is the difference between ten minutes and an hour.
The 7.0 changelog also records the unglamorous work behind those controls: a 401 error when switching to header or footer templates, a duplicated Edit Page button, and overlays that blocked widget selection after a switch were all fixed in that release. That history is a reasonable indication of how much the vendor relies on this mechanism, and of how recently it was still settling.
The smaller Pro-like controls that decide how a page looks
Sticky positioning and Custom CSS arrived together in 6.9.1 on 15 December 2025, both described by the vendor as matching what Elementor Pro does on the Advanced tab. In practice they are the two controls that most often make people open a Pro licence in the first place: pinning a container or a callout so it follows the scroll, and writing a rule without editing a child theme file.
The value depends on your discipline. Custom CSS in the builder means styling not tracked in a theme file, which is convenient for a quick fix and awkward when someone else inherits the site. If two people will touch the build, agree where CSS belongs before you start.
The theme also registers more than 3,500 icons in the Elementor icon library, and it lists Google Fonts, Font Awesome and Bootstrap Icons among its integrations. That is a practical rather than a visual point: a large icon set inside the builder means fewer one-off SVG files scattered through a project.
The Internal URL tag and what happens after a demo import
Added in 6.9.5 on 27 January 2026, Internal URL is a dynamic tag in an Avas group inside the Dynamic Tags panel. The vendor says it works across Pages, Posts, Products, Courses, Events, Portfolio, Services and Team, and that links update automatically after a demo import, so you are not hunting down hand-typed URLs pointing at a demo domain.
For a site that mixes content types — a services page linking to case studies that link to products — this is the tag you reach for instead of pasting a permalink. Existing WordPress permalinks are already dynamic; the reported advantage is that it does not require Pro. Treat the automatic-update claim as a reason to test one representative set of links after your own import, especially if the site changes permalink structure later.
A separate widget, Avas User Auth, was added in 7.0.2 on 21 June 2026 for login, signup and account screens. That is another job that would otherwise mean a membership plugin or Pro's form widgets, and it fits the same pattern of keeping the front end inside the theme.
Menu behaviour is a theme setting, not a plugin stack
The vendor lists menu item visibility conditions by User Role, Page, Post, Device and Language, and states that no plugin is required. Conditional menus are usually assembled from role plugins, device-specific CSS and, on a multilingual site, whatever the translation plugin's own menu sync offers. Keeping it in one panel is cleaner to audit, because the rules live in one place rather than across three plugins that each think they own the menu.
Language conditions are the ones to look at closely on a multilingual build. The theme lists WPML among the supported plugins, and a changelog entry from 6.9.15 on 3 May 2026 fixes the Avas Text widget so it filters content per language under WPML. Both suggest translation is treated as an ongoing concern rather than a checkbox.
Alongside the conditional logic, the vendor lists mega menu and side menu layouts, a sticky responsive header, and menu-item callouts that render as highlighted buttons. RTL support, a dark mode option and a cookie notice are listed as theme features too, which puts several of the settings that usually need a small plugin into the options panel.
The 7.0.4 addition: AI Studio, framed as optional
The most recent changelog entry, 9 August 2026, introduces AVAS AI Studio: a workspace for generating and personalising structured site content through the WordPress AI Client. The vendor describes control-by-control previews so you can review individual changes before applying them, plus recoverable backups, a personalisation history, safe rollback, and protection for edits made after AI content lands.
The parts worth weighing are the safeguards, not the generation. Anyone who has replaced a line of copy in bulk and then wanted it back knows that rollback and history are the features that make a content tool usable on a site that already has real text.
The optional Aimogen bridge and the AVAS AI Chatbot widget follow the same split: AVAS controls how the chatbot looks, and Aimogen handles conversations, providers, knowledge, privacy, limits and logs. Note that these sit outside the theme builder and are presented as optional additions. Nothing in the evidence describes how AI Studio behaves on a site with a large existing content set, so that is a question for a staging copy rather than an assumption.
What the listing and the archive actually settle
The demo count is large — the vendor says 80+ Elementor sites, 90+ Elementor widgets — and the marketplace category is corporate/business, though the demos span medical, education, fitness, restaurant, agency and events. Portfolio layouts come with three- and four-column filterable grids and pagination. Server requirements are listed as PHP 7.4 or higher, WP memory of 256 MB, a 64 MB post max size and a max execution time of 120, with a note that this needs raising on slower servers during import.
Two boundaries are easy to misread. Gutenberg Optimized is recorded as Yes in the marketplace attributes observed on 3 November 2026, but that does not mean the theme's demo layouts are block-built; the vendor says the demos are Elementor pages. And the vendor states plainly that demo images are for demonstration only and are not included, so plan on your own photography before launch.
The declared WordPress range runs from 4.9.x through 7.0.x, with WooCommerce 5.x to 9.x, WPML, bbPress, Events Calendar and Bootstrap 4.x listed as compatible. Those are the vendor's declarations, not results from running the theme on your stack, and version lists drift.
Where this lands: AVAS earns its place if you want to keep Elementor Pro off the project and still hand a client a site with editable headers, footers and templates. If you rely on Pro's other features or want block-editor site editing, the Pro substitution argument does not carry the decision on its own.
Questions & answers
Do I need Elementor Pro for the header and footer templates?
The vendor says no. AVAS ships its own Theme Builder with custom header and footer templates, and the demos are built with the free version of Elementor. Sticky, Custom CSS and the Internal URL dynamic tag are described as covering tasks that would otherwise need Pro. Check how the controllers you depend on behave on a staging install before you commit, since the vendor's statement is a scope claim rather than a feature-by-feature match.
Are the demo images included with the theme?
The vendor states that images are used for demo purposes only and are not included. You will need your own photography or licensed assets before a site goes live.
Can I edit menu visibility for specific roles or languages?
Yes, as a theme setting. The vendor lists menu item visibility conditions by User Role, Page, Post, Device and Language, with no extra plugin required for the conditions themselves. Language conditions pair with the listed WPML support, though multilingual menu behaviour is worth testing on your own setup.
Is AVAS block-editor friendly?
The marketplace attribute Gutenberg Optimized reads Yes as observed on 3 November 2026, but the vendor's demo layouts are Elementor pages. Treat that attribute as a compatibility declaration rather than a sign that the theme was designed around the block editor, and test any block-built page you plan to ship.
