Choose by workload

One cloud Mac
for all kinds of work

Run macOS workloads on a dedicated Apple Silicon physical machine. Builds, signed app distribution, inference experiments, and short-term regression testing each have a suitable configuration and rental term—so they don't all have to compete for space on a developer's local computer.

MacFTP Cloud Mac provides a complete physical machine, not a virtual machine. The macOS GUI and command line are ready to use. You manage your projects, dependencies, and workflows; we provide a cloud Mac you can connect to.

Rent a cloud Mac View rental plans

From $21.2/day, with daily, weekly, monthly, or quarterly billing. All prices are in USD.

Workflow handoff

Define the deliverable, then choose a machine

These workflow examples are illustrative; they are not active orders.

  1. Commit code → build an archive

    Self-hosted Runner · Pinned toolchain

    .xcarchive

  2. Export build → distribute for testing

    Certificate checks · Upload with fastlane

    .ipa

  3. Load model → capture results

    MLX / Core ML · Memory sampling

    Experiment log

  4. Run regression tests → export report

    Target OS · Simulator tests

    .xcresult
4 locations · 3 configurations

Singapore, Tokyo, Seoul, and Hong Kong. Check the console for real-time availability.

Continuous integration

Move builds off the developer's desktop

A good fit for iOS/macOS teams with frequent commits, multiple active branches, or a need to separate release builds from day-to-day development.

Start with FTP M4 Plus · M4 / 24GB / 512GB at $198.6/monthon a monthly plan. A dedicated machine keeps dependency caches and toolchain settings in place, cutting down on repeated environment setup.

Register the machine as a GitHub Actions self-hosted Runner or GitLab Runner, then use labels to route macOS jobs to it. Branches can submit jobs independently. For multiple heavy builds running at once, configure multiple machines and manage the queue—one dedicated machine does not mean unlimited concurrency.

Rent FTP M4 Plus View connection guide
Signing & delivery

Turn your archive into a shippable release

For App Store releases, TestFlight testing, and release teams that need to repeat signing and upload workflows.

Distribution usually follows the build, so FTP M4 Plus is a good fit. For a release concentrated in one stage, consider $107.2/weekon a weekly plan. For an ongoing release pipeline, consider monthly billing instead. Check how long the work will take; there's no need to choose a higher configuration just for uploads.

Teams in Japan may want to start with the Tokyo location to better align with local collaboration hours. Location doesn't guarantee upload speeds or change app review and processing times. Before deciding, test SSH, remote display, and artifact transfers over your actual office network.

Check certificate validity, provisioning profiles, and export settings before archiving and uploading with fastlane. A release is complete when the upload command succeeds and the target version is visible—not just when the terminal returns a success code.

Rent FTP M4 Plus Compare all rental terms
Inference & validation

Run your model first; decide on longer-term needs later

For local MLX inference, Core ML model validation, and app experiments that require real Apple Silicon hardware.

Recommended: FTP M4 Pro · M4 Pro / 64GB / 2TBon a weekly plan at $162.2/week. Its 64GB of unified memory gives model weights, the runtime, and context a larger shared memory budget—but it doesn't guarantee that models of any size or quantization will fit.

First fix the model version, quantization, context length, and batch size, then run a reproducible set of inputs. Record cold-start time, time to first output, sustained generation speed, and peak memory separately. Don't treat a single short prompt as a definitive capacity test.

MLX and Core ML support depends on the specific model and tool versions. Start with a small sample to validate operators and the conversion pipeline before scheduling longer runs. Export the environment details, result files, and reproduction commands before ending the experiment so the findings don't live only in an interactive session.

Rent FTP M4 Pro View storage add-ons
Short-term testing

Set aside a dedicated environment for regression tests

For testing on new OS versions, simulator regression, temporary macOS tasks, and short-term projects that shouldn't affect your everyday development machine.

For lighter testing, start with FTP M4 Core · M4 / 16GB / 256GB at $21.2/day. First check compatibility between your target Xcode, SDK, and OS versions. For several simulators running in parallel or larger projects, consider FTP M4 Plus.

Use the macOS GUI to work with project files remotely, or run scripts over SSH. Responsiveness depends on your local network, routing, and display settings. Try a short rental first, then extend it if the experience works for you. Workflows that need local peripherals, low-latency audio or video, or a physical device connection require separate compatibility checks.

Before changing the OS or toolchain, export your project and key settings, then confirm the required versions are available. After testing, copy reports, screenshots, and failure logs to your team's storage. A rental extension is not a backup plan, so hand off your data before the rental ends.

Rent FTP M4 Core by the day Remote access help
Move an existing project over

Local Mac → cloud Mac: three acceptance checks

Don't start by moving the entire disk. First sync a project that runs, then rebuild the toolchain, and finally connect CI. Keep the results from each check so you know where to troubleshoot if something goes wrong.

01 · Data sync

Move only source code and required inputs

Transfer the project with rsync or SFTP. Exclude DerivedData, temporary build directories, and regenerable caches; keep lockfiles, test assets, and project settings.

Check:Compare the commit ID and checksums for key files, then verify the working directory, permissions, and free disk space. Use a dry run first to review the changes.

rsync -azn \
  --exclude 'DerivedData/' \
  --exclude 'build/' \
  ./project/ \
  "$MAC_HOST:~/work/project/"

After reviewing the dry-run results, remove n.MAC_HOST is the SSH connection alias provided with your machine. This example does not delete files already on the remote host.

02 · Rebuild the toolchain

Match versions first, then add credentials

Set up Homebrew dependencies, Xcode, and Command Line Tools based on your project checklist. Verify the developer directory, then import certificates and provisioning profiles through a secure channel.

Check:Compare Xcode, Swift, and dependency versions on your local Mac and the cloud machine. Run a build that doesn't require release credentials to rule out basic environment differences first.

xcode-select -p
xcodebuild -version
swift --version
brew bundle check

brew bundle check Install Homebrew first, then run this command from the directory containing your project's Brewfile. It checks dependencies; it does not import signing assets.

03 · Connect CI

Get a successful manual run before automating

Run your project command successfully on the machine, then register a Runner using your platform's instructions. Configure repository access, job labels, the working directory, and credential permissions.

Check:Trigger a test commit and confirm that the job runs on the target machine, logs are traceable, and artifacts can be retrieved. Verify how the service runs after ending the interactive session.

uname -m
xcodebuild -list
launchctl list

Check build targets from the project directory. Runner registration and background operation depend on your platform version. One successful interactive run doesn't mean the service is ready.

How to verify the migration

The same commit can be run again; dependencies and signing inputs are traceable; results can be stored off the machine; and credentials can be revoked. Migration time depends on project size, network conditions, and tool downloads, so no fixed completion time is promised.

Start with the role

Turn the need into a testable requirement

These role-based examples help teams align on goals. They are not real customer reviews or promises of results.

“I want release builds off my colleagues' computers. For every handoff, we should be able to find the archive, logs, and toolchain version for the same commit.”

iOS lead · Example CI build requirement

“I need to compare model configurations on the same machine, recording memory, output quality, and run conditions before deciding whether to extend the experiment.”

Machine learning engineer · Example inference experiment requirement

“I want a separate environment for regression testing a new release, so I can retrieve the report without turning my everyday development setup into a test bed.”

Independent developer · Example short-term testing requirement
Before you order

Choose a configuration for the workload and a rental term for its duration

These recommendations are starting points, not performance guarantees. Test memory, storage, and job queues with your actual project before extending a rental or adding a machine. All three configurations are available in Singapore, Tokyo, Seoul, and Hong Kong.

Use case and recommended setup; prices are in USD and billed upfront for the selected term
Use case Recommended configuration Recommended rental term and price What to validate first
iOS CI/CD FTP M4 Plus
M4 / 24GB / 512GB		 Monthly · $198.6/month Resource use per archive, queue length, dependency caching, and artifact retention.
App Store & TestFlight distribution FTP M4 Plus
M4 / 24GB / 512GB		 Weekly · $107.2/week Certificates and provisioning profiles, export settings, upload credentials, and processing results.
MLX / Core ML experiments FTP M4 Pro
M4 Pro / 64GB / 2TB		 Weekly · $162.2/week Model compatibility, quantization settings, context length, and peak memory.
Short-term regression & remote work FTP M4 Core
M4 / 16GB / 256GB		 Daily · $21.2/day Target toolchain, simulator needs, remote interaction, and data export.

Need more capacity?Storage expansion and Thunderbolt 5 daisy-chaining are optional add-ons and don't change the base configuration lineup. See the full rental plans for pricing, compatible configurations, and billing terms.

Check compatibility first:These recommendations may not fit workloads that depend on an Intel Mac, require permanent hardware ownership, or need a machine outside the listed configurations. List your tool and connection requirements, then contact us by email or through a console support ticket.

Payment & delivery:We accept USDT-TRC20, Visa, Mastercard, and Amex through Stripe. All prices are in USD. Check the console for currently available payment gateways and machine locations.

Compare three configurations and four rental terms Discuss project compatibility

Start with one task and complete a real handoff

Bring your project’s tool versions, resource requirements, and expected rental term, then choose a configuration and location. You don't have to rebuild an existing pipeline all at once—start by getting one reproducible task running.

Rent a cloud Mac View all rental plans