How CoreSpeed Manages and Protects Your WordPress Website

CoreSpeed is SiteCare’s fully managed WordPress platform.

It is designed for organizations that want their website infrastructure managed with the same discipline applied to other important business systems: controlled access, documented changes, consistent configuration, dependable performance, and fast recovery.

Over years of managing WordPress websites, we have found that the most reliable environments share a few important characteristics:

• Production systems are protected.
• Infrastructure is managed consistently.
• Changes follow a defined process.
• Website traffic is filtered and optimized before it reaches the server.
• Performance does not depend entirely on WordPress generating every page request.
• The team responsible for the outcome has the access needed to manage the complete delivery path.

Those principles shape every layer of CoreSpeed.

Rather than providing an open server environment for customers to administer independently, SiteCare manages the complete website delivery stack, including Cloudflare, DNS routing, edge caching, server configuration, WordPress performance, code deployments, security controls, backups, and production support.

The result is a faster, more stable, and more maintainable WordPress platform.

A Managed Edge and Origin Architecture

CoreSpeed is not a single server or a traditional hosting account. It is an integrated architecture with several coordinated layers.

A typical request follows this path:

Visitor → Cloudflare edge network → CoreSpeed caching and routing → CoreSpeed origin server → WordPress

Each layer has a specific role.

Cloudflare edge layer

Cloudflare sits in front of the website and acts as the first point of contact for incoming requests.

It manages DNS resolution, proxies website traffic, applies routing logic, serves cached responses, and reduces the number of requests that need to reach WordPress.

CoreSpeed origin layer

Behind Cloudflare, the CoreSpeed origin servers run a standardized and tiered configuration managed by SiteCare.

CoreSpeed uses server-level automation to apply baseline tuning for PHP-FPM, Redis, and MySQL. Server configurations are assigned by tier so resources and application settings can be matched to the needs of the websites hosted on each server.

WordPress integration layer

A companion WordPress plugin connects WordPress activity with the CoreSpeed edge caching system.

When content changes, the plugin communicates with the Cloudflare Worker so the relevant URLs can be revalidated. It also provides the ability to revalidate all URLs when a broader cache refresh is needed.

Managed operations layer

SiteCare monitors and troubleshoots activity across the platform using server logs and internal diagnostic tools.

Our CoreSpeed log tooling can surface traffic patterns such as top IP addresses, user agents, referrers, query strings, and recent PHP fatal errors. This gives our team direct visibility into both traffic behavior and application-level failures when investigating an issue.
Together, these layers allow SiteCare to manage the website as a complete system rather than treating hosting, DNS, caching, security, and WordPress as unrelated services.

Cloudflare Is a Core Part of CoreSpeed

Cloudflare is sometimes described as a DNS provider or content delivery network. Within CoreSpeed, its role is considerably broader.

It is the programmable delivery layer between website visitors and the CoreSpeed origin server.

This allows SiteCare to make intelligent decisions about how requests are routed, cached, refreshed, and passed to WordPress.

Serving pages from the edge

WordPress normally generates a page by processing PHP, querying the database, running plugins, assembling the response, and sending it back to the visitor.

That process can be resource-intensive, particularly on websites with older themes, complex plugins, large databases, or significant traffic.

CoreSpeed uses a custom Cloudflare Worker to store pages in Cloudflare’s Cache API. Pages are also stored in a distributed key-value store to reduce the effect of cold cache requests and avoid sending unnecessary traffic back to the origin.

Once the cache is warm, visitors rarely need to reach the origin server directly. They can receive a response from a Cloudflare data center closer to them.

This provides several benefits:

• Faster page delivery
• Lower time to first byte
• Reduced demand on PHP and MySQL
• Greater resilience during traffic increases
• More consistent performance across geographic regions
• Less sensitivity to inefficient plugins or application code

The origin server remains important, but it is no longer responsible for generating every public page request.

Keeping content current without sacrificing speed

Caching improves performance, but it must also respect the way WordPress is used.

When someone updates a page or post, visitors expect to see the new version promptly. A simple purge-based cache system removes the old page and waits for the next visitor to rebuild every caching layer.

That approach can create repeated performance slowdowns on websites that are updated frequently.

CoreSpeed uses a revalidation strategy instead.

When content is updated, the WordPress plugin notifies the Cloudflare Worker. The Worker marks the existing page as stale and refreshes the current version from the origin in the background. A visitor can still receive the previous cached response immediately while the updated version is being prepared for subsequent requests.

This creates a practical balance:

• Editors can continue updating WordPress normally.
• Visitors continue receiving fast responses.
• The cache refreshes without requiring every visitor to wait for WordPress.
• Frequently updated websites do not repeatedly lose the benefit of a warm cache.

Preventing unnecessary cache bypasses

Many caching systems perform well under ideal conditions but become less effective when URLs contain tracking parameters, cookies, or other request variations.

Marketing links often include parameters from advertising, email, analytics, and campaign platforms. Those parameters may not change the actual page content, but they can cause traditional caching systems to treat each request as unique.

This is especially problematic because campaign landing pages are often among the most frequently requested and commercially important pages on a website.

The CoreSpeed Worker can centrally define which query parameters should affect caching and which can be safely ignored. It can also account for cookies and headers that would otherwise cause a cache bypass even when the response is suitable for caching.

This allows SiteCare to preserve accurate website behavior while keeping important public pages fast.

Reducing dependence on the origin server

The CoreSpeed page cache is designed to serve requests from the edge, reduce cold starts, prevent unnecessary cache bypasses, improve slow origin response times, and reduce load on the production server.

This is particularly valuable for websites that:

• Have high server response times
• Use resource-intensive themes or plugins
• Publish or update content frequently
• Receive campaign-driven traffic
• Have a low cache hit rate on traditional hosting
• Need performance to remain consistent during traffic spikes

Cloudflare does not replace the CoreSpeed origin. It allows the origin and WordPress application to operate more efficiently.

Why SiteCare Manages the Cloudflare Zone

For CoreSpeed, using Cloudflare nameservers is not simply a preference about where DNS records are stored.

It gives SiteCare the ability to manage the delivery layer on which CoreSpeed depends.

The Cloudflare zone provides the connection between:

• The public domain
• The Cloudflare proxy
• CoreSpeed Workers
• Cache and revalidation logic
• Preview routing
• The CoreSpeed origin server
• Production cutovers and recovery decisions

For a Worker to route traffic to different origins, the DNS must be proxied through Cloudflare, the Worker must be installed in the account controlling the domain, a route must direct requests through the Worker, and the necessary DNS records must exist within that zone.

This is why SiteCare-managed Cloudflare nameservers are an architectural requirement for the complete CoreSpeed experience.

When the Cloudflare zone is controlled by a separate provider, MSP, or unrelated account, SiteCare may not be able to reliably:

• Install and manage the required Workers
• Apply routing changes
• Coordinate cache behavior with WordPress
• Preview the CoreSpeed origin using the live domain
• Complete rapid production cutovers
• Maintain consistent proxy and performance settings
• Diagnose the full request path
• Prevent conflicting Cloudflare rules or features
• Take responsibility for the entire delivery stack

A shared or fragmented model can leave one organization managing DNS, another managing Cloudflare settings, another managing the server, and another managing WordPress.

That structure may be workable for self-managed infrastructure, but it makes it difficult for any one team to accept responsibility for performance, routing, and recoverability.

CoreSpeed is designed around a simpler operating model: SiteCare manages the web delivery path from Cloudflare through WordPress.

Nameserver Management Does Not Change Domain Ownership

Delegating nameservers to SiteCare’s Cloudflare environment does not transfer ownership of the domain, website, content, or business data.

The domain remains registered to the customer through its domain registrar.

Nameservers determine which DNS platform answers requests for the domain. They allow SiteCare to manage the records and traffic controls required to operate the website on CoreSpeed.

Other business services can continue using the same domain, including:

• Email
• Microsoft 365 or Google Workspace
• Verification records
• Third-party applications
• Subdomains
• Customer portals
• Remote access services

The DNS transition should preserve the records those services depend on while allowing SiteCare to manage the web traffic associated with CoreSpeed.

For larger organizations, this may require coordination with an internal IT team or MSP. That collaboration is welcome. The goal is not to replace the organization’s broader technology partner. It is to give SiteCare responsibility for the Cloudflare layer required to deliver and support the website.

Safer Website Previews and Migrations

Cloudflare also allows SiteCare to preview a website on CoreSpeed before changing the public production origin.

The CoreSpeed preview Worker can route an individual review session to the new CoreSpeed server while all other visitors continue using the existing production server.

A preview cookie is set for the reviewer, and caching is disabled for that session so the new origin can be evaluated accurately. Public visitors remain unaffected.

This provides a safer migration workflow:

1. The website is prepared on CoreSpeed.
2. A designated reviewer accesses the normal domain through a private preview session.
3. The reviewer sees the CoreSpeed origin while the public still sees the current production website.
4. Issues can be identified and corrected before launch.
5. The Cloudflare route can be changed from preview behavior to the production page-cache Worker after approval.

This is more representative than reviewing a temporary URL because the website can be tested through its actual domain, routing, cookies, redirects, and application behavior.

It also makes the final cutover more controlled. Because traffic routing is managed through Cloudflare, a launch does not need to depend on a prolonged public DNS propagation window.

A Consistent Cloudflare Configuration Matters

Many hosting providers also use Cloudflare behind the scenes. This can create a layered configuration where traffic passes through both the customer’s Cloudflare settings and the hosting provider’s Cloudflare environment.

Those overlapping layers can introduce behavior that SiteCare cannot fully control.

For example, a hosting provider may inject cookies or activate bot-management features that cause otherwise cacheable responses to bypass the edge cache. The CoreSpeed Worker is designed to sit in front of those responses and retain control over caching behavior where possible.

Managing the Cloudflare zone allows SiteCare to apply one coherent set of rules rather than relying on assumptions about configurations controlled by multiple parties.

This consistency supports:

• Predictable caching
• More reliable troubleshooting
• Fewer configuration conflicts
• Controlled routing
• Faster incident response
• Clear accountability

Fully Managed by Design

Traditional hosting generally gives customers a server account and leaves them responsible for deciding how it should be managed.

CoreSpeed takes a different approach.

SiteCare manages the production environment on the customer’s behalf, including:

• Cloudflare and web-facing DNS
• Edge routing and caching
• Hosting infrastructure
• PHP, Redis, and MySQL configuration
• WordPress performance
• Security controls
• Backups and recovery
• Software maintenance
• Code deployments
• Production troubleshooting

This allows us to operate the platform consistently and take meaningful responsibility for its performance and reliability.

A Protected Production Environment

A live website should be the final destination for tested and approved changes, not the place where development work happens.

CoreSpeed protects production by routing file, code, and database changes through managed workflows rather than allowing them to be made directly on the server.

This gives every website on the platform a more predictable operational model.

Changes can be:

• Documented
• Reviewed
• Tested
• Deployed consistently
• Validated after launch
• Reverted when necessary

This approach reduces unexpected downtime and makes troubleshooting more efficient.

Version-Controlled Code Deployments

CoreSpeed websites use version control as the foundation of the deployment process.

Version control provides a reliable history of the website’s code, including:

• What changed
• When it changed
• Who made the change
• Which version is currently deployed

This creates a clear source of truth for the website.

When code is uploaded directly to a production server, those changes fall outside the deployment history. They can also be overwritten during future maintenance, software updates, or deployments.

By keeping production code aligned with version control, CoreSpeed allows our team to deploy confidently and restore a previous code version quickly when needed.

Managed File Workflows

CoreSpeed does not rely on traditional FTP access for production file management.

Website files are handled through managed deployment and content workflows.

This protects the production environment from common risks such as:

• Accidental file deletion
• Undocumented code changes
• Overwritten customizations
• Compromised FTP credentials
• Malware introduced through uploaded files
• Differences between the live server and the approved codebase

For routine documents, images, and downloadable resources, the WordPress Media Library is often the most appropriate option.

For organizations that distribute larger assets such as firmware, software downloads, product files, or technical documentation, SiteCare can help establish a purpose-built delivery workflow. Depending on the use case, that may include WordPress, managed object storage, Cloudflare delivery, or another appropriate solution.

The objective is not simply to place files on a server. It is to make sure those files remain secure, organized, scalable, and reliably available to customers.

Managed Database Changes

CoreSpeed production databases are managed by SiteCare rather than exposed through phpMyAdmin.

Direct SQL access can be efficient, but it also allows immediate and potentially irreversible changes to the live website.

A single query can unintentionally alter or remove:

• Website content
• User accounts
• Orders or form submissions
• Plugin settings
• Serialized WordPress data
• Relationships between records

For that reason, production database work follows a controlled process.

Our team can perform tasks such as:

• Search-and-replace operations
• Product or company name updates
• URL migrations
• Data cleanup
• Configuration changes
• Content corrections
• Database imports and exports

These changes can be backed up, tested, reviewed, and validated before the work is considered complete.

This provides the efficiency of database-level work while preserving the integrity of the production environment.

Precise Recovery Options

Backups are an essential part of website management, but they are only one component of a complete recovery strategy.

A full-site restore can recover an environment, but it may also reverse unrelated content, form submissions, orders, or changes created after the backup.

CoreSpeed combines backups with:

• Version-controlled code
• Managed deployments
• Cloudflare routing
• Edge caching
• Documented database work
• Standardized server configuration

This gives SiteCare more precise recovery options.

Depending on the issue, our team may be able to:

• Revert a specific code deployment
• Restore an individual file
• Reverse a targeted database operation
• Route traffic away from an unhealthy origin
• Restore the full website
• Reapply a known server configuration

The more consistently a system is managed, the more confidently it can be restored.

Security Through Controlled Access

One of the most effective ways to protect a production system is to limit the number of ways it can be changed or accessed.

By not exposing FTP, SSH, or phpMyAdmin as standard customer-facing services, CoreSpeed reduces the number of credentials, services, and entry points that attackers can target.

This helps reduce risks associated with:

• Stolen credentials
• Weak or reused passwords
• Malware uploads
• Unauthorized database access
• Accidental production changes
• Untracked third-party activity

Cloudflare adds another layer by placing the origin behind a managed proxy and allowing SiteCare to control how public requests reach the website.

Access to the underlying environment is provided to the SiteCare team members who need it to operate and support the platform, following defined internal controls.

Supporting SOC 2 Type II Practices

SiteCare’s operational practices are evaluated as part of our SOC 2 Type II compliance program.

The CoreSpeed architecture supports important principles associated with secure system management, including:

• Access control
• Change management
• Auditability
• Separation of responsibilities
• Risk management
• System availability
• Incident response

The Cloudflare, server, deployment, and WordPress layers are managed as parts of the same operational system.

Protecting production access and maintaining control of the delivery path helps SiteCare apply those practices consistently.

A Better Fit for Most Organizations

Some hosting platforms are designed primarily for developers who want to administer servers directly.

CoreSpeed is designed for organizations that want SiteCare to manage WordPress on their behalf.

For most clients we work with, server administration is not the business outcome they are seeking.

They want their website to be:

• Fast
• Secure
• Stable
• Properly maintained
• Easy to support
• Ready for traffic growth
• Recoverable when something goes wrong

The CoreSpeed architecture is built around those outcomes.

What to Do When You Need a Change

SiteCare manages production changes through our support and development workflows.

Contact our team when you need assistance with:

• Uploading or replacing files
• Publishing downloadable resources
• Updating website code
• Running database queries
• Completing search-and-replace operations
• Changing WordPress configuration
• Updating DNS or routing
• Troubleshooting production issues
• Deploying custom development work

We will determine the safest and most efficient way to complete the request while preserving the integrity of the production environment.

Frequently Asked Questions

Why does CoreSpeed use Cloudflare nameservers?

Cloudflare is the traffic management and edge delivery layer for CoreSpeed.

SiteCare uses it to manage DNS routing, proxy traffic, operate the CoreSpeed page-cache and preview Workers, coordinate cache revalidation, reduce origin traffic, and support rapid production cutovers.

Managing the Cloudflare zone allows SiteCare to operate these systems consistently and take responsibility for the complete website delivery path.

Can our MSP continue managing our other technology systems?

Yes.

CoreSpeed’s Cloudflare requirement relates to the website delivery architecture. An organization’s MSP can continue managing email, devices, identity, networking, Microsoft 365, Google Workspace, internal infrastructure, and other systems.

SiteCare can coordinate with the MSP during the DNS transition to identify and preserve the records required by those services.

What happens if our organization cannot delegate nameservers?

SiteCare can review the organization’s technical and governance requirements.

However, some CoreSpeed capabilities depend on having the domain proxied through a Cloudflare zone controlled by SiteCare. These include Worker-based caching, preview routing, coordinated revalidation, and complete management of the public request path.

If SiteCare cannot manage that layer, the platform may not be able to provide the complete CoreSpeed architecture or the same level of operational accountability.

Do we still own our website, domain, and data?

Yes.

Your organization retains ownership of its domain, website, content, and data.

Delegating nameservers determines which DNS platform manages the domain’s records. It does not change domain ownership.

Website and database exports can be provided when needed.

How should we manage downloadable files?

Many files can be managed through the WordPress Media Library.

For larger, frequently updated, or business-critical downloads, SiteCare can recommend and implement an appropriate storage and delivery workflow.

Can SiteCare make bulk database updates?

Yes.

Our team can perform database-level updates, including global search-and-replace operations, while following the appropriate backup, testing, and validation process.

How are custom code changes deployed?

Custom code is added to the website’s version-controlled codebase, tested, and then deployed through the CoreSpeed workflow.

This keeps the live website aligned with the documented source code and makes future maintenance more reliable.

What happens if a deployment or origin server has a problem?

Because code changes, routing, caching, and infrastructure are managed through a controlled process, our team can identify the affected layer and select the most appropriate recovery option.

A problem may be addressed by reverting a code deployment, restoring targeted data, refreshing the edge cache, changing routing, or restoring the broader environment.

This is generally faster and more precise than relying exclusively on a full website backup.

The CoreSpeed Approach

CoreSpeed is built on a simple principle: production websites should be managed as important business systems.

That means controlling the full request path, protecting direct production access, standardizing infrastructure, documenting changes, serving content efficiently from the edge, and ensuring recovery is fast and dependable.

Cloudflare is central to that model.

It allows SiteCare to manage how traffic reaches the website, reduce unnecessary origin requests, keep cached content current, provide safer previews, and make production routing changes with confidence.

Combined with CoreSpeed’s managed servers, version-controlled deployments, WordPress integration, and operational support, this architecture allows SiteCare to take greater responsibility for the performance, security, and stability of the websites we manage.

CoreSpeed is not traditional self-managed hosting.

It is a done-for-you WordPress platform built to keep your website running reliably while your team stays focused on the business it supports.