If you manage WordPress sites for clients, your browser probably looks like ours used to: a Cloudflare tab for DNS and caching, a hosting dashboard for servers and applications, a CDN dashboard for media, and a WordPress admin screen for every site that needs attention. Every cache purge, update check, uptime question, and "is this safe to roll out?" moment means switching contexts across tools that do not understand each other.
We built Aura to collapse that operational layer into one place. The current story starts with SiteAgent, a free WordPress plugin that gives useful site visibility, then grows into Aura Pro/Agency for the SaaS workflows agencies need: provider operations, safe rollout, backup guards, reporting, and support.
The problem: WordPress operations are scattered across providers
Most agencies, freelancers, and product teams we talk to have landed on a similar setup without really choosing it:
- Cloudflare for DNS, WAF, and CDN on the edge.
- Bunny CDN for media-heavy pull zones and storage zones — cheaper and faster than pushing everything through Cloudflare for large files.
- Cloudways (or similar) for managed application servers on top of DigitalOcean, Vultr, or AWS.
- A portfolio of WordPress client sites with different plugins, themes, update risk, uptime needs, and maintenance expectations.
Each of those tools is genuinely good at its job. The problem isn't any individual provider — it's the seams between them. When a client reports a slow page, the workflow is: log into Cloudflare, check the zone; log into Bunny, check the pull zone; log into Cloudways, check the server; SSH in, check the app. By the time you have an answer, you've burned thirty minutes on context switching.
That is the frustration Aura is designed to solve — not by replacing good providers, but by giving agencies one operational layer above them.
What Aura is built around
Aura is in active development. The launch direction is now SiteAgent-first: make the free WordPress visibility layer genuinely useful, then add the paid SaaS control plane around safety, rollout, provider actions, and reporting.
Free SiteAgent visibility first
SiteAgent is the free WordPress plugin behind Aura. It exposes authenticated health, inventory, update, and maintenance context with zero frontend impact. That means an agency can start by seeing what is happening across sites before automating anything risky.
A unified resource view
Aura is designed to pull WordPress sites and provider resources into a single, searchable operational view. Every resource should carry a consistent shape — provider, type, status, links, and safety context — so teams stop memorizing which dashboard lives where.
Safe actions before broad automation
The common operations — update visibility, maintenance actions, provider tasks, cache purges, and rollout workflows — need confirmation, audit trails, and safety checks. Aura Pro/Agency is where those SaaS-backed workflows live. The plugin stays useful; the paid layer adds fleet operations.
Why an operations layer, not another host
There's a reasonable question here: why not build yet another host and compete head-on? The answer is that we think the bottleneck for most agencies isn't the providers themselves — it's the operational overhead of stitching WordPress, hosting, DNS, CDN, cache, updates, reporting, and support into one workflow.
What's missing is the layer above: a place where the resources you already own behave like they know about each other. That's the problem Aura is built around, and it's why our connector-based architecture treats each provider as a first-class integration rather than something to abstract away.
Where we're going
Short-term roadmap, roughly in order:
- More providers. AWS, Hetzner, Vercel, DigitalOcean, and WP Engine are all on the list. If there's one you want badly, tell us.
- Richer actions. Bulk cache purges across linked zones, scheduled reboots, cron-triggered deploys, SSL health checks.
- Proper alerting. Status changes, provider outages, failed actions — delivered where you actually read them (email today; Slack and webhooks next).
- Audit and compliance. Exportable action logs, per-user permissions inside an organization, and SSO.
Longer term, we think there's a real opportunity for an opinionated "do the right thing" layer on top. One that knows your stack well enough to suggest what to do next — "this pull zone hasn't been hit in 30 days, archive it?", "your Cloudways server is on an outdated PHP, here's a one-click upgrade" — not just expose every button every provider ships. Tooling that closes the loop, instead of widening it.
For WordPress teams, SiteAgent is the entry point. Aura Pro is the next layer when visibility becomes a need for safer fleet operations.
FAQ
Is Aura a replacement for Cloudflare, Bunny, or Cloudways?
No. Aura is a management layer that sits on top of the accounts you already have. You keep using those providers; Aura just gives you one place to work from.
Where are my provider credentials stored?
Encrypted at rest in our database using AES-256-GCM, with a per-installation key. Aura only decrypts them at the moment a request is made to a provider, and we never log the plaintext. Read more in our privacy policy.
Which providers are part of the Aura direction?
Aura is being built around WordPress, SiteAgent, and common agency infrastructure providers such as Cloudways, Cloudflare, Bunny CDN, and Hostinger. Exact availability can differ during private preview, and more providers will be prioritized from real agency workflows.
How do I get started?
Start with SiteAgent if you want to understand the free WordPress visibility layer, or join the Aura early-access list if you want the private preview for agency fleet operations.
Can I follow along as you ship?
Yes — this blog is where we will publish product updates, practical WordPress operations guides, and launch notes. Check back in as we build the content pipeline.
Thanks for reading. If you have been looking for a safer WordPress operations layer across client sites, join the private preview and tell us where your current workflow breaks.
— The Aura team