Start with your needs, not a rental

Tell us about your CI workflow.
We’ll help you decide if hosting makes sense.

Office Macs, shared runners and dedicated hosting each have their place. Tell us how often you build, how much concurrency you need and what hardware your team currently maintains. We’ll help you decide whether to keep your current setup or host a dedicated physical Mac mini.

Rent a build node Draft an enquiry email

Still weighing your options? Get in touch first. For help with an existing node, sign in to the portal and open a support ticket.

No procurement brief needed

Four details that tell us more than “we need faster builds”

Rough estimates are fine; you don’t need to run a full performance test first. Try to separate time spent waiting for a runner from time spent building—the two call for different solutions.

  1. 01

    Team and workflow

    How many people commit code? Does one release owner package builds manually, or does every merge trigger a build? Also let us know whether your current Mac is used for day-to-day development, so we don’t mistake team size for hardware requirements.

  2. 02

    Build volume and concurrency

    How many builds do you run on a typical day and on release days? Note the time for a representative build, the longest queue and whether you run multiple branches or simulator tests at once. Peak load often matters more than the daily average when choosing a setup.

  3. 03

    Project and toolchain

    Tell us whether you build native apps, use Flutter or React Native, and which versions of Xcode, fastlane and CI tools you use. Include any large dependencies, multiple targets, UI tests or archive caching.

  4. 04

    Team and release regions

    Along with your team’s location, tell us where your code repository, dependency sources and artifact destinations are. The closest build node isn’t always the best choice; it helps to consider the entire data path.

Please don’t send repository access tokens, passwords, signing keys or full certificates by email. Project size and a description of the error are usually enough to start the conversation.

Pre-sales and support take different routes

Still comparing? Email us. Already running a node? Open a ticket.

Both options connect you with our service team. Email is best for discussing your options; tickets keep questions tied to your order, node and follow-up troubleshooting.

For customers with an active node

Keep node issues together in the portal

Use a ticket for connection issues, node operation, renewals, billing or questions about an existing order. Sign in to the portal, open the support area and create a ticket with the relevant order or node ID.

Include the time and time zone, steps to reproduce, expected result and actual result. Add any follow-up details to the same ticket so everything stays in one place.

Replies and follow-up: Check your ticket for replies and requests for more information. Resolution times vary depending on the issue, whether a node needs replacing and the nature of a billing question.

Sign in and open a ticket
Before choosing a plan

Use email to weigh a move out of the office

Ask us to compare self-hosting with managed hosting, choose among three plans, assess multi-node needs or clarify payment and billing. Include the four details above in one email to make it easier to get to a useful answer.

Email us at support@osxport.com. Use the tool below to draft your message, then send it from your own email account.

Replies and follow-up: We’ll reply to the address you write from. We may ask follow-up questions about your workflow; nodes are online year-round, but that doesn’t mean email replies have a fixed, minute-by-minute response time.

Draft an enquiry

Turn your workflow details into an email

This tool only drafts an email. Your answers are used to create a draft on this page; they aren’t sent or uploaded through this form. Review and send the draft from your own email account.

Also tell us who maintains your current build machine.
If you have timings, separate queue time from build time.
Native apps, React Native and simulator testing are useful to mention too.
Haven’t chosen a node region yet? We can start by looking at the network path.
Don’t include passwords, tokens, private keys, full card numbers or other sensitive credentials.

Fill in the required fields to create a draft. This page won’t send an email for you.

Choose for your data flow, not just map distance

Pick the closest fit from five regions

Start with your team’s location, then compare the paths for fetching code, downloading dependencies and uploading artifacts. These are pointers, not latency measurements for your network. Test with your own CI workflow to see what works best.

Singapore

A good starting point for teams in Southeast Asia. If your code and dependencies are nearby too, it’s easier to assess the full path from checkout to artifact upload.

Choose Singapore

Japan (Tokyo)

Consider this region if your team or main workflow is in Japan. Test dependency downloads and artifact delivery as well as remote access; don’t judge by the feel of the remote connection alone.

Choose Tokyo

South Korea (Seoul)

Worth comparing for teams in South Korea and Northeast Asia. If build dependencies come from other regions, track download times too, so you can tell whether the node is really the bottleneck.

Choose Seoul

Hong Kong

Consider it for teams in southern China and Southeast Asia. Remote access, source sync and artifact transfer use different paths; measure each one separately rather than relying on a single overall impression.

Choose Hong Kong

US West

A starting point for teams on the US West Coast or workflows whose code and artifacts are routed through the region. Test it first, then compare the time needed for cross-region collaboration.

Choose US West

All three plans are available in these five regions. Check the portal for live availability. When you get in touch, just tell us your preferred region and why you chose it.

Sometimes the right advice is “don’t move”

Make sure a dedicated node is the right fix

A dedicated physical machine is reserved for one customer, so you won’t compete with other customers for build resources. It won’t eliminate waits within your own pipeline or fix project configuration and code-signing errors.

Occasional builds and a spare Mac

If you package builds only once or twice a month, already have an idle machine and can look after its power and network, keeping it in-house may cost less. Check how much you actually use it; there’s no need to move just to get “on the cloud.”

What to discuss: Whether the cost and upkeep of your current machine are actually affecting releases.

Spiky jobs that need on-demand capacity

If jobs are occasional, environments can be recreated each time and a shared queue works for you, shared runners may be a better fit. A dedicated node’s concurrency is still limited by its hardware and job scheduling.

What to discuss: How long peak demand lasts and whether keeping caches matters more than scaling up and down.

Expecting a remote node to replace all local testing

Windows and Flutter teams can move iOS builds to a cloud Mac, but local device interaction, peripherals and final on-device checks still need to be handled separately. Remote build access doesn’t replace a complete local testing setup.

What to discuss: How to split responsibilities between packaging, simulator tests and real-device testing.

On the other hand, if you build after frequent merges, need to keep caches and no longer want to maintain office hardware, a dedicated hosted node is worth trying. Nodes are online 365 days a year, and the whole machine is reserved for you. Your team stays in control of how jobs are scheduled.

Know what you’ll be billed for

Ask about billing periods, add-ons and settlement—not payment credentials

All orders are billed in USD. We accept USDT-TRC20 and Visa / Mastercard / Amex through Stripe. Available payment gateways are confirmed by the backend at checkout.

Before ordering: check what’s on the bill

Tell us the plan, billing period (daily, weekly, monthly or quarterly), number of nodes and whether you need SSD expansion or Thunderbolt 5 daisy-chaining. Check the plan price and add-ons separately so you don’t mistake an expansion for part of the base configuration.

The order page shows the itemised price and amount due. Don’t include your full card number or security code in an email.

Already paid? Keep a record with the order

For payment status, renewals or billing questions, open a support ticket in the portal first. Include the order or invoice ID, the time it happened and any message shown on the page. If needed to reconcile a USDT-TRC20 payment, you can provide the transaction hash—but never your wallet’s private key.

If you can’t sign in yet, email us with a description of the login issue and the related order ID. Once access is restored, continue the conversation in a support ticket.

Try your workflow and see if it’s a fit

Plans start at $19.7/day. Test with your own code, dependencies and artifacts before committing to a permanent setup. Still have questions? Start by drafting an enquiry email.

Rent a build node by the day Draft an enquiry first