Host · Solutions
The Solution is the product.
A Solution is everything one product needs: the app, its database, the functions behind it, its files, domains, email and AI. Group them once, and they’re built, released and secured together.
What a Solution is
Our value is the Solution, not the server.
Anyone can rent you compute. What’s hard is everything around it: which database goes with which app, what ships first, who can release it, and who pays. A Solution answers all of it in one place.
One place
Every app, database, Ambassador, bucket and domain belongs to exactly one Solution. Nothing is orphaned, and nothing sits in two Solutions with two release schedules.
One release
Plan, migrate, deploy. The database changes before the app that reads it, in an order worked out for you, and every step is verified.
One bill (coming soon)
Per-Solution billing is on its way, so a client’s portal will be the client’s cost, not buried in yours.
Your people, your roles
Decide who can see a Solution, who can release it and who manages access, including a contractor who has no seat.
One region
A Solution lives where you choose: Sydney, Singapore, Frankfurt, London or Virginia. Its data stays there.
How releases work
Plan. Migrate. Deploy. Verified.
Most platforms deploy an app. They can’t put a database migration in front of that deploy, because they don’t own the database. We own the whole set, so we can, and we can refuse a release that would break.
- 1
Plan
See exactly what the release would do before anything runs. If any step would refuse, the whole release refuses: nothing partial, nothing to undo.
- 2
Migrate
Schema changes apply first, so no app ever boots against a database it doesn’t understand.
- 3
Deploy
Sign-in, functions, the app and its domains ship in dependency order. Each step records what it actually returned, not a status we wrote ourselves.
Releases only go forward. If one stops half way, resume it and every step that already applied is carried across, not run twice. Or abandon it on purpose, with a reason on the record.
Members and roles
The right people can ship it. Nobody else can.
Access is per Solution. A contracted developer can be made a guest releaser on your Solution: they ship your work without a seat, and lose access the moment you remove them.
| Role | Can |
|---|---|
| Viewer | See the Solution and its release history. |
| Releaser | Also plan and release it. |
| Owner | Also manage who else has access. |
Coming soon
Each Solution pays its own way.
Per-Solution billing is coming: each Solution will get its own bill for the compute and storage it actually uses. Today, Host comes with your licence, hosting, builds, SSL and bandwidth are included, and metered usage draws on your plan’s credits.
See Host pricingQuestions
What is a Solution on Waymaker Host?
A Solution is everything one product needs, grouped: the app, its database, the functions and agents behind it, its storage, domains, email and AI. It is built, released and secured as one unit, in one region.
Why release a Solution instead of deploying an app?
Because an app is rarely alone. A Solution release runs database migrations before the app that needs them and deploys everything in dependency order, so an app never boots against a schema it doesn’t know.
What happens if a release stops half way?
The record says which steps went live and which never ran. You either resume, which works the plan out again and never re-runs a step that already applied, or abandon it deliberately. Releases only go forward.
Can a contractor release my Solution without a Waymaker seat?
Yes. A guest can be granted the releaser role on one Solution. It is never automatic, and removing their guest access stops them releasing immediately.
How is a Solution billed?
Today, Host comes with your Waymaker licence and its metered usage draws on your plan’s credits. Per-Solution billing, where each Solution gets its own bill, is coming soon. The details are on the pricing page.