Agent-native cloud.
European infrastructure for AI builders - compute, databases, and full AI stacks, billed by the hour.
Infrastructure your agents run
Point your agent at a project. It provisions real EU infrastructure and hands you a live URL.
Full cloud stack, by the hour
Real VMs, managed databases, autoscaling clusters, and private networks. EU-hosted.
Self-healing deploys
Builds retry, wait out locks, and recover from the failures that break most deploys.
Infrastructure your agents run.
Point your agent at a project through the redu MCP. It provisions what the project needs, real VMs, a managed database, and autoscaling clusters under load, runs it in the EU, and gives you a live URL.
Your agent works inside your own account and quota, on real infrastructure, not a sandbox, and you see every step.
# 1. Add redu to your agent claude mcp add --transport http \ redu https://mcp.redu.cloud/mcp \ --client-id redu-mcp # 2. From your project folder, run: "Deploy this project to redu" # You get a plan ready. You approve it. # It deploys, and self-heals complicated workloads.
Full cloud stack. By the hour.
Our own infrastructure, not a reseller. Real machines in a European datacenter, with EU data residency. Use the console, the API, or your agent. No commitment, no minimums. £200 free credits to start. Full pricing →
A fleet that ships code while you sleep.
A coordinator assigns tasks to a fleet of agents. Each writes code and opens a PR. You wake up to merged features.
Agents have full access to your infrastructure. They can spin up VMs, volumes, and clusters if the task needs it. Not a sandbox.
Full setup guide →The AI stack your agents run on.
One VM. Every layer pre-wired. Deploy in five minutes and give your agents a full environment to work in.
Questions, answered.
How is redu different from a traditional cloud platform?
It is one. You get the same real primitives as AWS or GCP: VMs you fully control, private networks, storage, managed databases, load balancers, autoscaling. And we run the whole cloud ourselves, not a reseller on top of a US hyperscaler.
What is different is who operates it. A cloud like AWS is powerful, but you run it, clicking through consoles and wiring up endless permissions, or you pay a team who does. On redu your agent operates it: you say what you want, and it provisions and runs the real thing.
How is it different from a PaaS like Vercel, Railway, or Render?
A PaaS is a managed slot to run your app in: push code and it runs, nothing to operate. That convenience is the whole appeal, and you pay for it by giving up the machine, their runtime, their limits, their margin.
redu is the real cloud itself: the actual VMs, networks, and databases you would otherwise never touch. Normally that means operating it yourself, so your agent does that instead, and you keep the convenience while getting the control back.
It is like owning the car instead of taking the taxi, except your agent does the driving, so you still just say where to go.
Things you can do on redu that you cannot on a PaaS:
- Your infrastructure is not limited to preset tiers and a fixed network model. The machine, the network, the storage, all of it is yours to shape.
- If a custom deploy breaks, your agent can go into the infrastructure itself and fix it: the VM, the networking, the storage. A PaaS gives you at most a shell inside your app container, never the machine, network, or storage underneath.
- We recommend a path, but we do not enforce it.
- Instead of shaping everything you build to fit the platform, redu shapes itself to you, with your agent.
For example, redu does not offer managed Kubernetes today. But ask your agent and it can build one for you on redu, it has everything it needs. Try that on a PaaS and it will not work without heavy workarounds or hacks.
Why does real infrastructure matter?
It saves you from the two things that bite PaaS users: the bill and the ceiling. A PaaS charges a premium for the convenience, so past a small scale the same workload is often several times cheaper on real infrastructure.
You also get to run what a managed runtime will not: scale just the database on its own fast disk, put services on a private network, run a long job with no timeout or build cap.
There was always one catch: operating it used to need a team. Now your agent does that, so you get all of it without one.
Is it safe to let an agent run my infrastructure?
Yes. Your agent shows you a costed plan and does not provision until you approve, keys are scoped and expiring, retries are safe to repeat, and every action is logged.
Think of your agent as the driver and redu as the road built for it: guardrails everywhere, none of them slowing it down.
What happens when a deployment breaks?
It runs on a real machine, so your agent can SSH in, read the logs, fix it in place, and push the fix back to your repo.
It works best with you steering, the way you would pair with a developer. The point is it has the whole machine to work on, not a locked-down slice of someone else's runtime.
What does it cost, and do I need a card?
Pay as you go, by the hour, with no commitment, and you start with £200 in credits.
A card is required at sign-up to confirm you are a real person and keep abuse off real compute. Adding it does not charge you.