WordPress
Every WordPress site reaches a point where the plugin list is the problem. This one is a single Custom HTML block. Nothing gets installed, so there is nothing to update, nothing to deactivate when the site breaks, and nothing that can argue with your theme.
The logos in these examples are well known marks shown as samples, so the widget is demonstrated at a realistic size. They are not customers of DreamWidget and imply no endorsement.
Three steps
Upload your logos, pick a layout, set the colours. Phones get their own settings, which you adjust while previewing at that width rather than guessing.
The editor gives you a single iframe tag. That is the whole integration. No shortcode, no script tag in your header, no functions.php.
Edit the page, add a Custom HTML block, paste, update. In Elementor or Divi, use their HTML widget instead. Same tag either way.
The honest comparison
Plugins are not bad. They are just a heavier thing than this job needs, and the costs show up later rather than on install day.
PHP running on every request. Its own stylesheet and usually jQuery, loaded site wide whether or not the page has a carousel on it. Database rows. An update every few weeks, each one a small chance of a conflict with your theme or your builder. And it has your database credentials, because every plugin does.
One iframe tag on the page that shows it. It loads after your content, from a CDN, in its own frame, so it cannot block your page from rendering and cannot reach into your site. Nothing to update. If you delete the block, it is gone with no leftovers.
The trade is that the widget lives on our servers rather than yours, and it needs a network connection to appear.
Compatibility
Custom HTML block. The block editor's built in one, no extra block library needed.
The HTML widget. Drop it in any column and the widget fits the container it lands in.
A Code module. Same tag, and it respects the row width you put it in.
Switch to the Text tab and paste. The visual editor will not strip it as long as you paste on the Text side.
Works on plans where the Custom HTML block is available, which is where embeds are permitted anyway.
Nothing enqueues styles into your theme, so there is no
specificity war and no !important to write.
Questions
Yes, that is the whole idea here. One iframe tag in a Custom HTML block. Nothing installs, so nothing needs updating and nothing can conflict with your theme.
Yes. Every builder has an HTML or code widget. Because the embed is a plain iframe rather than a script, it does not compete with the builder for control of the page.
It loads in its own frame, after your content, from a CDN rather than your host. It cannot block rendering, and it adds no CSS or JavaScript to your site's own bundle. Give the iframe a height so it does not shift your layout while it loads, which the embed code does for you.
Edit the widget and every page showing it updates. The embed points at the widget rather than carrying a copy, so you never touch the WordPress page again.
Anywhere a Custom HTML block or widget goes, including footers, sidebars and reusable blocks. It is responsive, so it fits whatever width it is given.
No, on any plan including the free one. We serve from a CDN where views cost us nothing, so we do not meter them the way most widget services do.