Powerups
Why pay for the things a static site needs?
A static site is fast, cheap and almost enough. Almost. It still has to be built, it should deploy itself when you push, and somebody has to be able to contact you. Solve those three separately and you are paying four bills to run one website. They are built in here instead.
Instead of a CI service
Builds
We run your build command in a throwaway container and publish what it produces. Any framework that outputs a folder.
How builds workInstead of a deploy pipeline
GitHub
Connect once, choose a repository, and every push to your branch goes live. Private repositories included.
How deploys workInstead of a form service
Forms
An endpoint your form posts to. Enquiries arrive by email and in your dashboard, with spam filtering built in.
How forms workThe arithmetic
What this normally costs.
Not a competitor comparison — those services are good at what they do. It is just what a small site ends up paying once it needs more than files.
Paid tiers buy bandwidth and storage. Powerups are not the upsell — they are the reason a static site is enough.
Still static
None of this makes your site dynamic.
Your pages are still files on disk, served without running anything. A build happens before the deploy, not during a request. A form posts to an endpoint we own, not to code of ours running inside your site.
That matters because it is why the site stays fast, why there is nothing to patch, and why a rollback is a pointer move rather than a redeploy.
Get started
Every powerup, on the free tier.
Nothing here is held back for paid plans. Create an account and turn them on.