Compute

Apps and projects,on your own address

Deploy a site, a folder from a Cloud Storage Drive, or a container image. It is published at a name such as studio.broadbent.app, and you pay for the compute time it uses.

Start free

Start with 200 hours credit for free

One pod runs for about 8 days. Extra replicas and workers use the hours faster. After that, compute time comes off your credit balance.

Get started

Example

Try a pod that is already live

demo-app.broadbent.app

This is an app we published from a folder. Open it to see a Cloud Compute pod on its own address, with HTTPS.

Open the example

Start

Two ways in, one platform

An app is files. A project is a container, a worker, or a schedule. Both run in your own space. The first 200 hours are free, then both bill from the same credit balance.

  • 01

    Deploy an app

    Drop HTML, CSS and JavaScript, or a zip from one folder. A folder on a Cloud Storage Drive from Broadbent Cloud works the same way: we take a snapshot and publish it.

  • 02

    Deploy a project

    Run a container image, add a worker or a cron job, or supply your own Kubernetes YAML. Privileged and host-level options are removed before anything starts.

  • 03

    An address of your own

    Every deployment is published at a name such as studio.broadbent.app, with HTTPS. Point your own domain at it with a CNAME when you are ready.

  • 04

    Pay for compute time

    The first 200 hours are free, about 8 days for one pod. After that, add credit and pay for the hours a pod is running. An empty balance suspends the pod and keeps the files.

Compute time

Try a size before you deploy

Move the sliders. The monthly figure is a full month with every replica running. You are charged from credit for the hours it is actually up. CPU and memory are priced per replica. Storage is shared.

CPU cores

1 core

£2.50

Memory

1 GB

£1.50

Storage

10 GB

£0.60

Replicas

1 replica

This size

  • 1 CPU core
  • 1 GB memory
  • 10 GB storage
  • 1 replica

A full month running

£4.60

About 0.63p an hour while the pod is running.

Platform

What you get with every deployment

  • 01

    Cloud Storage Drive

    Deploy a folder from a Cloud Storage Drive from Broadbent Cloud. The pod gets a snapshot of those files. Later edits in the Drive stay there until you deploy again, and the pod never mounts the Drive itself.

    Learn more

  • 02

    Upload or a container

    A small site can be a file drop. A larger application should be a container image. Both get the same address, the same credit billing, and the same controls.
  • 03

    Public address

    We publish each deployment at a name on broadbent.app, for example studio.broadbent.app. Add your own hostname and point a CNAME at that address. Certificates are issued for the names you attach.
  • 04

    Firewall

    Leave the list empty and the address is open. Add IP addresses or ranges and only those can connect. A switch also allows Cloudflare’s published addresses, which is the right setting when Cloudflare sits in front.
  • 05

    Backups

    Save the deployed files and settings into a Cloud Storage Drive from Broadbent Cloud. The backup Drive is an additional cost. If the project was started from a Drive, the backup goes to a different one. This is a copy of what we deployed, not a live disk.

    See Broadbent Cloud plans and pricing

  • 06

    Your own space

    Each customer runs in a separate Kubernetes namespace, with CPU, memory and storage limits. You never receive a cluster login, and you cannot see another customer’s workloads. Workers and scheduled jobs are added from the portal.

Questions

Frequently asked questions

Is this shared hosting?
No. Shared hosting is a managed website plan. Compute is for an app or a project you deploy yourself, billed for the time it runs.
Can I deploy from a Cloud Storage Drive from Broadbent Cloud?
Yes. Choose a folder and we publish a snapshot of it. The running pod does not stay connected to the Drive, so changing files there does not change the live site until you deploy again.
Do I need to know Kubernetes?
No. Deploy an app or a container image and we run it. Kubernetes is what isolates your workloads. If you already write manifests, an advanced option accepts them after privileged, host-level and cross-namespace options are stripped.
What address do I get?
A name on broadbent.app, such as studio.broadbent.app. You can attach your own domain by adding a CNAME to that name.
How do the free hours work?
Get started claims 200 hours once per account. Checkout is £0, no card is taken, and a £0 invoice is added to the account. That is about 8 days for one pod. Each extra replica or worker uses the allowance faster. After those hours, compute time comes off your credit balance. An empty balance suspends the pod and keeps the files.
What does a backup include?
The files and settings we deployed, written into a Cloud Storage Drive from Broadbent Cloud. The backup Drive is an additional cost. See Broadbent Cloud plans and pricing. It does not copy a live container disk. A project that started from a Drive must be backed up to a different Drive.

Contact

Speak to the team

Call our Colchester sales team, or send a message anytime.

UK sales team · 8:00am–8:00pm