Fast websites. Serious infrastructure.

What can we host?

Pick what you're running to see the setup we'd use and the plan we'd usually start from.

How a site gets set up

Six steps, always in this order. How long each one takes depends on the site. Scroll to follow them.

# output
A written proposal with the plan and the price.

The architecture

What happens between a click and a page

Most requests follow the same path. The edge step applies to sites behind Cloudflare; the rest applies to every site.

WordPress, the platform we host most.

Most Brova Digital sites run on WordPress, so it's the setup we've tuned furthest: PHP workers and caching, set per site.

# Cloudflare cache rule (WordPress), example
# Cache HTML when:
#   http.request.method eq "GET"
#   and not http.cookie contains "wordpress_logged_in"
#   and not http.cookie contains "woocommerce_items_in_cart"
# Always bypass: /wp-admin*, /cart*, /checkout*, /my-account*
 
# Cloudflare security rules, example
#   /wp-login.php    managed challenge
#   /xmlrpc.php      block
#   /wp-admin*       rate limit

; PHP-FPM pool, one per site (example values)
pm = dynamic
pm.max_children = 12        ; from measured worker memory
pm.start_servers = 3
pm.min_spare_servers = 2
pm.max_spare_servers = 5
pm.max_requests = 500
php_admin_value[memory_limit] = 256M

-- MariaDB, one database per site (example values)
innodb_buffer_pool_size = 2G
 
# Redis object cache
maxmemory 512mb
maxmemory-policy allkeys-lru

Why Brova Cloud

• Sized after we look

  We choose the plan after reviewing the site, its traffic and its database.

• You message the engineer who set it up

  Questions go straight to the person who configured your site. No ticket queue, no re-explaining.

• Security in place before launch

  DNS, TLS, backups and, where the site uses Cloudflare, WAF and bot rules are set before it goes live.

• One team for the site and the hosting

  Brova Digital builds the site and Brova Cloud runs it, so there's no handoff between agency and host.

Plans

One monthly price for hosting and day-to-day operations, in US dollars, VAT included. We confirm the plan after reviewing the site.

Compare plans, limits and what's included →

The stack we choose for the job

WordPress, a headless CMS or a custom application. Underneath, the same work: server updates, backups and someone who knows the setup.

• 

  Cloudflare Turnstile

  Login, comment and checkout forms that attract automated traffic.

  Turnstile checks that a visitor is human without a puzzle, and without loading Google's reCAPTCHA scripts on your login page, which keeps a Google dependency out of privacy reviews.

  reCAPTCHA is a widely supported alternative. We use Turnstile because most of our sites already run behind Cloudflare, and it works on the rest too.

• 

  WordPress on managed hosting

  Editorial teams, WooCommerce stores, multilingual publishing, and organisations that already know WordPress.

  Most Brova Digital sites run on WordPress. We host them on HestiaCP with Nginx, PHP-FPM and MariaDB, with a separate system user and PHP pool for each site.

  We've spent more time tuning WordPress than any other platform we host, and the settings are made per site rather than per price tier.

• 

  Payload, when the CMS is an API

  Content that has to feed a site, an app, a kiosk and a newsletter from one model, with TypeScript in the same repository as the front end.

  A headless CMS is the right choice when the same content has to reach more than one front end. Payload keeps the content schema in code, in the same repository as a Next.js front end.

  On Brova Cloud, Payload runs as a Node.js application in a container, with its own database.

• 

  Containers, and virtual machines when needed

  Applications we can package as an image, and the few workloads that need a full machine.

  Applications run as containers on a separate server from the WordPress sites. They deploy from your repository. Every release is versioned, so we can roll back to the previous one.

  When software needs a full machine, it gets its own virtual machine on Proxmox.