DNS Zones
3- acme.com
- acme.dev
- acme.cloud
Zones, proxies, serverlets, volumes, crons and certificates all sit in a single project view — the same canvas you get in the console.
Reach Futrou from your terminal, your pipeline, or your coding agent. Every surface runs the same operations against the same API.
curl -fsSL https://futrou.com/install.sh | bash⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏Checking versions...⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏Installing Futrou CLI v2.0.21...Futrou CLI v2.0.21 installedRun 'futrou --help' to get startedfutrou loginPlease visit the below link in your browser and follow the instructions: https://api.futrou.com/v2/auth/cli/qbZiuz_zH1dMmfVKpeUY⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏Waiting for authentication (4:56 remaining)...curl -fsSL https://futrou.com/install.sh | bash⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏Checking versions...⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏Installing Futrou CLI v2.0.21...Futrou CLI v2.0.21 installedRun 'futrou --help' to get startedfutrou loginPlease visit the below link in your browser and follow the instructions: https://api.futrou.com/v2/auth/cli/qbZiuz_zH1dMmfVKpeUY⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏Waiting for authentication (4:56 remaining)...irm https://futrou.com/install.ps1 | iex⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏Checking versions...⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏Installing Futrou CLI v2.0.21...Futrou CLI v2.0.21 installedRun 'futrou --help' to get startedfutrou loginPlease visit the below link in your browser and follow the instructions: https://api.futrou.com/v2/auth/cli/qbZiuz_zH1dMmfVKpeUY⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏Waiting for authentication (4:56 remaining)... claude mcp add --transport http futrou https://mcp.futrou.com⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏Connecting to mcp.futrou.com...connected 4 tools · deploy, logs, scale, statusscale acme-api to 4 instances⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏services.scale · acme-api · 2 → 4done 4 instances healthy in 11sclaude mcp remove futrouremoved futrou curl -sX POST https://api.futrou.com/v1/services \ -H "Authorization: Bearer $FUTROU_TOKEN" \ -d '{"repo":"acme/api","region":"eu-central-1"}'⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏Creating service...201 Created{ "id": "svc_8fk2", "status": "running" } One control plane for deploying to the cloud and infrastructure you own.
futrou deploy Futrou handles the build, placement, certificates, and capacity so you can stay focused on the service.
Explore the docs →The things people ask us before they sign up.
Futrou is PaaS cloud platform that simplifies deploying applications. Unlike traditional shared hosting, Futrou lets you deploy any containerized application without need to build your own Docker images — PHP, Node.js, Go, Ruby, and more — with a serverless-like experience and no infrastructure hassle, flexible and always predictable billing per hour.
Yes — Futrou is one of the few PaaS platforms you can freely self-host. There are three ways to run it:
cloud.futrou.com manages the servers and infrastructure for you, so you can just focus on development and shipping. Every project deploys into its own isolated microVM for strong multi-tenant security, with a built-in WAF and anti-DDoS protection. Just sign up and immediately deploy.cloud.futrou.com allows you to bring your own servers into your workspace, combining them with Futrou's public infrastructure however you like. Deploys still go through Futrou Cloud exactly as before, with no visible difference — and if one of your servers goes down, Futrou can fail traffic over to its public infrastructure and back again once it recovers. Get the best of both worlds.No. Futrou's public regions run on Futrou's own servers, not resold AWS, GCP, or Azure capacity — and the same Futrou Nasua orchestrator runs the platform whether it's on Futrou's hardware or yours. That's what makes hybrid and fully self-hosted deployments possible: there's no cloud provider underneath to wrap.
Everything you need to run a full-stack application — backend, frontend, and everything in between — as separate services you can mix and match per project:
Node.js, Bun, Deno, PHP, Python, Ruby, Go, .NET, Lua, and Perl, along with the frameworks built on them — Next.js, Laravel, Django, Rails, and the rest. If it runs in a container, it can run on Futrou.
Every serverlet runs a Docker image — your own, published to any registry, or a Futrou base image you build on top of. There's no buildpack step and no source upload: deploy with the Futrou CLI, the REST API, or straight from the dashboard, locally or from CI.
Yes. Every serverlet gets a free *.futrou.cloud subdomain the moment it's created, with TLS included and nothing to configure. Bring your own domain whenever you're ready — Futrou requests and renews the certificate for you.
Futrou Cloud gives you access to Futrou's own public regions out of the box, or you can leave placement on Auto and let Futrou pick one for you. You can also connect your own servers as a private region and manage them through the same dashboard, billing, and team access as everything else.
Futrou Cloud uses flexible hourly billing for most of the services. You pay only for the public cloud infrastructure resources you actually use, metered hourly and deducted from your credit balance, with auto top-up options based on your usage. When credit auto top-up fails, services are stopped and after a graceful period permanently deleted. Futrou doesn't apply any additional charges and doesn't support overage payments.
All services deployed and running on custom private servers in hybrid cloud mode are completely free of charge. Self-hosted Futrou instances in private cloud standalone mode don't have or apply any billing logic. Futrou software for self-hosted instances is available for free for both personal and commercial usage. See Futrou Licenses.
No. Futrou runs on its own lightweight cloud orchestrator, Futrou Nasua, built specifically for platform needs. Futrou Nasua is inspired by Nomad and free to use for both personal and commercial purposes.
Yes. Futrou provides a remote MCP server at mcp.futrou.com, so any compatible AI client can manage your workspace, projects, and services using natural language.
Yes. The Futrou CLI manages Futrou Cloud or a standalone Futrou Nasua server with the same commands, locally or from CI. Beyond individual commands, it can manage your whole workspace as code: your project's whole state lives in a futrou.json config file — serverlets, proxies, DNS, volumes, and the rest — that you version alongside your app code and apply with futrou deploy, a bit like terraform apply for your Futrou infrastructure. Install it with a script, npm, or run it directly with npx.
Yes. The Futrou REST API is available at api.futrou.com/v2 over HTTPS and JSON, authenticated with a bearer token — everything the CLI and dashboard do goes through the same API.
Not yet as an official provider. In the meantime, the CLI and REST API make Futrou fully scriptable, and the CLI can store and version your project's infrastructure as code alongside your source.
Yes — Futrou Cloud is offered as a PaaS with a free tier for everyone, no credit card required. Hourly billing only starts once your service does, and you can self-host Futrou Nasua for free on your own hardware at any time.
Standard technical support over tickets and live chat is included with Futrou Cloud services. Self-hosted Futrou Nasua is free software backed by community support, with dedicated support available as a paid add-on.
No credit card required. Hourly billing starts when your service does.