Support for distributed teams

Submit a ticket for technical issues;
email us about purchases

For a build in progress, include the machine and order details. For a new machine, tell us your team’s time zones and workload. Choose the right channel for each.

Purchasing inquiries: support@pushmac.com. For issues with an active machine, please continue in the same ticket.

Choose the right channel

Pre-sales and team purchasing use the same email address. Existing customers can use console tickets to link instances, invoices, and support history.

Active instances and orders

For SSH connection failures, VNC login issues, Xcode environment changes, payment checks, or renewals, sign in to the console and submit a ticket. Include the related instance or order.

Add logs, updates, and replies to the original ticket to avoid repeating details across email threads.

First rental and model selection

If you haven’t started a machine yet, email us with your app type, build frequency, cache size, and team time zones. A single-app daily CI workflow and parallel archiving across multiple targets have different resource needs.

Include your preferred model and rental period. If you’re unsure about anything, just mark it “please advise.”

Multiple machines and long-term plans

Send bulk purchase inquiries to the same support email. For each node, list the number of machines, intended use, planned start date, and billing period. This helps coordinate handoffs across regions and renewals for each machine.

Each Mac mini is a dedicated physical machine. Your team manages task distribution and CI queues across machines.

How to check replies and progress

Email replies go to the address you wrote from. Check ticket replies and progress in the console. We don’t publish a standard first-response time. If builds are affected, state the scope, whether a fallback node is available, and the work hours you need restored in the first part of your ticket. This helps us assess priority.

Keep both time zones in sync in one record

Include the node and the time of the issue

Your team’s location may differ from the machine’s. “The connection failed last night” isn’t enough to locate the logs. Use an absolute time with its UTC offset so colleagues in Asia-Pacific and North America can follow the same record.

  1. 01

    Name the machine’s node

    Use the node name shown in the console and include the instance ID. The five nodes are Singapore, Tokyo, Seoul, Hong Kong, and the US East Coast. Don’t just write “overseas machine” or name a teammate’s city.

  2. 02

    Include the UTC offset

    Record the time and time zone, for example, “09:30 local time, UTC+08:00.” North American teams should include the UTC offset in effect at the time, rather than an abbreviation that may be affected by daylight saving time.

  3. 03

    Describe the impact and how to reproduce it

    Specify whether the issue involves SSH, VNC, dependency downloads, or a build command. Include the exact error, whether everyone is affected, and the last successful stage. Say what happened when you retried; don’t send only a screenshot of the failure.

Suggested format for the first part of a ticket

“Node: as shown in the console; instance: ID; time: local time and UTC offset; issue: SSH connects, but archiving fails; impact: release pipeline paused; troubleshooting: reran once, same error.”

For payment issues, include the order ID. For USDT-TRC20, provide the transaction hash; for card payments, include the billing record from the console. Never send your full card number or security code.

What to check before you rent

Confirm what you need before deciding whether to email us. Both models in the catalog are available by the day; check the console for real-time availability.

Run your own build by the day first

You can rent by the day, but this is not a free trial. Push M4 S has an M4 chip, 16GB memory, and a 256GB SSD for $19.2/day. Push M4 L has an M4 chip, 24GB memory, and a 512GB SSD for $39.7/day. Test with your own repository, recording the first-build time and the time after caching, before choosing a longer rental period.

Run machines across Asia-Pacific and North America

You can rent multiple machines in different locations, such as one in Singapore and another on the US East Coast. Both models are available in Singapore, Tokyo, Seoul, Hong Kong, and the US East Coast. Choose a node and rental period for each machine. They don’t share disks or combine into one runner automatically, so plan code sync, task labels, and queues yourself.

USD pricing and payment methods

We accept USDT-TRC20 and Visa / Mastercard / Amex via Stripe. All payments are in US dollars (USD). Available payment gateways are confirmed by the backend. To check a payment against an order, sign in to the console and submit a ticket with the order ID and relevant payment record.

Choose a model for your build workload

The 16GB model is a good starting point for daily CI on a single app. The 24GB model is better suited to parallel archiving across multiple targets and mixed Flutter / React Native builds. In your email, include the number of parallel jobs, dependency size, cache usage, and simulator usage. +1TB SSD and +2TB SSD are storage add-ons, not separate base models.

Prepare your purchase email

Put your purchase requirements in one email

Fill this out to generate an email you can review, then open your email app to send it to support@pushmac.com. This page won’t send the email or submit your information to the site’s server.

Enter your main working hours and UTC offset. Distributed teams can enter two sets.
Preferred node (select one)
Preferred model (select one)
Only include information needed for your purchase. Don’t enter connection passwords, private keys, certificates, or full payment details.

Review the email before sending. Opening your email app does not send it.

Ready to go? Start your rental

Two dedicated physical Mac mini models, available by the day. Choose a node and rental period, place your order, and get machine delivery details in the console.