The update log is the most informative part of the listing
Most theme descriptions promise layouts. Nanosoft's release history shows something less common: six consecutive releases, from version 1.2.5 in January 2023 through 1.3.2, that each updated Slider Revolution, ACF PRO and WPBakery Page Builder in the same entry. The 1.3.2 release, dated 25 September 2026, moves them to Slider Revolution 6.7.58, ACF PRO 6.8.10 and WPBakery Page Builder 9.0.1, and also records a fix headed "Broken Access Control."
That pattern tells you the author treats plugin currency as part of theme maintenance. It is still three separate products with three separate codebases inside your install; what you get is coordinated versions arriving together, not a single thing to keep current.
Read the access-control entry precisely. The changelog names the fix without saying what it addressed, so it shows access handling has been reviewed. It says nothing about whether any particular version is safe for your server, and nothing here is a security assessment.
WPBakery is the page surface, and the theme expects it there
The vendor describes the theme as including Visual Composer (now WPBakery Page Builder), Revolution Slider and Advanced Custom Fields, using a drag-and-drop interface and pre-built elements to assemble layouts. Version 1.2.0 records a fix for layout breaking when WPBakery is deactivated, which is a plain signal that the theme's layouts assume the builder is active rather than treating it as optional.
For your team that means the editing model is WPBakery's, with its own interface and habits, not the block editor. The marketplace attributes list "Gutenberg Optimized: No" — most sensibly read as a statement that the theme's layouts were tuned for the WPBakery workflow, not a claim that blocks stop working.
ACF PRO is where the repeating content lives
A page builder arranges things; custom fields describe things that recur. For an IT services or software company, most of the recurring list is familiar: service blocks, team members, case studies, client logos, pricing tiers. ACF PRO is the part of the bundle that lets you enter those as data once and render them through templates, instead of rebuilding the same layout on every page.
That split is the practical argument for this particular plugin combination in this niche. The builder handles the homepage argument and one-off campaign pages; the field layer handles the content that has to stay consistent across the site. The vendor description does not enumerate the field groups or say how far they are wired into the imported demo content, so inspect the imported site rather than assuming the structure is ready-made.
Above the builder sits an in-house element layer
The changelog traces elements that belong to the theme rather than to WPBakery: an ImageBox element fixed in 1.1.13, a project carousel and video button plus a video lightbox in 1.1.11, background options for rows and sections in 1.1.12, a Google Maps shortcode fixed in 1.1.1, and a full-width page template added in 1.1.10. Those are the pieces you would otherwise approximate with generic blocks, and they are why the theme is more than a skin.
The same history points at where trouble has appeared. Fixes for the frontend editor on the Carousel and ImageBox elements, a canvas effect fix for rows in 1.2.1, and a 1.2.5 fix for layouts breaking after a WPBakery update all land in the visual editing layer. If you hand this to a content team, exercise that surface on a staging copy first.
What the release notes say about the site as a whole
Other entries describe housekeeping that affects the build rather than the design. Version 1.2.8 added the ability to bulk install the plugins and cleared warnings on PHP 8. Version 1.2.9 fixed the Customizer failing on WordPress 6.7. Version 1.3.0 updated WooCommerce templates, and WooCommerce support dates back to 1.1.0. Demo sites were added in 1.1.2 and 1.1.4 — no total demo count appears in the source material, so judge the page inventory from the live preview rather than from tags.
The earliest entries show the ordinary settling of a 2018 theme: option resets fixed in 1.0.2, menu fixes for IE11, a missing icon pack restored across 1.1.7 and 1.1.8. None of it suggests a stalled product.
Declared compatibility, with a date attached
The marketplace attributes observed on 4 November 2026 declare WordPress versions from 6.0.x through 7.0.x, WooCommerce 6.x.x, a responsive layout at four or more columns, widget-ready sidebars, high-resolution assets, and PHP, CSS and JS files in the package, with Firefox, Safari, Opera, Chrome and Edge named among browsers. Those are listing declarations, not a run against your PHP build or plugin set.
Use them to draft a staging checklist. The theme is targeted at "startup, apps and digital technology business" sites, with marketplace tags covering software, SaaS, app landing, product showcase, lead generation, micro site and cryptocurrency — a description of the demo vocabulary rather than of any technical constraint.
Questions & answers
Do I have to keep WPBakery, Slider Revolution and ACF PRO updated myself?
The changelog shows the theme author updating all three with nearly every release, most recently in version 1.3.2. Coordinated versions arrive through theme updates, but the plugins remain separate products from separate vendors with their own interfaces, so updates stay a maintenance item you track.
Can I build the whole site with custom fields instead of the builder?
The vendor describes the plugins as working together, with ACF handling structured content and WPBakery handling layout, and it does not enumerate the field groups. Whether the templates render the content you need from fields alone is something to test on the imported demo rather than assume.
How many demo sites does Nanosoft include?
The changelog records demo sites being added in versions 1.1.2 and 1.1.4 but never states a total, and the marketplace tags do not supply a count. Check the live preview for the layouts you actually need.
