Why use ArduMaker cloud
Published on 2026-09-12 by frfrand
No competimos en cantidad de servicios ni en precio por gigabyte. Lo que resolvemos es otra cosa: que un equipo chico pueda operar infraestructura de varios clientes sin que se le vuelva un trabajo aparte.
There are providers with more services than us, and there are cheaper providers per gigabyte. It's worth saying this first, because we don't compete there.
What we solve is something else, and it's better understood by describing the problem.
The concrete problem
A developer or a small agency serving several clients ends up with scattered infrastructure: a server with one provider, domains with another, email with a third, certificates renewing manually or simply forgotten, and shared accesses in a password manager.
None of that is wrong individually. The problem is the whole: managing infrastructure becomes a separate job, one that no one bills and that always interrupts something else.
And there comes a time when it becomes truly painful: when a client leaves, or when someone new joins the team, and you have to separate what belongs to whom.
What we do differently
One Company per client. Each client lives in their own space, with their own VPS, their own domains, their own billing, and their own team. No shared servers or cross permissions. When a client leaves, everything goes together and without archaeology.
The full path in one place. Creating the VPS, linking the repository, pointing the domain, issuing the certificate, and deploying are steps in the same panel. You don't have to coordinate three providers to put a site online.
Insurance without anyone remembering. Closed ports by default, SSH that opens with an expiration date and closes by itself, automatic SSL, backups on another host verified with hash, and every command logged with who executed it.
Access per person. Each one with their own account and their own SSH key. Removing someone is one action, not a coordination with the whole team.
Separate billing per client. Each Company has its balance and its expenses, so costs can be transferred without doing manual calculations.
What we are not
Being clear about this avoids disappointments:
- We are not a hyperscaler. If you need two hundred managed services, presence in twenty regions and specific certifications, there are providers made for that.
- We are not the cheapest by raw resource. You can rent a bare server for less. What you pay extra for is that it comes with the panel, the isolation, and the things that happen on their own.
- We do not replace your team. The application is still yours, with its errors and its decisions.
For whom it makes sense
It fits well if you are a developer or agency with several clients, if you want the infrastructure not to be a separate job, if you care about being able to grant and revoke access quickly, and if you value that obvious things (certificates, backups, ports) happen without depending on anyone's memory.
It fits worse if your workload requires very specific services from a large provider, or if you have a dedicated infrastructure team that prefers to build everything from scratch.
One more thing
There is a dedicated MCP server, so you can operate all the infrastructure by talking to an AI agent: create a VPS, check logs, configure a service, publish a domain. It's a different way of working and quite comfortable when you already know what you want and don't want to navigate a panel to achieve it.