Hermes builds the app, now let it launch it.
Register one skill and your Hermes flows can deploy full apps to live public URLs — one small payment per deploy, runtime included, automatic expiry. No account, no credentials stored in flow configuration.
Real Hermes flows that end with a live URL.
Each pattern below is a Hermes Agent flow with the deploy skill registered once. Each ends the same way: a working link the flow can hand to the user or pass downstream.
From user prompt to working link.
A Hermes flow takes a user's request, generates the app, and deploys it as its final skill call — returning a live URL instead of a folder of code. The flow never touches the user's hosting accounts; its worst case is the few cents the deploy cost.
Ship a preview, let it retire itself.
A flow that produces something worth showing — a report viewer, a prototype, a landing page — deploys it and shares the link. The app expires on its own when the conversation moves on; the flow has nothing to clean up and nothing keeps billing.
Create endpoints mid-flow, discard after.
Long-running Hermes flows sometimes need a piece of live infrastructure — an endpoint that receives updates from another service, a form that collects input, a status page. The flow deploys it with one paid skill call and lets it expire when the task completes.
Redeploy each version for a few cents.
An iterating flow deploys version after version — each one a separate small payment, each replacing the last shareable link. Per-deploy pricing keeps cost proportional to iterations, and Hermes budget caps bound the total across the whole run.
One skill. A live app at the end of every flow.
Upload project files — JSON or tarball — as a Hermes skill call; the deploy returns a price, pays it from the flow budget, and hands back a public URL with a clear expiry. Extend with another small payment, redeploy to replace, or let it expire and owe nothing.
- Single Hermes skill
- Pay per deploy
- Runtime included
- Flow caps honored
Hermes Agent specific questions.
If something below doesn't cover your case, ping us — we work directly with Hermes Agent builders, no SDR funnel.
How does this register as a Hermes Agent skill?
+
It's one POST endpoint — deploy files, get back a URL and expiry. Register it in Hermes as an HTTP skill with per-deploy pricing; Hermes uses the quoted price to check the flow budget before the call fires.
Does Hermes need a separate account?
+
No. The deploy request with its automatic payment is the entire relationship. Nothing to create, no credentials to store in flow configuration.
How do app lifetimes work inside a Hermes flow?
+
Every deploy includes 24 hours of runtime. The flow — or the user, via the private management link returned at deploy time — can extend for a few cents per day. Unextended apps expire and cost nothing further.
What can a Hermes flow deploy?
+
Anything packaged in the standard container format: websites, APIs, bots, dashboards, small services. Each app runs isolated with firm resource limits; larger apps cost a little more per deploy.
How does per-deploy pricing interact with Hermes budget caps?
+
Cleanly. Each deploy or extension is one fixed, upfront-quoted payment, so Hermes can enforce flow budget caps exactly — no open-ended metering to estimate, no runaway spend mid-flow.
When should a flow use Compute sandboxes instead?
+
Use Compute when the flow needs a workbench — running code, builds, multi-step state — billed per second while it works. Use Instant Hosting for the finished result: one payment, a live URL, automatic expiry.