A failed payment never takes your client's site down.
A busy month never changes your bill.
Hosting for freelancers and studios who run other people's sites. One fixed price per App slot, no usage meters, and a busy month that gets absorbed rather than invoiced.
No card required.
Switch the month. Your bill does not move.
$ npx wawesome init --template contact-form $ npx wawesome deploy https://quiet-otter-42-site.wawesome.io
No surprise invoices.
No usage meters, no fees for going over.
Seats come with the plan.
One price a month. Every plan includes seats for your team, so a growing team moves you up the ladder.
On any paid plan, a busy month never switches a site off.
Going past the monthly allowance is absorbed, not invoiced.
The slot
One hostname. As many Functions as you want.
A slot is one hostname holding as many Functions as you want. You pay for client projects, not for people and not for gigabytes.
The serving guarantee
Two things that can go wrong, and what happens instead.
Busy month
- Your client's site, serving
- Your bill, unchanged
- Your Schedules, running
A busy month is absorbed, not invoiced, and never stops serving a paying workspace.
Failed payment
- Deploys
- New Apps
- Your client's site, serving
- Everything already deployed
A failed payment stops your deploys and never stops your client's site.
The sandbox
Code an agent wrote can only reach the hosts you opened.
Outbound is closed by default
Outbound calls are denied until the App opens a host. A Function reaches api.stripe.com because you said so, and nothing else.
Secrets can't be read back.
Not through the CLI, the dashboard or the API, not even by you. Only your running code sees the value. So a credential that can deploy can reach it through the code it ships. Only give deploy rights to an agent you'd trust with the key.
Agents get only what you grant.
Agents deploy over POST /v1/mcp with scoped capabilities. What the credential does not carry, the agent cannot do.
Unified deploys
One Version. Pages, files and handler, together.
One Version carries your pages, your static files and your handler. A rollback returns all three at once.
Each Function versions on its own, so shipping one route never puts the rest of the App at risk.
Four plans
One price a month. Pick a size.
Free
€0/ month
1 App slot
For one thing you want on the internet.
Solo
€9/ month
3 App slots
For a freelancer running a handful of client sites.
Studio
€29/ month
10 App slots
For a small studio shipping for several clients at once.
Agency
€149/ month
30 App slots
For an agency hosting a book of client work.
Templates
Start from a template that already runs.
Unified deploys
Contact Form
The contact page and the route its form posts to go out in one deploy. They share one address, so there's no CORS to set up, and one rollback undoes both.
Egress catalogue
Stripe Webhook Receiver
An endpoint for Stripe's events. It checks Stripe's signature on every request, so your code only sees the events Stripe really sent.
Schedules
Scheduled Job
A job that runs every five minutes. The timer is one line in a config file, and the job has no public address, so no one on the internet can start it.
This is not for everyone.
- The runtime is lightweight, memory-efficient and built on web standards.
fetch,Request,Responseand Web Crypto are there. Node built-ins likefsandchild_processare not, and packages that need them will not deploy. - There is no database here. Your Functions reach one over HTTP.
- The free plan slows down past its allowance, and well past it pauses until the next month begins. Paid plans absorb a busy month instead.
- Plans are sized for client sites, webhooks and small APIs, not for tens of millions of requests a month.
Put your first client site up.
A free workspace holds 1 App slot and needs no card.