xtool: A Cross-Platform Xcode Replacement

TL;DR: xtool is a Swift command line tool that replaces Xcode for building and deploying iOS apps, working across Linux, Windows and macOS through Swift Package Manager. It is MIT licensed, sits at 9,467 stars, and has been in development since November 2024.

What it is

Xcode is macOS-only, and for a long time that made iOS builds a hard dependency on Apple hardware. xtool attacks that directly by giving you a path to build and deploy iOS apps from any of the three major desktop platforms.

The repository states the scope plainly: cross-platform Xcode replacement, build and deploy iOS apps with SwiftPM on Linux, Windows and macOS. The site is at xtool.sh.

$ curl -s https://api.github.com/repos/xtool-org/xtool \
  | jq '{stars: .stargazers_count, language, license: .license.spdx_id, topics, created_at}'
{
  "stars": 9467,
  "language": "Swift",
  "license": "MIT",
  "topics": ["ios","linux","swift","swift-package-manager","windows","xcode"],
  "created_at": "2024-11-17T08:18:44Z"
}

Why this matters

The obvious win is CI. A build server that costs a fraction of a Mac, or a Linux container, can produce iOS artefacts without a dedicated Mac mini in the rack. That changes the economics of iOS continuous integration for teams that were previously paying for the privilege.

The topic list tells you the mechanism. It is built on Swift Package Manager, which means it leans on the same open package tooling the rest of the Swift ecosystem uses rather than inventing a parallel build system.

Two years of development history is a reasonable signal here. Created 2024-11-17, still pushing code as of 2026-10-14, with 93 open issues against 9,467 stars. That is a healthy ratio, and the issue count being an order of magnitude lower than vercel-labs/skills at a similar star count suggests a more settled project.

How to try it

git clone https://github.com/xtool-org/xtool.git
cd xtool

Because the source is Swift and the tool is distributed through SwiftPM, the interesting part is the cross-platform story rather than a single install command. Whether it can actually replace your existing Xcode workflow depends on how much of what you rely on lives outside the build-and-deploy path.

What it does well

It targets a real gap rather than a fashionable one. Plenty of teams ship iOS apps from non-Mac infrastructure already, and most do it with a pile of shell scripts and certificates they maintain themselves. A maintained tool that consolidates that is a genuine improvement over homegrown scripts.

MIT licensing keeps the adoption risk low, and for tooling that sits in your build path that matters.

When to use it

Reach for it when you need iOS builds to run somewhere that is not a Mac. Linux and Windows build agents are the obvious case, and xtool is the most credible open answer to that problem right now.

It is also a reasonable fit for teams that want build and deploy as a CLI operation rather than a GUI workflow, since scripted builds compose more cleanly into CI.

When not to use it

Xcode is a much larger tool than a build system, and the description scopes xtool to building and deploying. If your workflow depends on Xcode for profiling, debugging, interface design, simulator work or signing in ways this does not cover, you are not replacing Xcode. You are adding a second tool.

Read that carefully before migrating anything. “Xcode replacement” is the project’s framing; “build and deploy iOS apps from any platform” is what the description actually commits to.

Second, iOS signing remains the hard part on non-Mac infrastructure regardless of tooling. Provisioning profiles and keychain access are not made simpler by having a nicer CLI.

Source and Accuracy Notes

• Project page: https://xtool.sh
• Source repository: xtool-org/xtool (verified via GitHub API html_url)
• License: MIT (verified via GitHub API license.spdx_id)
• Stars at time of writing: 9467