# xCloud v2.9.11

> Released November 10, 2026

**Deploy Python, Ruby, Go, Java and Bun Apps from Git, and Keep AI Agents Away from Destructive Actions**

Every team can now deploy Python, Ruby, Go, Java and Bun apps from Git, and their data folders are kept between deploys. You can give a script or AI agent an API token that cannot delete or reboot anything. Team admins can now require two-factor authentication for every member.

## 🔥 New Features

### 🆕 Deploy Python, Ruby, Go, Java and Bun Apps from Git

Before, only a few teams could deploy these stacks from Git. A redeploy of an app built from its own Dockerfile could also lose the data in its folders. Now every team can deploy them, and the data stays.

**Who it's for:** Developers who deploy apps from Git.

-   Pick a Python, Ruby, Go, Java or Bun repository in **Deploy via Git**. xCloud detects the stack and offers to run it as a Docker container.
-   The form shows which folders are **Kept between deploys**. Every one of these apps keeps `/app/data`. Rails also keeps `/app/storage`, and Django also keeps `/app/media`.
-   If your app has its own Dockerfile, a redeploy now keeps the data in the folders it saves data to.
-   Laravel, Node.js and PHP repositories still deploy natively, even when they ship a Dockerfile. You can still pick the container instead.
-   If your server cannot run containers, you are told before you pick a repository. On an OpenLiteSpeed server you are told to use an Nginx server, and you can pick another repository with **Change Repository**.
-   Required `.env` values are checked before the site is created. When a small server runs out of memory during a build, the failure says so.

[How to Deploy Git Projects in One Click with xCloud](/docs/deploy-git-projects-in-one-click-with-xcloud/)

### 🆕 API Tokens That Refuse Destructive Actions

Before, the only guard against an AI agent deleting a site or rebooting a server was a confirmation the agent could send itself. Now you can give it a token that cannot do that at all.

**Who it's for:** Everyone who connects scripts or AI agents to xCloud with an API token.

-   Tick **Refuse destructive actions** when you create an API token.
-   To change an existing token, use the shield button on its row. The list marks such tokens **Refuses destructive actions**. Turning the option off asks you to confirm first.
-   Such a token can still read your servers and sites. Actions that xCloud counts as destructive, such as deleting a site or rebooting a server, are refused, even when the agent only asks to test them first.
-   Existing tokens are unchanged. The option is off unless you tick it.

[Manage Multi-Team API Tokens and MCP Connections](/docs/multi-team-api-tokens-and-mcp-access/)

## 🧑‍💻 For Developers: Public API and MCP

-   **Tokens that refuse destructive actions:** a destructive Public API call with such a token answers `403` with `errors.code` `forbidden_destructive`, `errors.next_actions` `use_token_allowing_destructive` and `errors.operation`. MCP answers `destructive_refused` and hides destructive tools from that token. On the Enterprise API, every write from such a token answers `403` `forbidden_destructive`.
-   **Disconnect Git:** `POST /sites/{uuid}/git/disconnect` stops a site deploying from its repository. It answers `422` while a deploy is running.
-   **Deploys on a disabled site:** Git deploys through the Public API and MCP now answer `409` "This site is disabled. Enable it to deploy." right away.
-   **Container or native:** on Git site create, `deploy_mode=dockerfile` still runs a Laravel, Node.js or PHP repository as a container.
-   **Release mode:** the release mode endpoints, and `release_mode` on Git site create, now work for every team.
-   **Freshness:** reads of WordPress plugins, themes, updates and status, site events, access logs and banned IPs now always return `observed_at`, `source` and `stale`.
-   **Managed PostgreSQL:** restart, logs and health now work for every team once PostgreSQL is ready.

## 🔒 Security

-   **Cloudflare Enterprise:** setting up a Cloudflare Enterprise domain now only changes servers in the domain owner's own teams.
-   **Google Drive and pCloud:** when you connect Google Drive or pCloud as backup storage, the sign-in code now stays on xCloud. It no longer passes through a white label brand's own domain.

## ⚡ Improvements

### Require Two-Factor Authentication for Your Team

Before, a team owner could not see who had no two-factor authentication (2FA), or make it a rule. Now admins can see it and require it.

**Who it's for:** Agencies and teams with several members.

-   The members table on your team page has a **2FA** column that shows **Enabled** or **Not enabled**. Only people who can edit the team see it.
-   In the team settings, tick **Require two-factor authentication for all members**. The team page then shows a **2FA required** badge.
-   A member without 2FA can only open their authentication settings until they turn it on. A notice there names the team.
-   You can turn the rule on only after your own account has 2FA.

[How to Manage Teams, Roles, and Permissions in xCloud](/docs/team-roles-permissions-in-xcloud/)

### Pending Invites Get Their Own Section, with the Invite Link

Before, pending invitations were mixed in with your members, and you could only send the link again by email. Now they have their own list, and you can copy the link.

**Who it's for:** Agencies and teams that invite people.

-   Your team page has a **Pending invites** section. Each row shows the person, role, server count, invited date and the invite link.
-   Use **Copy Link**, **Change Role**, **Resend Email** or delete on each row. The link works for 7 days, and only for the invited email address.
-   Only people who may invite members see the link and the actions.

[How to Manage Teams, Roles, and Permissions in xCloud](/docs/team-roles-permissions-in-xcloud/)

### Disconnect a Site from Git

Before, you could not delete a Git provider while a site still deployed from it, and nothing let you move the site off it. Now a button does it.

**Who it's for:** Developers who deploy from Git.

-   Open the site's Git page and click **Disconnect Git**. The site and its files stay exactly as they are, so your deployed code keeps running.
-   Once its last site is disconnected, you can delete the Git provider.
-   Disconnecting is refused while a deploy is running.

[Connect GitHub and Deploy Git Projects with xCloud](/docs/how-to-integrate-a-git-provider-with-xcloud/)

### Billing Suspensions Lift Once You Pay

Before, a server or site suspended for an unpaid bill stayed suspended after you paid, until we brought it back by hand. Now it comes back on its own.

**Who it's for:** Everyone.

-   Once every due invoice is paid, xCloud restarts your suspended servers and brings back your sites, usually within a few minutes.
-   A message, **Your services are back**, names what came back. Servers can take a few minutes to start.
-   Suspensions for abuse are not lifted this way.

[Why xCloud Suspends a Site or Server: Billing and Abuse Suspensions Explained](/docs/why-xcloud-suspends-a-site-or-server-billing-and-abuse/)

### More Changes

-   **Release mode for every team:** every site's Git page now shows the **Release mode (zero-downtime deploys)** card. Each site still opts in. If a site can't use it, the card says why. [How to Use Zero-Downtime Deployments (Release Mode) in xCloud](/docs/zero-downtime-deploys-with-release-mode-in-xcloud/)
-   **Managed PostgreSQL:** every team can now restart managed PostgreSQL from the server's management page and read its logs. A restart drops sites' database connection for a few seconds. [How to Install Managed PostgreSQL and pgAdmin in xCloud](/docs/install-managed-postgresql-and-pgadmin-in-xcloud/)
-   **Free plan signup:** a new Free account now lands on the dashboard, not on Bills & Payment. A banner and a To-Do item ask you to add a payment method, with an **Add Payment Method** link. The dashboard, server list and site list open before you add it. [Set Up Your First Server with xCloud Managed Servers](/docs/setup-your-first-server-site-with-xcloud/)
-   **Site-down banner:** it now says "Your site isn’t responding" with the status code and time of the last check, and fits beside the assistant panel. **Diagnose this site** starts from the failed check.
-   **Server upgrade:** the **Server upgrade is not available** notice on xCloud Managed servers now shows as information, not a warning.

## 🐞 Bug Fixes

-   **Git Deploys**
    -   A deploy no longer removes the site's File Manager, so the File Manager keeps working.
    -   A deploy into a site folder that is missing, or has no `.git`, now says which case it is and what to do. Before, it said only "not a git repository".
    -   Deploys to a disabled site are now refused at once with "This site is disabled. Enable it to deploy." This includes push-to-deploy. Before, they failed and sent a failure email each time.
-   **Sites**
    -   **Disable Site** now always disables the site. Before, clicking **Disable** without turning on the inner switch left the site enabled.
    -   Changing a WordPress site's domain no longer leaves the site without xCloud-Cron when SSL setup for the new domain fails.
-   **Servers**
    -   New servers now install and start cron, so scheduled tasks, WP-Cron and monitoring run on minimal server images too.
    -   Auto healing now restarts a stopped MariaDB database. Before, a stopped MariaDB stayed down.
    -   Nginx updates now always switch your server to the new Nginx version. Before, some servers kept running the old one.
    -   **Regenerate Nginx Config** no longer breaks Nginx on a server where your own site is the default site, and puts the server's default back if it fails.
-   **Cloudflare Enterprise**
    -   A failed origin certificate install now keeps the working certificate. Before, one bad certificate could break every site on the server.
-   **One Click Apps**
    -   Python One Click Apps, such as Flask or Django apps, no longer hang on logins, forms and uploads.
-   **To-Do and AI Assistant**
    -   The PHP security patch item no longer shows **Fix with AI** next to its one-click **Fix**.
    -   The login protection suggestion now reads **Recommended**, not **Needs attention**.
    -   The assistant's To-Dos entry now works the first time you open the assistant, and shows "No To-Dos right now. Everything looks good." when nothing is open.
    -   The server name under the site header stays readable with the assistant panel open.
