Clevera vs OpenStation

Clevera is an AI-powered product that turns screen recordings into narrated tutorial videos and step-by-step help articles. This plugin links your WordPress site to your Clevera workspace so you can build a public help experience on your site without copying embed codes by hand. Once connected, editors can browse Clevera projects from inside the WordPress editor and add the Clevera Help Center block (or Elementor widget) to a page, then pick which project to show. Visitors get that project’s categories, screencasts, embedded videos, and related article content. When you update content in Clevera, the on-site experience reflects those changes on the next load — no re-exporting or republishing in WordPress. What you can do Connect your WordPress site to a Clevera workspace in a few clicks Review a clear connection disclosure and explicitly confirm before any data is sent to Clevera Browse and select Clevera projects inside the block editor and Elementor (for users with content-editing access) Render a public help center for the project chosen on that page Show project categories, screencasts, embedded videos, and related article content Filter and search screencasts by project, category, or keyword where the UI exposes those controls Rotate or disconnect the API key from WordPress, or manage the connection from the Clevera side How the connection works The plugin uses a guided setup flow instead of pasting a raw API key. From Settings → Clevera AI you are sent to Clevera to sign in and select a workspace. Clevera issues a short-lived exchange token; the plugin exchanges it for a site API key bound to your site URL. The key can be rotated automatically on a schedule and you can also rotate or disconnect manually. Requirements A Clevera account — sign up at clevera.ai WordPress 5.8 or later (as required by the plugin) PHP 7.4 or later Elementor (optional; required only for the Clevera Help Center Elementor widget) External services This plugin relies on external Clevera services to connect your site and to load help-center content. By default, the plugin does not start the connection flow until an administrator explicitly confirms the disclosure on the settings screen. https://app.clevera.ai Used for: * The connection flow between WordPress and Clevera * Exchanging the temporary connection token for the site API key * Validating the connection * Loading project, category, screencast, and article data for connected sites * Rotating and disconnecting the site API key Data sent to app.clevera.ai may include: * Site URL * Site name * Return URL for the connection flow * Authorization state token * Site API key in authenticated server-to-server requests * Selected project and content request parameters needed to load help-center data This service is contacted: * When an administrator connects the plugin * When an editor loads Clevera project choices * When the public help center loads data for the selected project * During scheduled connection validation, key rotation, or disconnect operations Terms of service: * https://www.clevera.ai/terms https://share.clevera.ai Used for: * Rendering Clevera-hosted embedded videos inside the help center Data sent to share.clevera.ai depends on the embedded player URL and may include: * The embed identifier * An embed access token generated by Clevera * The selected content language * Standard browser request metadata This service is contacted: * When a visitor loads a help center page that displays a Clevera video embed Privacy Site owners should review their own privacy disclosures if they use the public help center, because visitor browsers may load embedded content and assets from the Clevera domains above. The plugin’s connection flow is opt-in. An administrator must explicitly confirm the connection disclosure before site URL, site name, return URL, and a signed state token are sent to Clevera. Privacy-related information for the Clevera service is described in the terms linked in External services.

wp-admin forgets. OpenStation doesn’t. You know the moment. You’re deep in a post and you need one image from the Media Library. You click over, find it, click back, and everything you had going is gone. Your scroll position, your half-typed thought, the three other things you had queued up in your head. That’s not a bug you hit. That’s the design. wp-admin shows you one screen at a time, and every navigation throws the last one away. It has worked this way since 2003, like a fridge that empties itself every time you close the door. WordPress has rebuilt almost everything else. The editor, the site editor, the patterns, the styles. The admin’s one-screen-at-a-time model is the layer nobody touched. OpenStation touches it. Install it and admin screens become draggable, resizable windows. Edit a post while the Media Library sits open next to it. Drag an image from one window straight into the other. Keep comments open in the corner. Reload the browser and your window layout — open pages, positions, sizes, and window states — comes back where you left it. OpenStation itself is free, GPL, and opt-in per user. One click in the admin bar turns it on for you. One click turns it off. Nobody else on your site sees anything change, and deactivating the plugin restores the classic admin exactly. No Core patches and no lock-in. Optional AI providers may charge for their service. Built and maintained by Automattic, the company behind WordPress.com, Jetpack, WooCommerce, and Tumblr. Work on more than one thing at once Admin pages open as windows, including pages added by most other plugins. Drag them, resize them, snap them, tile them, minimize them to a taskbar. The admin menu becomes a dock of icons. Two editors open at once is one click away. Never lose your place Moving between open windows leaves each page in place. Across reloads, OpenStation remembers your open pages, window positions, sizes and states, virtual desktops, and focus. Closing a window with unsaved changes warns you first. A desk you can actually put things on Drop posts, media, and links right onto the wallpaper. Sort them into folders. Trash them to a Trash that actually holds things. The stuff you’re working on this week can just sit out where you can see it. One desktop per job Virtual desktops, the way your operating system does them. One for writing. One for the store. One for comment triage. One for that redesign you keep poking at. Switch between them without closing anything. Find anything with Cmd+K The full WordPress command palette, plus slash commands from your plugins, all under one keystroke. Turn on the optional AI assistant and you can ask it things like “which post had the comment asking for the recipe?” and it searches your own content to answer. (Requires an AI provider configured in Settings → Connectors on WordPress 7.0+. Details under “External services” below.) See how your site fits together The Corkboard is an interactive, zoomable map of how your posts, pages, and products link to each other. Pan around it. Find the orphans. Find the hubs. Running a store? Orders, Products, Coupons, and Customers become browsable folders with stock and sale ribbons. Open a customer to see their lifetime spend and what they buy most. Follow a product to its buyers, or a coupon to who redeemed it. Make it yours Wallpapers, from color presets to animated scenes to your own photo. Live widgets pinned to the desktop: drafts, stats, recent comments, a focus timer. Uploadable desktop themes, including a built-in Legacy theme that brings the old WordPress blue back in one click. And Mio, a soft-body desk companion that drifts across your wallpaper and gets bumped around by your windows. Off by default. You’ll turn it on. For developers Extend OpenStation through documented PHP and JavaScript APIs. Register windows, icons, wallpapers, widgets, commands, and settings tabs through stable openstation_register_* PHP APIs and a typed JavaScript API; customize dock items through documented hooks; add AI tools with the WordPress Abilities API. Copy-paste examples live in the developer docs on GitHub. External services No external service is required for OpenStation’s desktop interface. The optional AI Assistant and two user-initiated enrichment features make the external requests described below. AI Assistant The optional AI Assistant sends data to the AI provider you configure in WordPress’s Settings → Connectors (for example OpenAI, Anthropic, or Google). Generation is routed through WordPress 7.0’s built-in AI Client, which supplies the credentials stored in Connectors. The plugin never handles an API key itself. With no provider configured in Connectors, no external AI requests are made. When the AI Assistant is enabled and a user invokes it (via Cmd+K or the slash-command palette): What is sent: the user’s prompt, the conversation history for the active session, and tool-call metadata. The plugin’s built-in tools (search_posts, search_pages, search_comments) run WordPress’s native keyword search and may include excerpts of the matching posts/pages/comments in tool results, which are then sent back to the provider as part of the agentic loop. When it is sent: on user-initiated AI requests, and (if an administrator enables “Score new comments with AI”) on comment-save hooks for spam analysis. Posts, pages, and taxonomy terms are not sent automatically. Why it is sent: to obtain model completions and tool-call decisions that drive the AI Assistant. Who provides the service: whichever provider you configured in Settings → Connectors. Which provider (and endpoint) receives the data depends entirely on that configuration. Review the chosen provider’s own terms and privacy policy (e.g. OpenAI, Anthropic, or Google). URL shortcut favicons When an authorized user creates a desktop shortcut to an external URL, OpenStation asks that URL for its page HTML and favicon so the shortcut can display the site’s icon. The request is made from your WordPress server and sends the requested URL, the server’s IP address, an OpenStation user-agent string, and normal HTTP request metadata to the operator of that site. This happens only when a user creates the shortcut. The destination site’s terms and privacy policy apply. WordPress.org plugin information When an authorized user opens or refreshes parts of OpenStation’s Plugins window, OpenStation may request public plugin details, update metadata, and review excerpts from WordPress.org. These requests send plugin slugs, the site’s locale, and normal HTTP request metadata to WordPress.org. This information is used only to display and manage plugins. Review the WordPress.org Privacy Policy. OpenStation’s OAuth relay does not contact a service by itself. Third-party plugins that configure the relay may contact their own providers and are responsible for disclosing those services. Credits OpenStation is brought to you by Automattic. The plugin is open source under GPLv2-or-later; contributions are welcome on GitHub. Third-party libraries The plugin bundles the following third-party JavaScript library, loaded on demand only when a feature that needs it is in use: PixiJS (MIT License) — used by the Corkboard window, built-in canvas wallpapers (e.g. the animated WordPress logo), the Mio desk companion, and the Inkfall typing game. PixiJS is loaded from the plugin’s own assets/vendor/ directory; no CDN requests are made. Data files The Inkfall game’s word list (assets/games/inkfall/words.txt) is generated from the following sources (attribution also ships in the file’s header): FrequencyWords by Hermit Dave (CC-BY-SA 4.0) — English word-frequency ranking derived from the OpenSubtitles corpus. english-words by dwyl (Unlicense) — used as a validity filter. LDNOOBW English list (CC-BY 4.0) — used as an exclusion filter.