Fransys

Guide · Claude Code

Deploy with Claude Code, in Europe

Updated on

Claude Code can write a Dockerfile, a deployment configuration and the scripts that go with them. What it does not provide is the place where the application runs, or the person who responds when it goes down. So the question is where it runs, and who runs production afterwards.

No credit card, no commitment.

your-app · claude

example

Welcome to Claude Code!

cwd: ~/your-app

  1. Get our app up and running on Fransys, with a European provider. Prepare the plan, I approve.
  2. I'm reading the repository: an API, a Postgres database, a Redis cache. I'm preparing the plan with Fransys.
  3. fransys - prepare_plan (MCP)(project: "your-app")3 blocks to create, with the provider and in the country you choose.
  4. fransys - estimate_project (MCP)(plan: "production") + Worker machines€89.98+ Control plane nodes€31.49+ Load balancer€27.49+ Volumes€3.30+ Backups€1.26+ Image registry€0.05+ Logs€1.20+ Metrics€9.60 Total, public prices as of October 27, 2026€164.37 a month Of which Hetzner, at its public rate, with no margin€55.16
  5. Plan ready in Fransys › Plans 3 blocks, €164.37 a month, machines included

    Approve and execute

    Reject

  6. Approved by a person on your team
  7. Approved in Fransys › Plans. The Fransys engine executes the plan, with no AI.
  8. The app is live: api.your-app.com.

A replayed session, drawn from the product. The blocks and amounts are those of the typical app, at public rates as of October 27, 2026.

The essentials

  1. 01Claude Code works in your terminal or your editor: it reads your repository, writes the code, runs the commands.
  2. 02It does not host your application: to get it live, you need a server or a platform.
  3. 03In Europe, three paths: a server you run yourself, a classic platform, or a platform with an airlock for the agent.
  4. 04Claude Code connects to Fransys in one line, over MCP: it reads your infra and prepares its changes as costed plans.
  5. 05On Fransys, a typical app (an API, a database, a cache) comes to €164.37 a month at public rates, machines included.

Three ways to get what the agent wrote live

  1. Path 1

    A server you rent

    Claude Code installs it in an evening. After that, the backups, certificates, updates and alerts are yours.

    Who runs production afterwardsYou

  2. Path 2

    A classic platform (a PaaS)

    You push the code, it runs it. Claude Code writes the configuration; the platform does the rest, within its limits.

    Who runs production afterwardsThe platform, within its limits

  3. Path 3

    A platform with an airlock for the agent: Fransys

    The agent prepares a costed plan, a person on your team approves it, an engine with no AI executes it, under a ceiling in euros.

    Who runs production afterwardsThe engine, after your approval

European PaaS, compared

  1. Ask Claude Code:

    Read https://www.fransys.cloud/en/for-an-agent, then look at our repository. Tell me if Fransys can host this project, what would need to change, and what it would cost per month.

  2. Also ask it for the link to your infra plan (its guide: https://www.fransys.cloud/en/plan/llms.txt): the /en/plan page costs it, machines included, line by line.

  3. Open the console in demo mode, for free and with no card, to see your projects, your costs and the plans to approve.

  4. Go live: you add your card, create your cluster with the European provider you choose, and set the ceiling in euros.

  5. Connect Claude Code to Fransys: claude mcp add --transport http fransys https://mcp.fransys.cloud/mcp. From then on, every infra change goes through the airlock before it runs.

  6. Fransys deploys from your Git repository. Your current infra stays in place until you give the go-ahead.

What it costs

Resources are paid at public prices, the server at the provider's rate, with no margin. Standard support is included, with a reply within 48 h; Business adds €500 per month for a reply within 24 h; Enterprise, on a quote.

Starting price · public prices as of October 27, 2026

A typical app (an API, a database, a cache): €164.37 a month, machines included

The calculation, machines included, Standard support included
Worker machines
2 × cpx22 (2 vCPU, 4 GB) · Hetzner €39.98 + Fransys €50
€89.98
Control plane nodes
1 × cax11 (2 vCPU, 4 GB, ARM), required by the Stable criticality level · Hetzner €6.49 + Fransys €25
€31.49
Load balancer
1 × lb11 · Hetzner €7.49 + Fransys €20
€27.49
Volumes
21 GB of persistent disk · Hetzner €1.20 + Fransys €2.10
€3.30
Backups
42 GB stored
€1.26
Image registry
1 GB
€0.05
Logs
4 GB ingested, 4 GB retained
€1.20
Metrics
2,400 active series
€9.60
Total, per month€164.37
Of which Hetzner, at its public rate, with no margin€55.16

This sizing is a typical example. Yours is calculated on your infra plan.

Connect Claude Code to Fransys

One line in your terminal.

claude mcp add --transport http fransys https://mcp.fransys.cloud/mcp

Claude Code then reads your logs, your metrics, your deployment history and your costs. To act, it prepares a costed plan; nothing runs without approval from a person on your team.

Cursor, Codex and any MCP-compatible agent connect the same way, and pass through the same airlock.

Connect your agent

Before going to production, check

  • That backups are tested, not just taken.
  • That rollback works.
  • That secrets are not in the repository.
  • That preprod is not prod.
  • That someone reads the alerts, and responds when it breaks.

The twelve things an agent forgets in production

Your questions

Can Claude Code deploy on Fransys on its own?

No, and that is deliberate. It prepares a costed plan, and nothing runs until a person on your team has approved it. Then the Fransys engine, with no AI, executes it.

What about Cursor or Codex?

Same path: they connect over MCP, like Claude Code, and pass through the same airlock. Even before connecting, an agent that can read a web page can read /en/for-an-agent, look at your repository and cost your infra using our public prices.

Where do the servers run?

With the European provider you choose: Scaleway, OVHcloud, Hetzner or Outscale (SecNumCloud-qualified), in France, Germany, Finland or Poland.

We already have a Kubernetes cluster, will you take it over?

No. The platform does not take over a cluster already in place: it deploys from your repository, onto a new cluster. What our DevOps as a service covers.

Your repository, on the European cloud you choose.

No credit card, no commitment.

The airlock, in detail