Full-page caching
Serve cacheable pages closer to visitors while your existing server stays the source of truth.
CyberPanel Edge
Full-page edge caching for the sites you already run. Keep your origin, review every DNS change, and share one allowance across every location.
No card required · Keep your existing hosting · Guided setup
Hosting provider? Become a partnerDownload WordPress pluginRead the setup guideCUSTOMER WALKTHROUGH
Seven chapters, at your pace. Follow the written steps while you set up your workspace; the walkthrough never changes your account, payment, DNS, or WordPress site.
01 · CHOOSE A PLAN
Choose a plan from this page to open the Edge signup journey. Create an account, verify your email, and continue to the saved plan selection. Compare bandwidth, domains, cache storage, and request limits. One plan is shared across your connected domains and locations.
Free collects no payment. For a paid plan, review the displayed monthly fee and overage terms; you must choose or add a payment card before confirming the first charge.
View plans →Open Manage plan and renewal for your existing selection. Do not create another account or plan to work around a pending activation.

02 · ACTIVATE THE PLAN
On your saved plan page, use the displayed activation or payment action. Follow Activation progress until the plan is Active. Regional storage checks must pass before the allowance can be used.
Check status now reads your saved status; it does not charge your card or start activation. A paused network check is not a successful activation.
Read the step marked Action needed or Paused. Stay on this same saved plan and use its offered retry or resume action. If payment status is uncertain, review the existing invoice instead of starting another payment. Send support the plan reference if the problem continues.

03 · CONNECT DNS
Open DNS connections. Use an existing connection on your own account or add a new provider. For Cloudflare, use a token restricted to Zone Read and DNS Edit for the zone you will connect. Enter it on the platform page, never in a support message.
Only enabled connections are available for setup. Saving a connection does not verify its provider permissions or change your website traffic; provider access and ownership are checked during domain setup.
Open DNS connections →For validation or credential-encryption errors, the page keeps the form open and shows what needs attention. Correct the fields, re-enter your credentials, and save again. If the result is interrupted or uncertain, check the saved list before submitting again. If every saved connection is disabled, add a new enabled connection. Existing records are retained.

04 · ADD YOUR SITE
Choose Connect a domain, select your DNS connection, and enter the exact hostname visitors use. The origin IP is your existing web server, not an Edge address. The origin TLS hostname must match a valid certificate served by that web server.
Use Save & continue only after checking these values. Saving setup does not approve the DNS change.
Connect a domain →Correct validation errors before saving. If an incorrect IP or TLS hostname has already been saved, stop before activation and contact support with the domain reference. Self-service editing of that saved origin is not available yet; do not delete DNS records or create duplicate enrollments to restart.

05 · ACTIVATE THE DOMAIN
Use Check DNS ownership now to publish and check the unique ownership TXT record. Follow the origin, plan, and regional readiness checks. Use Refresh DNS preview to inspect the exact proposed website-routing changes.
Read the current records and proposed changes before choosing Approve & queue activation. The queued job is not the same as Active. A site is not marked active until the public path verifies successfully.
Read the reported step and use Check status now after resolving the cause. If the page offers Discard unstarted activation, it can discard only an approval whose DNS operation has not begun; then refresh and review the preview again. Otherwise keep the same setup and contact support with the domain reference. Do not assume an interrupted request changed nothing.

06 · APPROVE WORDPRESS
Download CyberEdge Cache 0.4.8. In WordPress, upload the ZIP under Plugins → Add New → Upload Plugin, then activate it. Open Tools → CyberEdge Cache → Connect to CyberEdge.
Sign in to the same platform account, check the exact site shown, then choose Approve and return to WordPress. If you started the connection earlier, use the saved continuation shown by domain setup. Approval grants access only to that domain's purge connection, not your password, billing, or DNS credentials.
LiteSpeed Cache is not required. An existing LiteSpeed Cache installation may remain for origin optimization; do not disable login, cart, or checkout protections to force a HIT.
Follow the saved plan or domain link if setup is still pending. For a temporary connection check failure, use Check connection again. If the secure attempt expires or WordPress does not accept the return, go back to Tools → CyberEdge Cache and start Connect to CyberEdge again. Never reuse or share an authorization URL.

07 · CHECK HIT AND PURGE
In Tools → CyberEdge Cache, use Check cache status. This checks the public homepage without your WordPress login cookies and reads X-CyberEdge-Cache. The first eligible request may be MISS; check again for HIT.
Also test the public page in a fresh private browser session. Logged-in, cart, checkout, and other personalized requests must bypass shared caching. A browser reload with cache bypass enabled is not the same test as an anonymous normal visit.
Use Purge worldwide once, inspect the delivery and queue status, then check the page again. Queued is not delivered: the worker must process the event before you rely on a fresh response. Check a real content update too. Confirm bandwidth and allowances in your platform Overview.
View domains and usage →A missing header, non-successful HTTP response, or repeated MISS is not a confirmed HIT. Check routing, plugin connection, page eligibility, and origin response. If purge delivery is unavailable or events remain queued, keep the saved connection and report the visible error to support; do not keep clicking purge or force-cache private pages.

The customer journey
CyberPanel checks ownership, origin TLS, capacity, and public routing. A site is not marked Active until the live route verifies.
Choose a plan and create your account →Compare the allowances, register or sign in, verify your email, and continue to your saved plan selection.
Free collects no payment. Paid plans require a selected or newly added card before the first charge. Follow the saved cycle until its activation checks pass.
Use a connection owned by your account. Disabled connections do not count as ready for setup; provider access and ownership are verified in the next stages.
Enter the visitor-facing hostname, existing public web-server IP, and certificate-valid origin hostname. Double-check these before saving.
Verify ownership, inspect the exact DNS preview, and approve the change. Queued is not Active: wait for readiness and the live public route to verify.
Download CyberEdge Cache 0.4.8 and start Connect to CyberEdge in WordPress. Approve the exact site only after its plan and domain are active, then return to the plugin.
Check X-CyberEdge-Cache on an anonymous successful response. The first request may MISS, then HIT. Confirm a real content update and completed purge delivery separately; private and WooCommerce sessions must stay uncached.
Built for the work
Performance should not require handing over the rest of your stack.
Serve cacheable pages closer to visitors while your existing server stays the source of truth.
Only ready nodes enter DNS. Unhealthy nodes are withdrawn instead of receiving new visitors.
Bandwidth, requests, domains, and storage are managed once across every edge location.
See the records CyberPanel proposes to change before you approve activation.
Your origin address and certificate hostname are verified as separate onboarding gates.
Prior DNS values and activation evidence are retained for a reviewed restoration path.
Simple monthly plans
Requests carry no separate fee on paid plans. Paid bandwidth overage is $0.01 per delivered GB.
Good questions
North America, Europe, and Singapore are live today. Geo-aware DNS routes visitors to a healthy nearby location.
No. Your existing HTTPS server remains the origin. Edge stores eligible responses closer to visitors and fetches from that origin when required.
No. A production WordPress site should install CyberEdge Cache 0.4.8 and use its one-click connection. It marks safe anonymous pages cacheable, protects logged-in and WooCommerce traffic, and triggers a signed worldwide purge after posts, products, stock, themes, or menus change. Without it, CyberEdge only caches responses already marked public by standard HTTP headers. An existing LiteSpeed Cache install may remain for origin optimization.
No. The onboarding flow previews the exact web-routing records involved. Mail, TXT, CAA, and unrelated records are preserved.
Yes. The Free plan collects no payment and includes 10 GB of monthly bandwidth for one domain. Delivery pauses when a free allowance is exhausted.
Have the public hostname, a public origin server IP, an HTTPS port, and a certificate-valid origin hostname ready.
Only after ownership, origin TLS, edge readiness, metering, and the public route are independently verified.
Your next visitor is already on the way
No card required for the free plan. Keep your existing hosting. Need help first? Talk to CyberPanel support.
All seven written chapters remain available without JavaScript. Chapter playback is optional.