Compute
Deploya project
Address
A name you choose
The first part of the address is yours. HTTPS is included, and you can point your own domain at it with a CNAME.
Service
Your app
A public image listening for HTTP, with a certificate on this name.
Try a pod that is already live
demo-app.broadbent.app
Open a live pod first. This one is an app made of files. A project uses the same kind of address for a container, a worker, or a schedule.
Projects
A container, with room to grow
Each project runs in your own namespace. The first 200 hours are free. Extra replicas and workers use those hours faster, then compute time comes off your credit balance.
01
A container image
Paste a public image, such as nginx:1.27. We run it, give it an address, and issue a certificate for that name.
02
A worker
Add a background process beside the main container. It uses the same CPU and memory, and counts as another pod for billing.
03
A schedule
Add a cron job with a command and a timetable. It runs in the same space as the project.
04
Your own YAML
Supply a Deployment, Service, Job or CronJob. Privileged, host-level and cross-namespace options are removed before anything starts.
Examples
Projects people run
01
A web service
A public image that listens for HTTP, published at studio.broadbent.app. Start with one pod, then add replicas from the portal if you need them.02
An API and a worker
The API serves requests. A worker beside it handles a queue. Both run in the same namespace and bill for the hours they are up.03
A nightly job
A cron that runs a command on a schedule, for example a report or a cleanup, without keeping a second website online.04
A manifest you already have
Paste the YAML you use elsewhere. Ingress, privileged containers and anything outside your namespace are stripped. The address is still one we publish for you.
Get started now with 200 free hours
One claim per account. Checkout is £0, about 8 days for one pod, then you deploy in the portal.