Build planning · Node support

Tell us about your build pipeline

Still choosing a setup? Email our support team with details of your build workload. Already have a node? Sign in to the portal to submit and track a ticket. Start with what’s blocked, then include the information we need to reproduce it.

Rent a physical Mac node Sign in to submit a ticket

We don’t offer live chat or guarantee a fixed response time. Email replies continue in the same thread; track ticket updates in the portal.

New to VMFly? Email us

For pre-sales advice, team purchasing needs, or help accessing your account. Share your goals and constraints—instead of simply asking us to “recommend a machine”—so we can make a useful recommendation.

support@vmfly.com

Have an order? Link a ticket

For node issues, renewals, and payment checks. Sign in to the portal, open the support area, and include the relevant order or node ID. Add any follow-up details to the same ticket.

Open a portal ticket
Prepare your request

Make it easy for us to pick up

Fill in the form and select “Draft email.” Your email app will open a draft. This won’t create a ticket in the portal or send an email automatically—you’ll need to review and send it from your email app.

If you have an account, use the email address registered to it so we can verify your details. The sender address will be set by your email app.
What do you need help with? (required)
Copy the ID from the portal. Leave this blank if you haven’t rented a node yet. Don’t include passwords or private keys.
A useful format is “goal → what happens → what you’ve tried → relevant logs.” Remove passwords, private keys, access tokens, and full card details first.

The draft will be addressed to support@vmfly.com. The form assembles the email on your device; it doesn’t upload your entries to a server.

Avoid unnecessary back-and-forth

Include the right details

The three checklists below cover node selection, troubleshooting, and payments. Include only what’s relevant to your issue, and keep sensitive credentials out of emails and logs.

Choose a node for your build workload

Start with your daily build count and peak hours, then describe project size, whether you use Unity, and your team’s location. You can describe project size by the number of targets, dependency installation time, and cache usage.

  • Tell us what each pipeline run includes—compilation, UI tests, or archiving—and whether these steps need to run concurrently.
  • Glide M4: Apple Silicon M4, 16GB memory, 256GB SSD. A starting point for everyday CI on a single app.
  • Cruise M4 Pro: Apple Silicon M4 Pro, 64GB memory, 2TB SSD. Consider it for projects with multiple targets or Unity.
  • Describe your typical workflow: frequent remote debugging, unattended builds, or transferring large build artifacts.

Available locations: Singapore, Tokyo, Seoul, and Hong Kong. Check the portal for current combinations and availability.

Pinpoint where the issue occurs

Include the node ID and the time the issue occurred, including the time zone. Then tell us whether you can’t connect to the node, the runner isn’t picking up jobs, or xcodebuild starts but fails during execution.

  • Describe the expected and actual results, and include the exact error message—not just “build failed.”
  • Share the first error from xcodebuild or the runner, along with the surrounding context, rather than only the final exit code.
  • Include your Xcode version, the command you ran, and any changes made since the last successful build.
  • List what you’ve already tried, especially restarting the runner, switching toolchains, or clearing caches.

For existing nodes, use the portal ticket system. If you can’t sign in, email us from your registered address and explain the issue. Never send your account password.

Help us check a payment

Include your order ID, selected billing period, payment method, and payment time. For renewals, SSD add-ons, or Thunderbolt 5 daisy-chain issues, also specify the node and what you’d like changed.

  • We accept USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). All payments are settled in US dollars (USD).
  • For USDT payments, include the transaction hash, network, and transfer amount.
  • For card payments, include the payment result or error message. Don’t share your full card number, security code, or verification code.
  • If the payment page doesn’t show a successful result, keep your order and payment records. Don’t retry the same payment until you’ve checked them.

Available payment gateways are determined by the response from our backend. Use payment records for verification; the email draft prompt on this page does not confirm payment.

Keep the conversation with the node’s ticket

Already have an account? Sign in to the portal to submit and track a ticket. Add logs or reply in the existing ticket to keep all the troubleshooting context together.

Open the portal Email support