For agencies and freelancers running client sites
Shipping a client site is the easy part. Being on call for it for the next three years is not. ServerlessHub operates the agreed AWS-based hosting, deployment setup, custom domain, HTTPS, CDN delivery, and ongoing platform support for the sites in your portfolio—without touching your code, your client relationship, or your invoices.
Choose Managed Hosting for a stable site, or Platform Care when a site needs a more active release and support relationship. Portfolio pricing starts at three sites.
Best suited to marketing sites, documentation sites, landing pages, and other lightweight client work.
// platform-fit.md
✓ Architecture agreed before launch
✓ Ownership and access documented
✓ Support scope defined in writing
✓ No black-box platform claims
Why this exists
You can ship a solid client site in a weekend, then spend the next three years on domains, certificates, deploy settings, cache rules, access requests, and the message that arrives at 9pm because something changed.
ServerlessHub is for agencies and freelancers who want a platform partner behind their client work — without handing the client to an opaque website builder, and without taking on permanent server administration themselves.
We do not promise a magic black box. Before a project starts, we agree on the architecture, ownership, support scope, and the limits of the service.
What we handle
We set up and operate the agreed AWS-based hosting environment. This may include static hosting, global content delivery, custom domain configuration, and managed HTTPS.
We document who owns the domain, repository, hosting account, and operational access before launch — including what happens if a client leaves you, or you leave us. Handover should be written down, not improvised.
We coordinate the production launch, verify agreed pages and forms, and provide the support included in the selected plan.
After launch, hosting-scope issues have a named place to go instead of your phone. New features, content changes, application development, and third-party costs stay separate unless explicitly included.
Good fits
Projects to review carefully
If your project is outside the current service scope, we will say so early. A bad fit is more expensive after launch.
The working model
You or your agency remain responsible for the code, product behaviour, the client relationship, client-facing content, and third-party accounts unless we agree otherwise. ServerlessHub operates the agreed hosting platform, deployment process, delivery layer, and platform support scope.
The exact split is confirmed in writing before work begins.
You or your agency
ServerlessHub
You Build and maintain the site or application code
ServerlessHub Set up and operate the agreed hosting platform
You Own the client relationship and approve changes on their behalf
ServerlessHub Configure the agreed domain, HTTPS, and delivery layer
You Maintain third-party accounts and application-level integrations unless otherwise scoped
ServerlessHub Coordinate deployment and verify the launch checklist
You Provide client-facing content and support unless otherwise scoped
ServerlessHub Provide platform support within the selected plan
How it works
Send the URLs, frameworks, expected traffic, integrations, how many sites you are looking to place, and what you need help with.
We confirm platform fit, what we can manage, likely implementation approach, and items needing separate work.
Once scope is approved, we prepare the environment, coordinate deployment, test important paths, and make the release.
After launch, hosting-scope issues for every site in the arrangement go to one place. Feature work and new requirements are scoped separately.
Plans
We confirm ownership, deployment access, traffic expectations, and service limits before launch — per site, and across the portfolio.
Managed Hosting is for a stable client site that needs a reliable production home. Platform Care is for sites that need ongoing release coordination, agreed integration support, and a more defined operational relationship.
Pricing moves on volume, not on who you are. From three sites, the per-site rate is set from the portfolio and the support model it needs.
For one eligible client site — static, documentation, marketing, or landing page — that is stable after launch.
from $18/month
For an eligible client site with an active release schedule, agreed integrations, or a need for closer platform coordination.
from $49/month
For agencies and freelancers placing several client sites under one operating model.
From 3 sites
AWS usage, paid third-party services, additional development, and work outside the agreed support scope are separate charges. We identify these before they become a surprise.
Ownership and exit
We document the ownership model before launch. At a minimum, that means clarity on:
For a reseller-managed or agency-managed AWS account, the handover process is explained plainly before launch — including what happens to a site if a client leaves you.
Agency FAQ
Astro is a natural first supported framework because this site is built with it. Other frameworks are agreed only where we have a repeatable deployment and support process.
Repository and deployment arrangements are agreed during project setup, including the provider, access model, and release process.
The answer depends on the operating model. Client-owned, agency-owned, ServerlessHub-managed, and hybrid account arrangements have different support, billing, and handover implications, so this is decided before launch.
We only commit to workflows that are already available and supported for the project.
Possibly, but it needs a discovery call. ServerlessHub is aimed first at lightweight web projects; databases, authentication, real-time features, complex integrations, and compliance needs may require a custom engagement or a different platform.
Managed Hosting is designed for a stable eligible site after launch. Choose Platform Care if the site needs ongoing release coordination, priority help with the agreed platform setup, or support for agreed integrations. It is not a development retainer; new features and work outside the agreed scope are estimated separately.
The recurring plan covers the platform service in your agreement. New product features, substantial content work, and new integrations are estimated and approved separately.
The site’s source lives in a repository you or your client controls, and that repository is the backup — we can rebuild and redeploy the site from it. We do not run separate automated snapshots of the hosting environment; the platform is defined by the code and configuration, which are version-controlled. On Platform Care we hold deploy access and can redeploy or roll back a release quickly if one goes wrong.
Yes, subject to the agreed account and handover model. We document the assets and access needed for a reasonable handover before launch — including what moves if a client leaves you.
Pricing moves on volume, not on identity. A single site is priced the same whoever is placing it, because the support workload is the same. From three sites, we set a per-site rate from the portfolio and the support model it needs, and confirm it in writing before anything is committed.
White-label arrangements are available and agreed before launch. We confirm in writing who the client contacts, what we handle directly, what routes through you, and how the support boundary is described to the client.
Discuss a portfolio
Tell us what you are running, the frameworks involved, how many sites, and where you want help. We will tell you whether ServerlessHub is a fit and what the platform work would involve.
Submitting this form starts a fit review. It does not create a hosting commitment or guarantee a particular architecture. See our Privacy Notice.
