VPS for iOS and macOS Development — from €5.49/mo
Move builds, tests and your repository to a server — the backbone for an iOS team next to your Mac, a 5-hour test period before payment, completely risk-free
Set up a team server
Straight to the point: we do not rent physical Macs or virtual macOS — final builds and code signing for iOS and macOS must run on Apple hardware, as the macOS licence requires. Our VPS covers everything else in an iOS team workflow: the Git repository, CI runner, test API stands and build artifact storage. You install Linux or Windows yourself, deploy your stack and attach your own Mac as a build agent. Plans start at €5.49/mo, and a 5-hour test period lets you verify your pipeline before paying.
Plans
A server for an iOS team
A Git repository and light tasks fit Standard 1 (4 vCPU, 4 GB); a CI runner and test stands need Standard 2 (4 vCPU, 6 GB) or higher. A 5-hour test period before payment.
Compare all plansStandard 1
| 4 vCPU · AMD EPYC |
| 4 GB RAM |
| 50 GB NVMe |
| Unlimited traffic |
| 1× IPv4 · KVM |
| 24/7 support |
Standard 2
| 4 vCPU · AMD EPYC |
| 6 GB RAM |
| 60 GB NVMe |
| Unlimited traffic |
| 1× IPv4 · KVM |
| 24/7 support |
Git and a CI runner
Run your own Git server and build runner: linters, unit tests and static analysis execute on the server, not on a developer laptop.
Test stands and APIs
Keep the backend, mocks and test databases for your app in one place — the team tests against a shared stand, not local copies.
Artifacts on NVMe
Builds, distributions and dependency caches live on fast NVMe drives with a dedicated IP — SSH access from anywhere.
How to fit the server into an iOS pipeline
Choose a plan and an image
Pick a plan — Standard 1 (4 vCPU, 4 GB) or Standard 2 (4 vCPU, 6 GB) — and a Linux image for your CI stack.
Install the OS yourself
Through the panel you deploy the chosen OS on a KVM server yourself — the configuration stays fully under your control.
Attach the runner and stands
Install a Git server, a CI runner and test services, and delegate the Apple build step to your own Mac — it joins the same pipeline.
What to move to the server, what to leave on the Mac
Only what requires Apple tooling stays on the Mac: Xcode compilation, code signing and App Store uploads. Everything else — the repository, tests, backend, artifact storage and notifications — moves to the VPS and stops depending on a single machine in the office.
We will suggest how many vCPU and how much RAM your pipeline needs. The base environment is described on the Linux VPS page, and build pipelines are covered in VPS for CI/CD.
Help me chooseFrequently asked questions
Didn't find your answer?
Write to us via the contact page.
No. We rent servers with Linux and Windows; physical Macs and virtual macOS are not in the line-up. For an iOS team the server covers CI, the repository and test stands.
Final builds and code signing run only on Apple hardware — the macOS licence and Xcode tooling require it. Our server takes over the remaining pipeline steps.
The Git repository, CI runner, unit tests and linters, a test backend with a database, build artifact storage and upload scripts. That is almost the whole pipeline except the compile step.
Yes, that is the typical setup: the CI coordinator and job queue live on the VPS, while a Mac mini in the office connects as a separate build agent and takes only the Xcode steps.
A runner with tests and a test database fits 4 vCPU and 6 GB — Standard 2 at €6.99/mo. If several builds run in parallel, take 8 GB (Standard 3, €8.99).
Linux: Ubuntu LTS for fresh packages and documentation, Debian for stability. Windows is chosen when .NET tooling or Windows tests are needed nearby.
You do: pick an image and deploy the OS through the panel in a couple of minutes. A KVM console gives hardware-level access if something goes wrong.
Automatic backups are not included in the plan — you run backups yourself in the control panel in a couple of clicks. The repository is worth mirroring to external storage as well.