A managed Magic Cloudlet is hosted, secured, and kept current by the people who wrote the runtime — with one developer user included. Add people as your team grows. No meters, no credits, billed monthly.
The math is simple enough to do on a napkin — which is exactly the point. Drag the sliders; the total updates live.
| Line | Qty | Unit | / month |
|---|---|---|---|
| Managed Cloudlet — incl. 1 developer user | 1 | $100 | $100 |
| Additional developer users | 0 | $200 | $0 |
| Additional users | 0 | $100 | $0 |
| Managed Services — 10 dev hrs | — | $3,000 | — |
| Total | $100 |
A Magic Cloudlet on Nuity infrastructure — you build on it, we run it.
A dedicated Magic/Hyperlambda master developer from Nuity — ten hours a month building, integrating, and maintaining alongside your people. Requires a managed cloudlet.
Two things live here. Need Magic Cloud installed and configured on your own local infrastructure? That's a custom job — scoped and quoted per engagement. And when Managed Services isn't the right shape — no managed cloudlet, or a single well-defined problem — the same engineers work on a consulting basis instead: scoped, quoted, delivered.
The $100 isn't a license fee — the runtime underneath is MIT and always will be. What you're paying for is everything around it: hosting, security hardening, updates, and the technical knowhow of the people who wrote it, on call when you need them.
And the meter never touches your success: accounts on the cloudlet are the only thing priced. The apps, APIs, and AI agents you ship from it serve unlimited end users — your customers are never a line item on our invoice.
An account on your cloudlet. A user ($100/mo) works within whatever roles you assign — the runtime's RBAC enforces the boundary. A developer user ($200/mo) holds full administrative and build rights. End users of the apps and APIs you ship are never counted, never billed.
A developer user can do everything the cloudlet can do — which is exactly why you should have few of them. Pricing full privilege at a premium keeps it where it belongs and nudges every team toward least privilege. On a platform whose whole thesis is the security boundary, that's not a pricing quirk; it's policy.
Yes. If your data has to stay behind your firewall, we install and configure Magic Cloud on your local infrastructure as a custom job — scoped to your environment and quoted per engagement. You get the same runtime and the same validation boundary, on hardware your compliance team already trusts.
Managed Services is a standing arrangement on a managed cloudlet. When that's not your shape — you host elsewhere, or the need is a single well-defined build — the same engineers are available on a consulting basis: you describe the problem, we scope it, quote it, and deliver it. Start with an email.
Bring your team size and your use case. We'll price it live, walk the validation boundary against your reality, and tell you plainly whether a cloudlet fits.