Remote Mac desktop
Access a development desktop from a non-Mac workspace to review projects and use graphical tools.
View connection tips
Start with your workload
Your work, connected to a dedicated cloud Mac
Whether you need a remote desktop, app development, build jobs or model testing, start with the same question: how much memory and storage does the task need, and what connection will work for you? XCZone provides dedicated physical Macs, not virtual machines. Compare the use cases below, then choose a configuration and location.
Three configurations and five locations. Check the console for real-time availability.
Task → configuration → connection
Configuration checklist
Start with the task
Do you need a graphical desktop or a build job that runs continuously?
One physical node can support different workflows, but choose a configuration based on your most demanding real-world task.
- Memory
- Combined usage from project processes, tools and models
- Storage
- Source code, dependencies, simulators and build caches
- Connection
- Local network, desktop client and team location
NextCompare use cases, then check plan pricing
Use cases
Find the workflow closest to yours
These five use cases aren’t mutually exclusive plans. Start with the task at hand, then factor in concurrent tools, caches and connection requirements.
iOS and macOS development
Check memory and local cache needs based on project size and the tools you run at once.
Compare configurationsiOS CI/CD
Run pipelines on a build node, with permissions and environment consistency built into your checks.
See how to connectAutomated app builds
Link dependencies, signing assets, builds and artifact checks in a workflow you can review.
View the delivery checklistApple Silicon AI experiments
Check model memory requirements and tool compatibility before considering a higher configuration.
See how to evaluate
Remote desktop
Your workspace doesn’t need to be a Mac. Your development desktop still is.
When working from a non-Mac device, use the connection details provided to access your cloud Mac’s graphical desktop, open projects, review interfaces or run development tools. Remote access is simply how you use the machine; underneath, it’s a dedicated physical Mac, not a virtual machine shared by multiple users.
Before connecting, check that your local network is stable, your remote desktop client is compatible, and the display resolution and input method suit your task. If you need to monitor animations closely or make precise interface changes, test the experience on your own network and device first. Don’t assume connection quality based on a location name alone.
Check these four things before you start
- Delivery detailsCheck your selected configuration, location and the connection method provided in the console.
- Local networkMake sure your network allows the required client, and watch for visual and input feedback while connected.
- Display and inputCheck that the resolution, keyboard layout and shortcuts suit your development workflow.
- End your sessionSign out when you’re done to protect connection credentials and sensitive project materials.
Everyday development
Choose a configuration by concurrent workload, not project name
Editors, browsers, simulators and build processes all use memory at the same time. Beyond source code, dependencies, simulator data and build caches also take up SSD space. Check usage in your current environment and leave room for growth.
XcodeZone M4 Start
M4 · 16GB RAM · 256GB SSD
A good fit for trying a remote development workflow or running a project with a small set of tools and caches you can clean up regularly. If you often run simulators alongside several large projects, check your peak memory use first.
Choose XcodeZone M4 StartXcodeZone M4 Work
M4 · 24GB RAM · 512GB SSD
A good fit if you want more headroom for your editor, simulators and everyday build tools. The larger SSD can hold more dependencies and build caches, but check your project’s actual storage needs.
Choose XcodeZone M4 WorkXcodeZone M4 Pro
M4 Pro · 64GB RAM · 2TB SSD
For heavier concurrent workloads or projects that need to keep a large amount of data locally. Choose this configuration based on actual memory usage, tool compatibility and storage needs.
Choose XcodeZone M4 ProIf your project data keeps growing, compare the four billing periods for SSD add-ons on the plans page. Don’t estimate long-term storage needs from the included capacity alone.
CI/CD
Connect a build node to your pipeline and track environment differences
A cloud Mac can serve as the physical node for a self-hosted runner. Before connecting it, check your code hosting permissions, macOS and Xcode version requirements, dependency installation method, and how build jobs will access the signing assets they need.
Code commit
Set the trigger branch, job permissions and files to check out. Don’t put tokens or certificates directly in the repository. Record a build command that works locally so you can compare it with pipeline results.
Self-hosted runner
Check the runner account’s permissions, toolchain version and dependency state. Make installation, cleanup and retry steps repeatable, and account for RAM and cache usage across concurrent jobs.
Build artifacts
Check the job’s exit status, key logs and artifact paths. Verify signing and target settings before delivery. If a job fails, keep enough information to troubleshoot without exposing sensitive values in public logs.
What you’re responsible for
A dedicated physical Mac doesn’t mean your pipeline is already configured. Your team is still responsible for code permissions, signing assets, runner updates and a consistent build environment.
Automated builds
Turn manual checks into a build workflow you can verify step by step
Automation is about more than fewer clicks: it makes results traceable for the same source code and configuration. First define which dependencies jobs install, which signing assets your team authorizes, and where to look in the logs if something fails.
Your team manages certificates and provisioning profiles. Never put private keys in scripts, public repositories or support tickets, and don’t assume the remote machine will store or update signing assets for you.
- 01Install dependencies
Pin tool and project dependency versions, then confirm installation works in a clean environment.
- 02Verify signing
Check the signing identity, provisioning profile, target identifier and job access permissions.
- 03Run the build
Record build parameters, exit status and log location so you can track down differences.
- 04Verify before delivery
Check that the artifact was generated, signing matches the target, and delivery version details are correct.
Apple Silicon AI experiments
Estimate model memory use before choosing more RAM
For local inference or development tools, first check the model files, memory usage after loading, and framework support for Apple Silicon. The model isn’t the only consideration: input context, concurrent processes and development tools also use resources. Downloads and intermediate files need SSD space too.
If your assessment points to a higher memory budget, compare the XcodeZone M4 Pro with 64GB RAM. This recommendation doesn’t guarantee support for a particular model, throughput or runtime. Test with your target tools and actual workload before choosing a rental period.
What to check before experimenting
- Model
- Check the version, file size and documented memory requirements.
- Tools
- Confirm that frameworks and dependencies support your target macOS and Apple Silicon environment.
- Concurrent tasks
- Include your editor, services and other running tools in your memory budget.
- Validation
- Use your own model and inputs to track memory use, results and error logs.
Choose a location
Five locations: choose based on your team and connection experience
The catalog includes Singapore, Tokyo, Seoul, Hong Kong and the US West. Location can help narrow your options, but it doesn’t reflect measured latency from your network. If your workflow depends on remote desktop access, test the connection with your own network and client. For team builds, consider where team members hand off work and retrieve artifacts.
Singapore
A location to consider for cross-region collaboration and remote access. Make your choice based on your own connection conditions.
Tokyo, Japan
If your team or daily work is based nearby, include it in your connection tests.
Seoul, South Korea
Consider where people work, how often they use remote desktop, and how work is handed off.
Hong Kong
Compare display and input responsiveness against other locations using the same client and network.
US West
For work involving US West collaboration, test your connection and delivery workflow first.
All three configurations are listed for these five locations. Check the console for real-time availability when you order.
Review your options
Write down three requirements, then compare pricing
Note your workflow’s peak memory use, the storage needed for source code and caches, and your usual connection location. If anything is unclear, measure it in your current environment or run a small test. That’s more reliable than judging by the configuration name alone.
| Configuration | Chip | Memory | SSD | What to check |
|---|---|---|---|---|
| XcodeZone M4 Start | M4 | 16GB | 256GB | Concurrent tools and cache space for lighter workflows |
| XcodeZone M4 Work | M4 | 24GB | 512GB | Simulators, dependencies and build caches for everyday development |
| XcodeZone M4 Pro | M4 Pro | 64GB | 2TB | Memory needs for heavier concurrent workloads or experiments |
This table is a selection guide, not a performance guarantee. The plans page lists daily, weekly, monthly and quarterly pricing for each configuration, along with storage add-ons. Check the configuration, location and rental period before ordering.
Know what you need? Configure your cloud Mac
Start with your memory, storage and location requirements. Compare configurations, rental periods and add-ons step by step.