redu

redu.cloud is an EU-hosted, agent-native cloud.

От сообществаРаботаетНужен API-ключГлобальныйБесплатноМожет изменять данные

Что умеет

Whoami: Returns authenticated user info.
Plan Instance: Aggregates images/flavors/keypairs/networks/security groups into human-friendly choices. Does not create anything. Happy path: import_keypair → plan_instance → create_instance → get_ssh
List Instances: Lists your compute instances.

Какие данные видит

Нужен ли аккаунт

Нужен API-ключ из настроек сервиса

redu.cloud is an EU-hosted, agent-native cloud. Provision and operate real infrastructure from your AI agent — virtual machines, private networks, block storage, managed PostgreSQL & Redis, load balancers, and autoscaling clusters. Real servers you own and SSH into, not a sandbox.

What your agent can do

Compute — create, start/stop/reboot, snapshot, and delete instances; get SSH commands and console logs
Networking — private networks, security groups, floating IPs, DNS
Storage — volumes, snapshots, backups
Managed services — PostgreSQL, Redis, autoscaling clusters

plan_instance resolves image, flavor, and network IDs for you — you never pass opaque IDs.

Get started

Create an account + API key at console.redu.cloud
Paste your key in the config above
Ask your agent to build something

Hosted in the EU. Docs: docs.redu.cloud.

Список инструментов сервера (32)

Технические названия из tools/list. Нужны только разработчикам.

whoami	Returns authenticated user info.
plan_instance	Aggregates images/flavors/keypairs/networks/security groups into human-friendly choices. Does not create anything. Happy path: import_keypair → plan_instance → create_instance → get_ssh_command. Call this second (after import_keypair, if you have no keypairs).
list_instances	Lists your compute instances.
list_flavors	Lists available instance sizes.
list_images	Lists available OS images.
list_keypairs	Lists your SSH keypairs. If empty, call import_keypair first before creating instances.
list_security_groups	Lists your security groups.
list_private_networks	Lists your private networks.
list_volumes	Lists your block storage volumes.
list_snapshots	Lists your instance snapshots.
list_backups	Lists your volume backups.
list_clusters	Lists your autoscaling clusters.
list_dns_entries	Lists DNS proxy host entries.
list_domains	Lists custom domains you have verified ownership of.
list_regions	Lists available regions.
import_keypair	Registers an existing SSH public key on your account. Use this to import your own public key so you can SSH into instances. The private key never leaves your machine.
delete_keypair	Removes an SSH keypair from your account by name.
get_ssh_command	Returns the SSH command to connect to an instance via the redu.cloud TCP proxy. Example: ssh -p 22011 ubuntu@myinstance-abc12345.redu.cloud
get_instance_logs	Returns the console log output from an instance.
instance_action	Start, stop, or reboot an instance. action must be START, STOP, REBOOT_SOFT, or REBOOT_HARD.
create_instance	Creates a compute instance. Use plan_instance first to get valid image_id, flavor_id, keypair_name, network_id. For reduOS, set cloud_init_template='reduos' and flavor m1.xlarge (16GB). SSH keypair must exist.
delete_instance	Permanently deletes an instance. This cannot be undone.
create_snapshot	Creates a snapshot of a running instance.
delete_snapshot	Deletes a snapshot by ID.
create_volume	Creates a block storage volume.
get_domain_verification	Returns the DNS TXT record to add for custom domain ownership verification. Add the record to your DNS provider, then call verify_domain.
check_agent_prerequisites	Checks if your account has everything needed to run autonomous coding agents. Returns a checklist: API key validity, private network, SSH keypair, and billing. Safe to call anytime — read-only. Call this first before create_controller.
create_controller	Creates a self-configuring controller VM on redu.cloud. Auto-discovers your network, Ubuntu image, and flavor. Generates and uploads an SSH keypair if you don't have one. The VM bootstraps itself — no SSH or VPN needed. After ~7 minutes, authorize the fleet (run the authorize.sh one-liner it returns) then call trigger_agent_batch.
trigger_agent_batch	Starts the autonomous agent batch on your controller VM. Agents read agent-ready tasks from your ROADMAP.md, implement them in parallel, and open PRs. No VPN needed — runs over HTTPS; the controller stays running after you disconnect. Each ROADMAP task MUST be a single checkbox line `- [ ] Title — short description (agent-ready)` (the `- [ ]`, `bold title`, and `(agent-ready)` are all required; `##` headings and plain bullets are ignored). If this returns 'No agent-ready tasks', the tasks are mis-formatted — fix them to that exact format and retry.
get_agent_status	Returns the current status of your controller VM. On a freshly set-up VM also returns the trigger token needed to authorize the fleet and to call trigger_agent_batch. Call this after setup_agent_fleet to confirm the VM is ready.
setup_agent_session	One-shot tool that guides you through the complete agent setup: checks prerequisites, creates the controller VM, and returns next steps. Ideal for first-time setup. Call this when a user says 'set up autocoding agents for my repo'.
setup_agent_fleet	Complete one-shot setup: validates prerequisites, creates a controller VM + worker VMs, auto-creates a public HTTPS URL on port 7070, seeds a starter ROADMAP.md into the repo if absent, and returns the trigger token. Call this when a user says 'set up autocoding agents for my repo' or 'I want agents to work on my codebase'. HOW THE AGENT WORKS: each worker runs Claude Code inside the repo, implements one task, runs the test suite, and opens a pull request. It excels at focused, single-PR, testable units of work — add an endpoint, write tests for a module, fix a specific bug, add a UI page — and is poor at vague/large tasks, design decisions, or anything needing external credentials. TASK FORMAT (strict, one line each): `- [ ] Title — short description (agent-ready)` — the `- [ ]` checkbox, `bold title`, ` — ` separator, and `(agent-ready)` are ALL required; `##` headings and plain bullets are ignored. After this returns, the user needs to: (1) authorize the fleet by running the authorize.sh one-liner it returns (it runs `claude setup-token` for a long-lived token installed on the controller) — agents use the user's existing Claude Max/Pro subscription, NOT an API key. This is a shell command the USER runs in their own terminal; do NOT try to read or push the user's credentials yourself. The controller takes ~7 min to boot, so PREFER to poll get_agent_status until it reports the controller is reachable and present the authorize command only once it's ready — that way the user doesn't run it into a long wait. (The command also waits on its own, showing a live progress counter, so a user who runs it early is fine too.) (2) add well-scoped tasks in the format above to ROADMAP.md; (3) call trigger_agent_batch.