Let the data center handle power, network, and coolingYour build server, online 365 days a year

A dedicated physical Mac mini—not a virtual machine—with service arranged to run 365 days a year. Our iOS build servers are hosted in five locations: Singapore, Tokyo, Seoul, Hong Kong, and the western United States. Each machine is reserved for one team.

Rent a build server Compare the three plans
Port M4 Base from $19.7/dayDaily · weekly · monthly · quarterlyBilled in USD

Build schedule

tokyo-node-07 · Apple Silicon M4 Pro · 64GB unified memory · 2TB SSD

Year-round service scheduleOnline 365 days a yearIllustrative service schedule · each cell represents 1 day
Pipeline · example schedule
00:0006:0012:0018:00
main7 runs · example average 6m12s
release/2.43 runs · example average 9m40s
nightlyFrom 02:00 · includes UI tests

Example nightly task: UI tests, 2h05m. Branches share this team's CPU, memory, and storage. Set concurrency based on tests against your project.

Illustrative CPU usageThis team's tasks only

Schedules, durations, and online indicators are illustrative, not measured data. Check the console for current availability.

Run your favorite build tools on a dedicated server

Xcode fastlane GitHub Actions GitLab CI Jenkins Flutter React Native

These tools are installed on the server in the usual way and work just as they do on your own Mac. Their inclusion describes compatibility, not a partnership or endorsement. Your team remains responsible for tool versions, dependencies, and runner updates.

Compare your options

Self-hosted, shared runners, or dedicated hosting: which fits your team?

All three approaches work well for different teams. Compare where each fits—and where it doesn't—before deciding whether to rent an iOS build server.

Self-hosted

Mac mini in your office

Cost-effective for occasional builds if you already have a spare Mac

A good fit

  • You build occasionally and already have a spare Mac.
  • Someone can manage power, network, and system updates.
  • Your code or dependencies must stay on your company network.

Less suitable

  • You merge several times a day and can't rely on office power for overnight builds.
  • Network issues are frequent, and someone has to be on-site to restart the machine.
  • You want to take hardware upkeep off the release engineering team's plate.
Shared

Shared hosted runner

Convenient for light build workloads if queueing is acceptable

A good fit

  • Builds are infrequent and spread out, so waiting won't disrupt daily merges.
  • You need to scale up to many concurrent tasks for a short time.
  • You want to minimize machine management.

Less suitable

  • Builds often queue up, and shared capacity affects your release schedule.
  • Your workflows rely on DerivedData and dependency caches to stay fast.
  • You need a macOS environment you can control over the long term.
Dedicated

Data-center-hosted dedicated server

A good fit for frequent builds when you don't want to maintain hardware

A good fit

  • You merge several times a day and don't want to manage power, networking, or cooling.
  • You want to keep caches and set your own build order across branches.
  • Your team develops on Windows and needs remote macOS builds.

Less suitable

  • You build only once or twice a month and already have an idle machine.
  • You need to scale instantly to dozens of machines; a single dedicated server has limited elasticity.
  • You want someone else to manage your project dependencies, certificates, and pipelines too.
View the comparison table
Online year-round

Hosted in a data center and online 365 days a year

The data center handles power, networking, and cooling, so overnight nightly builds don't get skipped when the office loses power.

365days

Online year-round

The server doesn't follow your office hours.

0scheduled outages

Scheduled downtime

No need to plan build schedules around recurring service downtime.

5locations

Data center locations

Singapore, Tokyo, Seoul, Hong Kong, and the western United States.

1 server / 1 team

Dedicated physical server

Your server isn't shared with other customers.

Important note:Year-round operation doesn't mean hardware can never fail. If an issue occurs, submit a support ticket with the server name and error details. We'll help investigate, move you to another server, and restore the environment. Keep independent backups of your code, signing materials, build artifacts, and essential caches. Your team will still need to help rebind the runner and restore the environment after a server change.

See how server replacement works
Dedicated physical server

One Mac mini, reserved for your team

It's a physical machine, not a virtual machine, and it's not shared with other customers. Here are four key differences between a dedicated server and a shared plan.

Dedicated

The whole machine is yours

The server is assigned to your account and won't be allocated to another team during your rental. You can connect multiple developers and pipelines within your team.

Physical server

Not a virtual machine

Builds run directly on physical Apple Silicon hardware. The full macOS graphical interface and command line are available, so you can manage tools and dependencies for your project.

OSXPort orbital ring station logoOSXPort1 server · 1 team
Caching

Your caches stay in place

DerivedData, CocoaPods, and SPM caches aren't cleared by other customers' tasks. Set your own cleanup policy to keep archives and caches from filling the SSD.

Concurrency

No competing with other customers for CPU

When main and release build at the same time, they share resources only with your team's tasks. Dedicated doesn't mean unlimited concurrency: simulators and compile jobs still share the machine's capacity.

Read the dedicated server setup guide
Apple Silicon M4 / M4 Pro

M4 or M4 Pro? Choose for your project

Two chip options across three server plans. Start with M4 for a single-app project. Consider M4 Pro with 64GB for large multi-target builds, more concurrent tests, or local model inference.

Apple Silicon M4

Available in Port M4 Base and Port M4 Plus

Chip
Apple Silicon M4
Unified memory
16GB / 24GB
Storage
256GB / 512GB SSD

M4 is a good fit for

  • A single app or a small number of targets.
  • Everyday builds, archiving, and automated distribution.
  • A controlled number of simulators with incremental caching.

Not recommended for

  • Running multiple simulators at once with 16GB of memory.
  • Large projects with sustained high concurrency and no task limits.

Apple Silicon M4 Pro

Available in Port M4 Pro

Chip
Apple Silicon M4 Pro
Unified memory
64GB
Storage
2TB SSD

When you need more headroom

  • Large projects with multiple targets and schemes.
  • Concurrent UI tests across multiple simulators.
  • Local model inference and quantization tests that benefit from more memory.

Not needed for

  • A single app with a few builds a day.
  • Workloads requiring multi-GPU training or specialized accelerators.
Full pricing

Three dedicated server plans, from $19.7/day

Every plan gives your team a dedicated physical Mac mini, available in all five locations. Daily billing is ideal for testing a pipeline; monthly or quarterly billing suits always-on nightly builds. Check the console for current availability.

Port M4 Plus

Everyday parallel builds

Apple Silicon M4 · 24GB unified memory · 512GB SSD

$40.3/day

For everyday development, builds across multiple branches, and simulator testing. Set concurrency based on your own tests.

Rent Port M4 Plus

Billed in USD · Pay with USDT-TRC20, Visa, Mastercard, or Amex via Stripe. Available payment gateways depend on the response from the backend.

View the comparison table
5 data center locations

Choose a server near your team and code repository

Consider the locations of your code repository, dependency sources, and artifact destination—not just where developers are based. Prices are the same across locations for each plan. Latency ranges are estimates, not measurements of your connection or a guarantee.

SG

Singapore

Southeast AsiaTypical range: 20–50 ms

A good fit for teams in Southeast Asia and projects whose code, dependencies, and release workflows are mainly based there.

Choose Singapore → JP

Japan (Tokyo)

East AsiaTypical range: 30–60 ms

A good fit for teams in Japan and projects with repositories and dependency sources in East Asia that benefit from running builds nearby.

Choose Tokyo → KR

South Korea (Seoul)

Northeast AsiaTypical range: 30–50 ms

A good fit for teams in South Korea and workflows where code and artifacts are transferred mainly within the country.

Choose Seoul → HK

Hong Kong

South China & Southeast AsiaTypical range: 20–40 ms

A good fit for teams in South China. Test repository access, dependency downloads, and artifact transfers before choosing a location.

Choose Hong Kong → US-W

Western US

North America's West CoastTypical range: 25–35 ms

A good fit for teams on North America's West Coast and projects whose repositories, dependencies, or artifact destinations are mainly in the western US.

Choose Western US →
Build iOS apps without a Mac

Windows and Flutter teams: let a remote server build your ipa

How do you build iOS apps on Windows?

Keep writing, committing, and pushing code from Windows as usual. A runner on your dedicated server handles the build: it checks out your code, runs xcodebuild or fastlane gym to create an ipa, then sends the artifact back to your pipeline. You don't need to switch your development machine to a Mac.

Do you need a Mac to build Flutter apps for iOS?

You need a macOS build environment, but you don't need a Mac in your office. Install Flutter, Xcode, and your project dependencies on the server, then run flutter build ipa remotely and sign with your imported certificate and provisioning profile.

Signing requirements:You still need an active Apple Developer Program membership and must provide your own signing certificate, provisioning profile, and App Store Connect API Key. The server provides a build environment; it doesn't replace these release requirements.

Read the Windows and Flutter setup guide
  1. 1

    Push code from Windows

    Keep your existing development setup and push changes to your team's repository.

    git push origin main
  2. 2

    The server's runner picks up the job

    Register a self-hosted runner and use labels to route macOS jobs to the right server. Set a sensible concurrency limit for your team's tasks.

    runs-on: [self-hosted, macOS, osxport]
  3. 3

    Build and sign the ipa

    Import your certificate and provisioning profile, then configure signing. Store secrets in your CI system's secure variables, not in your repository.

    flutter build ipa --release
  4. 4

    Upload to TestFlight

    Configure automated uploads with your App Store Connect API Key, and return error logs and artifact locations to the pipeline.

    fastlane pilot upload
Example scenarios

Three teams, three pipelines

These illustrative first-person scenarios can help you choose a plan. They aren't named customer testimonials or performance test results.

Example scenario

Overnight builds for a five-person development team

2:00 AMnightly schedule

“We used to keep our build machine at the office, and a weekend power outage meant rescheduling jobs. Now nightly builds run on a Singapore server, with code and reports returned to our existing pipeline. No one on the team has to take turns looking after the machine.”

If your project needs to connect to devices on your company network, first check that remote network access meets your requirements.

Port M4 Base · $98.5/month

Example scenario

Flutter builds without a Mac

0local Macs

“Our whole team develops Flutter apps on Windows. After we push, the Tokyo server builds the ipa and uploads it to TestFlight. We manage the signing materials ourselves and check CI logs when a build fails—no more borrowing a Mac at the last minute.”

Remote builds don't replace local device testing. Plan separately for checks that require interacting with a physical device.

Port M4 Base · from $19.7/day

Example scenario

Parallel builds during release week

3branch pipelines to schedule

“We need builds for main, release, and hotfix. We run lightweight jobs in parallel and stagger memory-intensive tests. Our dedicated server handles our jobs only, so we don't have to wait for other customers to free up resources.”

Measure peak memory and archive times before setting concurrency. Three branches don't necessarily mean you need to run three full builds at once.

Port M4 Plus · $201.6/month

See more workflow examples
FAQ

Common questions before you get started

Not sure whether to rent a server? Get in touch with your team size, daily build count, archive time, and primary release locations. If you already have idle hardware and build infrequently, we'll tell you honestly when self-hosting is the better choice.

Get help choosing a setup
Is the server really available year-round?

The server runs at a data center and is online 365 days a year. Hardware issues can still affect tasks. Sign in to the console and open a support ticket with the server name, issue details, and recent actions so we can help investigate and move you to another server. The service schedule isn't a record of past incidents.

Can I install Homebrew and choose my Xcode version?

You can manage Homebrew, Xcode, and project dependencies to suit your pipeline. Before changing Xcode versions, check your SDK and project requirements and record tool versions in your build logs. Avoid having multiple jobs modify the same global environment at once.

When does monthly billing cost less than daily billing?

Compare the monthly price with the daily price. Port M4 Base is $19.7 per day or $98.5 per month. At list prices, five daily billing periods cost the same as one monthly period. If you expect to keep using the server, monthly billing may be a better fit. Check the order page for billing period dates and renewal terms.

Which payment methods do you accept?

All charges are in US dollars (USD). We accept USDT-TRC20, Visa, Mastercard, and Amex via Stripe only. Available payment gateways are shown at checkout. Check your order, amount, and payment network before paying.

Can several people share a server?

Yes. Multiple developers and pipelines within your team can use the same server; it isn't shared with other customers. Set appropriate access controls for build directories, signing materials, and runners, and limit concurrent compile and simulator tasks.

Build notes

Practical guides to choosing and setting up your build environment

From cost trade-offs to build environment setup, our articles cover the details teams often need to check so you can review them together before getting started.

DevOps & CI/CD

Testing Swift Union-Find on a Cloud Mac

Build a runnable Swift union-find implementation and cross-check connectivity and component counts against an independent graph traversal.

 DevOps & CI/CD

Testing iOS dependency graphs on a cloud Mac

Define deterministic dependency ordering with runnable Swift checks for missing nodes, duplicate edges, and tasks blocked by cycles.

 DevOps & CI/CD

Testing iOS Bloom Filters: False Positives and Snapshot Boundaries

Run a small Swift implementation to verify Bloom filter invariants, then test false positives and snapshot compatibility separately.
Next step

Try your pipeline for a day

Daily billing starts at $19.7/day for Port M4 Base. Connect your existing runner and test a clean build, an incremental build, and a full signed archive before switching to monthly or quarterly billing.

Try a server for a dayCompare the three plans

Example invoice · monthly

Server location
Tokyo
Port M4 Plus
$201.6
+1TB SSD
$12.9
Total · USD
$214.5

Example monthly total = $201.6 + $12.9, excluding other add-ons.

Payment: USDT-TRC20 or Visa, Mastercard, or Amex via Stripe.