Most WordPress agencies do not start with an automation problem. They start with a visibility problem.
A client asks whether a site is healthy. A plugin update looks harmless, but nobody remembers which sites depend on it. SSL is close to renewal. A maintenance action worked on one site but failed on another. Before you can automate safely, you need a clear view of what is happening across the sites you already manage.
That is why Aura starts with SiteAgent: a free WordPress plugin that gives useful, authenticated visibility without turning the plugin into a paywall trap.
Visibility is the first layer of safer operations
Automation is tempting because it promises speed. But without context, speed becomes risk.
A safer agency workflow starts with questions like:
- Which sites are connected and reachable?
- Which plugins, themes, and WordPress versions are installed?
- Which sites have updates waiting?
- Which sites show signs of health, SSL, or uptime issues?
- Which actions were run, by whom, and with what result?
SiteAgent is designed to expose the site-side signals Aura needs for those workflows. It gives the dashboard a reliable way to understand a WordPress site before Aura Pro/Agency starts layering on scheduled rollout, backup guards, vulnerability context, provider operations, and reporting.
Why keep SiteAgent free?
Because the plugin is the trust layer.
Agencies should be able to install it, inspect the public repository, connect a site, and get meaningful value before they decide whether the SaaS automation layer is worth paying for. A free plugin that does nothing useful until you upgrade would be a bad product and a bad WordPress.org citizen.
So the model is intentionally simple:
- SiteAgent: free visibility and basic authenticated site context.
- Aura Free: a small operational layer for early site visibility.
- Aura Pro/Agency: paid SaaS workflows for teams that need fleet rollout, provider operations, backup/rollback safety, vulnerability insights, reports, and support.
That separation matters. The plugin should remain useful. The SaaS layer should earn the upgrade.
What SiteAgent should help agencies see
A good agency operations layer needs more than a green/red status indicator.
Useful WordPress visibility includes:
- Site health and environment context.
- Installed plugin and theme inventory.
- Update availability for plugins, themes, translations, and core.
- Authenticated maintenance actions.
- Uptime and SSL context from the Aura side.
- Action history that helps explain what changed.
Some of that comes from the WordPress site. Some of it comes from Aura. The point is to combine both sides into one operational picture.
What it does not mean
SiteAgent-first does not mean unsafe auto-updates.
For Aura, safe rollout has to respect guardrails:
- WordPress core remains manual unless a separate plan explicitly changes that.
- Real rollout focuses on plugins, themes, and translations.
- A site should be connected before rollout.
- High or critical vulnerability context should affect eligibility.
- Recent backup state matters before changes run across a fleet.
That is the difference between useful operations software and a dangerous bulk-update button.
Where Aura Pro fits
Once an agency has visibility, the next problem is coordination.
Aura Pro/Agency is where the SaaS control plane belongs:
- Scheduled rollout policies.
- Fleet workflows across client sites.
- Backup and rollback-aware history.
- Provider operations around DNS, CDN, hosting, and cache.
- MCP / AI-agent tools for operational workflows.
- Client-ready reports and support paths.
This is the paid value: not hiding basic plugin functionality, but making the entire operation safer and more scalable.
The launch path
Aura is currently moving through early-access positioning. The goal is to validate the SiteAgent-first story with agencies that manage real WordPress fleets, then open the broader launch once the workflow is sharp enough.
If that sounds like the way you already manage client sites — too many dashboards, too much update risk, not enough operational visibility — start with SiteAgent or join the Aura private preview.