ServerlessHub Developers

For developers and technical teams

You build the site.We run the platform work.

Bring us an eligible website or lightweight web project. ServerlessHub can provide the AWS-based hosting, deployment setup, HTTPS, CDN delivery, and ongoing platform support agreed for the project.

You keep control of the code and product decisions. We make the infrastructure side less of a distraction.

Best suited to marketing sites, documentation sites, landing pages, and other lightweight web projects.

// platform-fit.md

Architecture agreed before launch

Ownership and access documented

Support scope defined in writing

No black-box platform claims

Why this exists

Hosting should not become another unpaid job.

You can ship a solid site in a weekend, then lose days to domains, certificates, deploy settings, cache rules, client access, and the message that arrives after something changes.

ServerlessHub is for developers who want a reliable platform partner without handing their client to an opaque website builder or 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

A focused platform layer for eligible projects.

Deployment and hosting

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.

Practical handover

We document who owns the domain, repository, hosting account, and operational access before launch. Future handover should be clear rather than improvised.

Launch support

We coordinate the production launch, verify agreed pages and forms, and provide the support included in the selected plan.

Ongoing platform care

After launch, we handle agreed hosting and configuration tasks. New features, content changes, application development, and third-party costs stay separate unless explicitly included.

Good fits

  • Static websites and documentation sites
  • Astro and other lightweight frontend builds
  • Marketing sites and campaign landing pages
  • Client sites that need custom domains, HTTPS, and CDN delivery
  • Forms and lightweight integrations reviewed during discovery
  • Agency handovers and white-label arrangements with a clear support boundary

Projects to review carefully

  • WordPress sites with plugin-dependent dynamic features
  • Sites with authenticated user areas
  • Ecommerce, membership, or booking systems
  • Projects that depend on a database, background jobs, or real-time updates
  • Regulated or high-compliance workloads
  • Applications where uptime, incident response, or usage needs exceed the stated plan

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

Clear responsibilities from the start.

You Build and maintain the application or site code

ServerlessHub Set up and operate the agreed hosting platform

You Decide product behaviour and approve changes

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

The exact split is confirmed in writing before work begins.

How it works

From repository to production, without the mystery.

  1. 01

    Share the project

    Send the URL, repository details if appropriate, framework, expected traffic, integrations, and what you need help with.

  2. 02

    Get a fit and scope review

    We confirm platform fit, what we can manage, likely implementation approach, and items needing separate work.

  3. 03

    Set up and launch

    Once scope is approved, we prepare the environment, coordinate deployment, test important paths, and make the release.

  4. 04

    Keep the platform cared for

    After launch, you have a named place for hosting-scope issues. Feature work and new requirements are scoped separately.

Plans

Choose the level of support your project needs.

The starting point is scope, not price. Ownership, deployment access, response time, and limits are agreed before work begins.

Starter platform support

For one small, eligible static or marketing site after onboarding.

from $29/month

  • Hosting on the managed AWS-based stack
  • Custom domain and HTTPS setup
  • CDN delivery for cached content
  • Standard platform support
  • Documented traffic or usage allowance
  • One-time setup or migration quoted separately when required
Check project fit

Growth platform support

For an eligible site with agreed forms, integrations, or a more active release schedule.

from $79/month

  • Everything in Starter
  • Support for agreed integrations
  • Priority platform support
  • Any backup or recovery arrangement defined in scope
  • Documented traffic or usage allowance
  • Setup, migration, and application work quoted separately
Discuss Growth support

Agency / custom

For agencies that need a repeatable platform partner, several client sites, or a specific handover model.

Let's talk

  • White-label and multi-site arrangements
  • Project-specific platform design
  • Support commitments agreed for the account
  • Defined onboarding, ownership, and handover process
Talk about an agency setup

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

Your work should remain portable.

We document the ownership model before launch. At a minimum, that means clarity on:

  • The source repository and code ownership
  • Domain registration and DNS access
  • The AWS account or account-access arrangement
  • Credentials and third-party integrations
  • What is included if you need to move the site later

For a reseller-managed AWS account, the handover process is explained plainly before launch.

Developer FAQ

Questions, answered plainly.

Which frameworks do you support? +

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.

Can I use my own Git repository? +

Repository and deployment arrangements are agreed during project setup, including the provider, access model, and release process.

Will I get AWS account access? +

The answer depends on the operating model. Client-owned, ServerlessHub-managed, or hybrid account arrangements have different support, billing, and handover implications, so this is decided before launch.

Do you support preview environments and CI/CD? +

We only commit to workflows that are already available and supported for the project.

Can you host my full web application? +

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.

What happens when I need a new feature? +

The recurring plan covers the platform service in your agreement. New product features, substantial content work, and new integrations are estimated and approved separately.

Can I move away later? +

Yes, subject to the agreed account and handover model. We document the assets and access needed for a reasonable handover before launch.

Discuss a project

Have a site ready to ship?

Tell us what you are building, the framework you are using, 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.