Figment vs Green Mini host: Mac Hosting Compared

Green Mini host (greenmini.nl/products) rents Apple silicon Mac minis from a Rotterdam datacentre, priced in EUR with no long contract and friendly remote hands during business hours. Figment competes directly with an M-series line from $95/month, a $29 virtual Intel macOS runner, and two managed tiers that package the CI work most teams do by hand. This page gives you the primary-source price map, the toolchain fit, and a concrete switch plan.

Verdict and the Figment plan that fits

At entry level, Green Mini host's M2 mini at €59/month is cheaper in nominal EUR than Figment's M-series entry at $95/month USD. $95 is an entry price and is not a verified M4/16/256 build — the exact chip, RAM, and disk are confirmed in your quote, so do not treat it as the same hardware as Green Mini's €74 M4. Apply a current ECB rate on your transaction day for a real conversion; the ECB reference on 2026-11-10 was 1 EUR = 1.1214 USD, which puts €59 at about $66.16 and €74 at about $82.98 before bank or card fees.

Where Figment separates is work, not metal. The Managed Build Mac at $249/month includes one M-series Mac, CI pipeline setup, automated backups, monitoring, and 30 minutes of hands-on support each month. Managed Mac Team at $999/month covers two M-series Macs, two CI runners, team setup, backups, monitoring, and one hour of monthly support. Green Mini host sells hardware plus support; it does not publish an equivalent managed CI package. If your team would otherwise spend engineering time maintaining runners, the managed tier is the material difference.

For a budget secondary runner the Figment $29/month plan is a virtual Intel macOS environment (2 vCPU, 8 GiB RAM, 80 GiB disk, browser-console access, outbound network for CI agents). It runs on Linux/KVM, has no GPU acceleration or audio, and is not Apple silicon — but it is a real Intel macOS runner, so it executes compatible Intel-Mac toolchains in-place.

Request a configuration quote at /mac-hosting/start.

Published plans and effective cost

Green Mini host prices verified against greenmini.nl/products on 2026-11-10. Base configurations shown; several lines allow upgraded RAM or disk at additional cost.

Green Mini host does not list a setup fee and does not publish an annual-prepayment discount on the products page; monthly billing is the default and volume discounts are stated for 10+ servers. Payment methods include credit card, iDeal, SEPA transfer, and SEPA direct debit. Taxes, fees, and currency conversion appear on the actual order. Figment prices are USD monthly; physical-hardware and i3 plans currently collect configuration requests until supply is confirmed, so do not assume instant availability.

Worked cost example — twelve months on an entry M-series runner:

• Green Mini host M4 / 16 / 256: 12 × €74 = €888/year. Approx. $995.80 at the 2026-11-10 ECB rate (before card fees).
• Figment M-series entry at $95/month: 12 × $95 = $1,140/year. Delta to Green Mini's M4 is about $144 at today's rate, in exchange for US-dollar billing and the option to upgrade into the $249 managed tier without changing provider.
• Figment Managed Build Mac $249/month: 12 × $249 = $2,988/year. Compare that to Green Mini's M4 plus the loaded cost of roughly 30 minutes of your own DevOps time per month plus backup and monitoring tooling.

No annual Figment discount is promised and none is assumed here; confirm final terms in the quote.

Hardware, access and toolchain fit

Green Mini host's whole current line is Apple silicon (M2, M4, M6, M4 Pro, M5 Pro, M5 Ultra). Figment's physical M-series is also Apple silicon; the exact chip generation lands in the quote. Access on Green Mini host is dedicated hardware over the public network with support available; access to the Figment $29 virtual Intel macOS is through its browser console with outbound network for CI agents — inbound public SSH to that VM is not implemented, so plan secret and artifact flow accordingly.

Xcode compatibility per Apple's requirements table on 2026-11-10:

Treat Xcode 26.x and 27.x as Apple-silicon-only; pick either provider's physical M-series for those. The Figment virtual Intel macOS runs Xcode 16.x and the 15.x and 14.3.1 lines that Apple still lists as Intel-compatible, which is enough for many maintenance branches and some iOS simulator work — confirm the exact Xcode/macOS pair in Apple's table before committing. visionOS simulator work requires Apple silicon on either provider.

Reliability evidence and a build-time test you can run

Green Mini host publishes ">99.99% uptime in the last 12 months" on its products page; that is an observed figure, not a contractual SLA, and Figment does not publish a verified SLA number. Rather than guess, time your own project on each candidate.

#!/usr/bin/env bash
# Build-time sampler. Run on each candidate host after cloning your repo
# and installing the Xcode version your pipeline uses.
set -euo pipefail

PROJECT="${1:?path to .xcodeproj or .xcworkspace}"
SCHEME="${2:?scheme name from your project}"
DESTINATION="${3:-platform=iOS Simulator,name=iPhone 16}"

for run in 1 2 3; do
  echo "=== Run $run on $(hostname) at $(date -Iseconds) ==="
  # clean build; set -e aborts the script on any failure so a broken
  # build is never silently recorded as a fast run.
  /usr/bin/time -p xcodebuild \
    -project "$PROJECT" \
    -scheme "$SCHEME" \
    -destination "$DESTINATION" \
    -skipPackagePluginValidation \
    clean build
done

Take the median of three completed runs. Discard any run that does not reach the final build success — set -euo pipefail makes the script exit, so a failure is visible, not timed as success. This is an unexecuted example, not a benchmark.

Migration: Green Mini host → Figment

Before provisioning. Submit the Figment configuration request at /mac-hosting/start with your required chip generation, RAM, disk, and target Xcode version. Confirm the macOS/Xcode pair against Apple's table. Write a names-only list of every secret your pipeline needs (certificate labels, token names, API key names) — no values in that file.

Export from Green Mini host. Export each iOS signing certificate with its private key as an encrypted .p12 from Keychain Access and store the password in your team's secret manager, not in a repo or a plaintext env file. Download provisioning profiles as .mobileprovision from the Apple Developer portal — they are files, not Keychain exports. CI configuration (.yml, Fastfile, shell scripts) stays in the repo and travels with the clone.

Restore on Figment. Install the matching Xcode first. Import the .p12 into Keychain using the stored password. Drop .mobileprovision files into ~/Library/MobileDevice/Provisioning Profiles/. Restore secret values through your CI vault or secret manager; never bulk-dump env to a plaintext file — it will pick up tokens. Run a clean build and confirm code signing.

Allowlists and cutover. If you maintain your own firewall, artifact store, or CI service IP allowlists, update them for the Figment host's outbound address; Apple services such as App Store Connect and TestFlight do not publish a fixed allowlist to pin against. Run your full test suite on Figment before cancelling the Green Mini subscription, and review Green Mini's cancellation terms on its products page.

Choose your Figment plan

Green Mini host is a good fit for EUR-billed teams that want dedicated Apple silicon at a low monthly rate and will run their own CI. Figment is the fit when you want US-dollar billing and the managed CI/backups/support bundled rather than assembled. Start your Figment quote at /mac-hosting/start or read the overview at /mac-hosting.

Related reading:

• Figment vs HA Hosting
• Figment vs Hatmac
• Managed Build Mac or Team: which plan?