Let’s talk The care behind a dependable website
Your hosting should support the website, not become another job for your team. We use Cloudflare and Vercel to host suitable custom websites, and provide the setup, deployment care and ongoing support around them. One clear place to start when something needs attention.
Two platforms. A considered choice.
Both provide ways to deliver websites through distributed infrastructure. We choose around your framework, content workflow, integrations and operating requirements. You do not automatically need both in the delivery path.
A useful fit for supported frameworks and headless websites that benefit from preview deployments and a managed release workflow. Vercel includes a CDN for content delivery. We configure the project, domains and environment settings, then check forms, CMS publishing and the release process.
Cloudflare Workers can serve static website assets and supported server-side functionality on its network. We assess runtime compatibility, caching and connected services before moving a site. Cloudflare can also manage DNS without being used as an additional proxy in front of another hosting platform.
A standard Webflow or Framer website normally stays with its platform’s hosting. We can help manage domains and the surrounding setup. Moving an exported site elsewhere does not automatically preserve its CMS, forms or other hosted features, so we explain those trade-offs before recommending a move.
What managed means in practice
Cloudflare or Vercel provides the hosting platform. Hilvy manages the agreed website setup and care around it. We write down that division so platform features are not mistaken for an unlimited support promise.
Set up source control, deployment permissions, preview access and release checks appropriate to the site. We document how to return to a previous deployment and what that does not restore. CMS content, uploaded files and databases need their own backup and recovery arrangements.
Review caching, images, scripts and key user journeys rather than relying on a hosting logo to guarantee speed. Monitoring, alert recipients and review frequency are agreed in the service scope. The useful measure is how the real website behaves for its visitors.
Document who owns the domain, code, provider accounts and billing. We agree support hours, escalation routes and the work included in the retainer. Platform subscriptions, traffic or compute usage, and third-party services are explained separately from Hilvy’s management fee.
Our own working setup
Hilvy’s own site combines Astro pages, Sanity content and selected React interactions, deployed on Vercel. That is a concrete example of our working setup. It is not a universal speed benchmark or a claim that every client uses the same stack.
From a client’s perspective
On website quality and maintainability, from an existing development client.
More client reviewsCollaborating with Hilvy has been a delight! They created a flawless website that not only looks and functions superbly but is also well-organized and easy to maintain.
Isabelle KrauzeUX Lead @ LLinformaticsThe details worth asking about
We agree the hosting configuration, deployment process, monitoring, recovery planning and support responsibilities in your proposal. Content updates, new features and wider maintenance can be included separately. Managed hosting is not automatically an unlimited design or development retainer.
We first check the framework, server requirements, CMS, forms, redirects and connected services. If the site is compatible, we plan the move, test it on a preview and check the live domain after switching. Some platform-hosted websites are better left on their native hosting.
No provider can guarantee that every page will be fast. Hosting is one part of performance alongside images, JavaScript, third-party embeds, backend responses and a visitor’s connection. We measure the existing site and identify the changes likely to make a useful difference.
No. Vercel already provides a CDN, and an additional proxy can complicate caching and security. We choose an intentional setup. Using Cloudflare for DNS does not require proxying the website through Cloudflare as well.
Those responsibilities must be agreed explicitly. A previous deployment is not a backup of the CMS or database, and platform protection does not remove application-security work. Support hours, backup frequency, recovery targets and any out-of-hours coverage belong in the service agreement.
The total depends on the website, provider plan, usage and support scope. We separate hosting and other third-party charges from setup and ongoing management. We also agree account ownership and how access or management would transfer if you chose another provider.
Share your current website and what is causing friction. We can review the hosting, identify the practical options and scope the ongoing care.
