One price per cloudlet. Unlimited users.
We run your Magic Cloudlet — hosting, hardening and updates straight from the people who wrote the runtime. You pay for the cloudlet, and nothing else. Not per seat, not per request, not per user of whatever you build on it. Add your whole team, ship to a hundred thousand customers, and the invoice is the same number it was last month.
A backend of your own, ops off your plate
- A cloudlet of your own — its own address, database, files and users, running on our infrastructure and watched by our people.
- Unlimited users — developers, colleagues, and every end user of every app you build. We never count them.
- Hardened and current — security updates land before you hear about the CVE, and RBAC is on from the first minute.
- Answers from the source — the people answering in the community channels are the ones who wrote Hyperlambda, not a tier-one script. Enterprise adds email support and a monthly call.
- Need another? Buy a second cloudlet. Development, staging and production are three; an agency often runs one per client.
- What people build on it — agents over an existing database, an MCP server for Claude, a legacy system wrapped instead of rewritten, and tools generated from a sentence.
Same software. Pick the machine.
The one most teams run
Enough machine for real production work, and the size every cloudlet starts at.
- Unlimited users, no seat counting
- Hosting, hardening and updates handled
- Community support on Discord and GitHub
- 14 day free trial, card required
- Month to month, cancel anytime
Twice the machine, same everything else
For heavier workloads, larger models and datasets that outgrow the Professional box.
- Everything in Professional
- Double the CPU, memory and storage
- Built for teams of developers working in parallel
- Email support, answered by the runtime's authors
- One 30 minute call with us each month
- 14 day free trial, card required
- Month to month, cancel anytime
Ten hours a month of the people who wrote it
A Hyperlambda master developer embedded with your team — building endpoints, wiring integrations, keeping things tight. Pairs with a cloudlet.
- 10 hrs/mo of a master developer
- Your backlog, built by the people who wrote the platform
- No middlemen between you and the source
Fixed costs are a feature.
The runtime is MIT-licensed — the software itself is free forever. Your $100 pays for the boring, essential things: hosting, hardening, patches, and a direct line to the team that built it.
And because we bill the cloudlet rather than the people using it, growth is pure upside. Hire five developers, launch to ten thousand customers, run your busiest month ever — the invoice does not move. Most platforms charge you more the better you're doing. We think success shouldn't come with a surcharge.
Best of all, there's no trapdoor under any of it. It's month to month — cancel whenever you like — and since the runtime is open source, you can take your cloudlet's files and database to your own hardware and keep every app you built running without us. Stay because it's worth it, not because leaving hurts.
Custom engagements
Data that can't leave the building? We'll install and configure Magic Cloud inside your firewall as a fixed-scope job. And when a subscription isn't the right shape, the same engineers take on one-off builds: scoped, priced, shipped. Price quoted before work starts.
Straight answers, up front.
Is there a free trial?
Yes — 14 days, on either plan. A card is required to start it, but nothing is charged until the trial ends, and cancelling before then costs you nothing. The cloudlet you get is the real thing with everything switched on, not a limited demo. Self-hosting stays free forever regardless, since Magic Cloud is MIT-licensed.
Are the users of the apps I build billable?
No. Never. You can sign up a hundred thousand people to an application running on your cloudlet and the price does not move. The cloudlet is the unit we bill for, and it is the only unit we bill for.
What counts as a cloudlet?
One running backend at its own address, with its own database, files and users. Most teams run more than one — development, staging and production are three cloudlets, and an agency running client work often keeps one per client.
What are AINIRO, Hyperlambda and Magic Cloud?
Three names for three different things. Hyperlambda is the programming language — the executable-AST runtime everything else is built on. Magic Cloud is the platform built with it: the backend, dashboard, IDE, CRUD generator, authentication and AI tooling, all MIT-licensed and published on GitHub. AINIRO is the company that builds both, and that runs the servers your cloudlet lives on — which is why a cloudlet's address ends in .us.ainiro.io. Buying a cloudlet means AINIRO runs Magic Cloud for you; downloading it from GitHub means you run it yourself, free, forever.
How is this different from what AINIRO sells at ainiro.io?
Different product, same technology underneath. AINIRO sells a managed service — AI chatbots and agents where AINIRO does the work for you: crawling and indexing your content, building and tuning the agents, wiring them into Shopify, Slack, HubSpot or whatever else you run, and supporting the result afterwards. The AINIRO plans that include setup and support run several times the price of a cloudlet here, because there you are paying for people rather than hardware. Here you buy the machine, not the service. A cloudlet is Magic Cloud running on hardware AINIRO keeps alive and patched for you, and everything on top of it is built by you and your AI coding agent. One flat price per cloudlet, unlimited users, nothing managed on your behalf. Buy here if you are a developer who wants the platform; go to ainiro.io if you want AINIRO to build and run it for you.
How many projects can I create?
As many as you like. Nothing counts your modules, apps, APIs, databases or endpoints, and nothing bills for them. A single cloudlet can host one application or twenty. The only ceiling is the machine itself — the CPU, memory and storage of the plan you picked — never a number we enforce.
What's the difference between Professional and Enterprise?
Two things: the machine, and how you reach us. Professional gives you 500m CPU, 1GB of memory and 2GB of storage; Enterprise doubles all three. Professional is supported by the community — Discord and GitHub, where the people answering are the ones who wrote the runtime. Enterprise adds email support, and one 30 minute call a month for the problems that are easier solved together than described. The software and the terms are identical, and moving up is a conversation rather than a migration.
Can it run on our own infrastructure?
Yes — and you don't even need us for that. The runtime is MIT-licensed, so self-hosting is free forever. If you'd rather we handle the install and configuration inside your firewall, we quote that as a fixed-scope job.
What if we need help without Managed Services?
Then we work by the job. Describe the problem, we scope it, put a fixed price on it, and deliver. Same engineers, no subscription required. Start with an email.
What if we want to leave?
Then you leave — it's month to month, cancel whenever you like. And because the runtime is MIT-licensed open source, quitting us never means quitting your app: run the same stack on your own hardware, move your files and database over, and everything you built keeps running without us. We'd rather earn next month than lock you into it.
How do I cancel, or change my card?
Through Stripe's customer portal — enter the email address you paid with and Stripe sends you a sign-in link. From there you can cancel, change your payment method and download every invoice. We never see your card details. Cancelling ends the subscription, and the cloudlet is removed once the period you have paid for is over, so export anything you want to keep before then.
Bring your use case. Leave with a price.
Thirty minutes with a working engineer. We'll size the cloudlet you actually need on the call, pressure-test the fit against what you're building, and tell you honestly if a cloudlet isn't it.