Common Questions
Where each request actually goes
Optimization Plugin
User → Origin server (cached). Every request still travels all the way to your data center.
Cloudflare Worker/APO
User → Cloudflare edge (you build & maintain it) → Origin. Generic tooling, your responsibility.
Abilifi
User → Managed WordPress Directory worker → Origin (rarely hit). Built, run, and supported for you.
At a Glance
Side-by-side comparison
| Aspect | Optimization Plugin | Cloudflare Worker/APO | Abilifi |
|---|---|---|---|
| Where it runs | Origin server | Cloudflare edge (self-managed) | Cloudflare edge (managed) |
| WordPress Directory tuning | None — general WordPress caching | None — general-purpose tooling | Purpose-built WordPress Directory worker |
| Who maintains it | You, via plugin settings | You or your developer, directly on Cloudflare | Managed by the Abilifi team |
| Billing | Flat annual license per site | ~$5/month plus Workers usage | Cloudflare base usage + Abilifi credits |
| Support | Standard plugin support | Limited, not client-integrated | Integrated support + AI auto-fix |
Pricing
How each option is actually billed
Three different billing models — a flat license, raw Cloudflare usage pricing, and a managed credit system.
Optimization Plugin
Flat license
- Annual license, per site or bundle
- No separate usage-based network charges
- All bandwidth and CPU cost stays on the origin server
Abilifi
Managed credits
- Client pays Cloudflare directly for base account/usage
- Client pays Abilifi credits for worker logic, updates, support
- Predictable pricing, no custom-script management
Cloudflare Worker/APO
Usage-based
- APO: roughly $5/month
- Plus Workers usage on top, typically
- You carry full Cloudflare config and billing complexity
Before You Start
Two accounts you'll need first
Have both of these ready and logged in before setup begins — the Abilifi team will need access to configure the worker correctly.
1. Log in to Abilifi
Sign in at abilifi.net first. This is where your worker credits, configuration, and support requests are managed.
2. Log in to Cloudflare
Have your Cloudflare account ready with Worker/APO access — Abilifi connects to it, but you keep ownership and billing on the Cloudflare side.
3. Let wpapps deploy it for you
After the technical setup — our team will deploy and configure for your WordPress Directory. Just make sure your Cloudflare Workers Paid plan is active and your Abilifi credits are available.
1. Log in to Cloudflare
For the Edge Worker optimization setup, you can directly use your own Cloudflare Worker / APO account.
A Cloudflare Workers Paid plan is required to use the Edge Worker optimization setup.
2. Log in to Abilifi (Required for AI-powered features)
If you want to use Abilifi-powered features, the wpapps team will create and configure your Abilifi account for you during the setup process.
3. Let wpapps deploy it for you
Our team will handle the technical deployment and configuration for your WordPress Directory.
Additional Abilifi Features
Available Credit-Based Features
Extend your Abilifi setup with additional features powered by credits.
- Configuration and maintenance of the Edge Worker.
- Ongoing updates and performance optimizations.
- AI-powered support, automated monitoring, and fixes.
- Line-by-line visibility into what drives each charge, with every credit mapped to a real operation.
Switching to Abilifi
How the migration actually works
No plugin swap, no manual Cloudflare scripting — the Abilifi team handles setup end to end. Make sure you’ve logged in to both Abilifi and Cloudflare first.
1
Audit setup
2
Connect Cloudflare
3
Deploy worker
4
Monitor
"
Abilifi gave us the edge-performance benefits without asking us to manage Cloudflare billing or write our own worker scripts — and the GeoDirectory-specific tuning is the part a generic plugin just can't do.
Ismi
dibelanda.com site owner
Common Questions
Comparison FAQs
Still solid for simple, single-region sites where you’re cost-sensitive and don’t need WordPress Directory-specific tuning. It’s origin-level optimization, not edge-level.
Yes — both Cloudflare Worker/APO and Abilify run on your Cloudflare account. You keep paying Cloudflare directly for base usage either way.
The managed worker and integrated support depend on active credits — without them, you’d be back to managing Cloudflare configuration and billing directly.
Setup covers auditing your current server, connecting Cloudflare, and deploying the WordPress Directory-tuned worker — ask your account contact for current setup pricing.
Contact Information
Fill up the form and our Team will get back to you within 24 hours.
