Ask. Be specific.

The minimum is 1 day. Daily rentals work well for temporary signing, one-off archiving, build troubleshooting or short-term testing. “Daily” refers to the billing period, not per-minute build time. Stopping a task, disconnecting SSH or closing screen sharing won’t end your order. Check the rental period before payment, then confirm the expiry time in the console after delivery.

No, rentals don’t renew automatically. To keep using your Mac, log in to the console and renew before expiry, then check the updated expiry time. After expiry, the machine is reclaimed and its disk is securely erased. Don’t leave archives, signing materials or your only copy of source code until the last minute.

Don’t assume that payments for daily rentals will automatically count toward a weekly rental. To make a change, first check the renewal or billing-period options available for your order in the console. If you don’t see the option you need, submit a support ticket with your order number, current expiry time and requested extension. The available options and amount due will be confirmed for your order. Submitting a request doesn’t mean the billing period has changed.

If you expect to use the machine for 3 consecutive days, compare weekly pricing before ordering: 3 days at the daily rate for SDK Pack 16 comes to $19.6 × 3 , for a total of $58.8, which is already more than the weekly rate of $52.9.

The process from order placement and payment to physical machine setup usually takes about 4 minutes. This is a guide, not a guaranteed countdown. Check whether your order is “Awaiting payment,” “Payment confirmation” or “Initializing.” Connection details won’t appear until payment is confirmed, even if you’ve already submitted a transaction.

Log in to the console to check the current status and service notices. If the status remains unchanged, submit your order number and proof of payment. For connection steps, see the User Guide.

Both options are dedicated physical M4 Macs. These are listed prices for each rental period, not daily averages calculated from monthly pricing.

For short tasks, start with the daily rate. For longer rentals, compare weekly, monthly and quarterly pricing. Discounts for longer periods don’t apply retroactively to shorter periods you’ve already paid for.

Add-ons are priced separately. Check the selected period and quantity when you order. +1TB SSD and +2TB SSD are storage add-ons, not separate models. Thunderbolt 5 linking is priced per machine; check the order page for available configurations.

Estimate the space needed for your repositories, dependencies, simulators, DerivedData and archives before adding storage. More storage means more capacity, not more memory, and it doesn’t replace backing up your build artifacts.

The rental plans pagehas itemized billing examples. For SDK Pack 16 rented daily for 3 days with a +1TB SSD add-on: the machine costs $19.6 × 3 = $58.8, and the additional storage costs $2.7 × 3 = $8.1, for a total of $66.9 USD.

This example shows how charges are calculated; it isn’t a recommendation for the lowest price. For the same rental length, compare weekly pricing first. There are no setup fees or hidden bandwidth charges, but always check the billing period, quantity, add-ons and total due at checkout.

We accept USDT-TRC20 and Visa, Mastercard and Amex credit cards processed by Stripe. All orders are charged in US dollars (USD). Actual gateway availability is determined by the checkout system. Use the payment methods shown at checkout; never send payment to an address provided ad hoc in an email or chat.

Before sending USDT, check the network, recipient address and amount due. After a card payment, keep your receipt number for reconciliation.

The required confirmation count and payment recognition criteria are shown by the gateway on the payment page. We don’t list a fixed number here because it may change. A successful wallet transfer doesn’t mean your order is confirmed: network confirmations and gateway processing can take time.

First check that the network is TRC20 and that the address and amount match the payment page, then refresh your order status. If the transaction is confirmed on-chain but hasn’t appeared in your order, submit a console support ticket with your order number, transaction hash, amount and transfer time, including the time zone. Don’t send repeated transfers for the same order.

Whether 3D Secure is required depends on your card issuer and the payment flow; it isn’t the same for every transaction. If a verification page appears, follow its instructions. If verification fails or is declined, don’t assume you’ve paid just because you’ve been redirected to the site.

Check the payment status of your order in the console. If your bank shows a charge but the order hasn’t updated, submit your order number and Stripe receipt number, and include when it happened. Never send your full card number, security code or verification code in a support ticket or email.

Choose Singapore, Tokyo, Seoul or Hong Kong when placing your order. Both models are listed in all four locations; check the console for real-time availability.

First consider the network route from your workstation to the machine, then the paths used to transfer repositories, dependencies and build artifacts. Interactive screen sharing is more sensitive to network latency than background builds. A shorter geographic distance doesn’t guarantee a faster connection on every carrier. Don’t base a long-term environment choice on a single reference latency figure.

Switching locations isn’t an instant migration that preserves the current machine’s state. If you need to change locations, first submit a support ticket to confirm availability, how your order will be handled and whether you’ll need a new setup. Then plan the migration.

Before migrating, export repository changes, signing materials, environment settings and build artifacts. Set up the toolchain and verify the build on the destination machine before dealing with the original one. Don’t return the old machine before checking that your only data copy works. For preparation steps, see the Environment Migration Guide.

All locations run 365 days a year. During your rental, you can use a machine for background builds or CI tasks, but you’re responsible for managing processes, disk space, credential expiry and the order’s expiry time. Disconnecting from your local machine doesn’t necessarily stop background tasks, and a remote session isn’t a process supervisor.

Use a CI runner or suitable process manager to retain logs, and upload artifacts to storage you control. Troubleshoot service issues separately from errors in your own software. Include the last successful run time and a minimal reproduction in your support ticket.

No. MacSDK provides an entire dedicated physical Mac mini. During your rental, its CPU, GPU and memory aren’t shared with other customers. You get full access to the macOS GUI and command line to set up your own build, test and development environment.

Dedicated resources don’t mean every project takes the same amount of time. Dependency downloads, compiler caches, parallelism and project settings all affect results. To compare the two configurations and the workloads they suit, see the Plan Comparison.

You can install the Xcode versions you need, including beta versions compatible with your macOS environment. Before installing, check system requirements and available disk space. Use installation files you’re authorized to use, and allow time to verify beta releases.

If you have multiple versions installed, manage their application paths separately. Run xcode-select -p to check which developer directory your command-line tools use, then run xcodebuild -version to confirm the version in use. Complete first-launch licensing, component installation and signing checks before connecting the machine to unattended CI, so builds aren’t blocked by interactive prompts.

Yes. You get an administrator account, SSH and screen sharing. Find your machine’s address and credentials in the console after logging in; instance credentials aren’t displayed on public pages. You can install tools, configure build dependencies and adjust the environment for your project.

Before changing remote login, firewall or startup settings, make sure you have another way to connect. Don’t change every access rule at once from your only SSH session. For first-time connections, password changes and key setup, see the User Guide.

After return, the disk is securely erased before the machine is prepared for its next deployment. Don’t rely on a returned machine as a backup, or expect to recover files after erasure. For information about data handling related to your order, contact us through a console support ticket.

Before expiry, do at least four things: export and verify your build artifacts; commit or back up any unpushed code; unregister your CI runner; and revoke repository, signing and storage access tokens you no longer need. After copying your files, open them from the destination to check that they work—don’t rely on a transfer task showing “complete.”

Before enabling FileVault, submit a support ticket to confirm the startup unlock and remote recovery options for your location. Administrator access doesn’t guarantee that the machine can restart unattended with full-disk encryption enabled. FileVault startup unlock requirements may affect SSH, screen sharing and CI recovery.

We don’t recommend enabling FileVault until you’ve confirmed the remote unlock process. If you enable it after confirming, keep your recovery key somewhere safe. Don’t put it in ordinary logs or a public repository. FileVault doesn’t replace off-site backups or revoking tokens before you return the machine.

Use passphrase-protected ed25519 keys, with a separate key for each team member. Don’t share private keys. Check the host fingerprint on first connection. After adding your public key to the machine, open a new session to verify key-based login before considering whether to restrict password login.

Enable only the access methods you need. You can connect to screen sharing through an SSH tunnel rather than exposing additional services directly. Don’t ignore unexpected host fingerprint changes; first check whether the machine was redeployed or replaced. For full commands and first-time connection steps, see the User Guide.

Start with the minimum information needed: your order number, location, when the issue occurred and its time zone, the exact error message and steps you’ve already tried. Redact passwords, private keys, access tokens and sensitive business information from logs. Never send signing private keys or full payment card details.

For technical issues, first submit a support ticket in the console. If you can’t log in, email support@macsdk.com. If we need additional files or verification, follow the instructions in your ticket.