OpsMac://contact — Live agent connected
contact://human — Just two channels

Who to talk to: email for pre-sales, ticket for support

> Connecting you to a human… pick a window

No bot menus here, no hold music. Everything runs through exactly two channels: for anything before you've placed an order — picking a tier, pricing, which node to choose — email support@opsmac.com. For anything after you're up and running — technical issues, billing, configuration changes — log into the console and open a ticket. Both channels are answered directly by the engineers who maintain these dedicated physical machines, so the more specific you are, the better your odds of solving it in one reply.

channels://3-windows

Three windows, three jobs

Pick the right one and skip the "can you give me your order number first?" round-trip.

Pre-Sales Inbox

No account needed: which tier to pick, which of the four nodes to choose, how daily billing works, bulk orders, and partnership inquiries.

  • Addresssupport@opsmac.com
  • What to includeOne line on what you're building + your budget cycle (day/week/month/quarter), e.g. "Unity builds, about 5 days a month"
  • ResponseFirst reply within 24 hours, staffed 365 days a year
Send an email →

Support Ticket Portal

Everything for existing orders: SSH or VNC won't connect, need a macOS reinstall, billing questions, adding an SSD, or changing your plan.

  • PathConsole → Tickets → New Ticket, automatically linked to your order and device
  • ResponseFirst reply within 12 hours for general issues; connection/boot issues go into the priority queue
  • CreditConfirmed node-side outages get credited for the downtime
Open the console →

Self-Serve Guides

First SSH connection, blank VNC screen, a runner that dropped offline, reinstalling the OS — our guides have step-by-step checklists for these, and most get solved in under 5 minutes on your own.

  • CoversFirst boot, changing credentials, remote desktop, CI setup and troubleshooting
  • GlossaryPlain-language explanations of terms like dedicated physical node, not a VM
  • AvailabilityAvailable any time, no waiting on anyone
Check the guides first →
New Ticket — Recommended Fields

Fill in these four fields and cut your back-and-forth in half

To troubleshoot a dedicated physical machine, engineers first need to know exactly which device on which node. Give us all four up front and most issues get resolved in the very first reply.

FieldWhat to enterWhy we need it
NodeSingapore / Japan (Tokyo) / Korea (Seoul) / Hong Kong — pick oneNetwork issues are diagnosed per node; the wrong one means checking the wrong data center
PlanM4 Home (16GB/256GB) or M4 Pro Workstation (64GB/2TB)The two tiers have different storage and memory troubleshooting paths
Order IDCopy it from your Orders page in the console, e.g. QV-2026-0118-0342Points us straight to the allocation record for your machine
DescriptionWhat's happening + when it started (with time zone) + what you've already triedTells us whether it's a node-side fault or a local config issue, and whether it goes into the priority queue

Here's what a well-written ticket looks like:

ticket — example
Node: Japan (Tokyo)
Plan: M4 Home (16GB / 256GB)
Order ID: QV-2026-0118-0342
Issue: SSH connections have been timing out since 14:20 today (Tokyo time); VNC screen sharing works fine
Tried: Switched networks, still times out; console shows the device online; sshd is running when checked over VNC
Expected: Please check whether port 22 is open on the node side

> Same goes for pre-sales emails: what you're using it for + your budget cycle + roughly where you're located — three lines is enough. Paste screenshots directly into the ticket, no need to zip them up.

presales://faq

The four questions we get asked most before you buy

Check here first — if it doesn't cover your case, emailing us will get you an answer faster than you'd think.

How do I choose between the M4 Home and M4 Pro Workstation?
For Xcode builds, day-to-day CI runners, and fastlane app packaging, the M4 Home (16GB/256GB, from $19.4/day) is usually plenty. If you're loading mid-sized models into unified memory for MLX / llama.cpp inference, or running multiple builds in parallel, go with the M4 Pro Workstation (64GB/2TB, from $59.9/day). If storage is your only bottleneck, there's no need to move up a tier — adding a +1TB SSD ($2.8/day) or +2TB SSD ($5.6/day) is more cost-effective. If you're unsure, just describe your project in your email and we'll recommend a config based on your workload.
Can I try it for a day before committing?
Yes — that's the whole point of billing by the day. The M4 Home runs $19.4/day, and it's about 4 minutes from payment to credentials in hand, so you can run your full build pipeline the same day. If you don't renew, it just expires — no silent charges. Once it's working well for you, switch to weekly ($52.4) or monthly ($97.1) billing, with quarterly ($264.1) offering the best value. Since every node runs the same config at the same price, feel free to try a different one during your trial to compare.
How much does latency vary between Singapore, Tokyo, Seoul, and Hong Kong?
All four nodes run identical hardware at identical prices — the only variable is the network path between you and the node. Rule of thumb: if your team is mostly in East Asia, go with Tokyo or Seoul; in Southeast Asia, pick Singapore; for most Greater China use cases, Hong Kong tends to have the shortest path. VNC desktop sessions are latency-sensitive, while SSH and CI jobs are much more forgiving. The most reliable way to decide is to spin up a day on each: test ping, SSH responsiveness, and VNC smoothness — a day's cost is a small price to find your best-fit node.
I want to upgrade from M4 Home to M4 Pro Workstation mid-rental. Who do I contact?
Open a ticket in the console specifying the tier you want, and we'll prorate the difference for your remaining term and schedule the migration — you'll need to back up your own data beforehand (only you can access the data on a dedicated physical machine). See the billing breakdown and pricing FAQ on the pricing page for full billing logic and expiration rules.
Support Hours — Response Time Policy

What time is it, and how fast will someone answer?

Our support team is staffed across the Tokyo and Singapore time zones, covering the full working day in both UTC+9 and UTC+8, 365 days a year — and our nodes run year-round too, with no scheduled downtime.

TOKYO · UTC+9 --:-- Online
SINGAPORE · UTC+8 --:-- Online
ChannelCoversFirst response
Pre-sales emailPlan selection, pricing, node recommendations, partnerships≤ 24 hours
Console ticket · GeneralBilling questions, add-ons, usage questions≤ 12 hours
Console ticket · OutageSSH/VNC won't connect, device won't bootPriority queue

> These times refer to the first human reply. Confirmed node-side outages are credited for the actual downtime — see our Terms of Service for details.

Payment inquiry scope: This service only accepts USDT-TRC20 and Visa / Mastercard / Amex (via Stripe), all billed in US dollars (USD). Payment-related emails and tickets are handled only for these two channels — if an on-chain transfer hasn't arrived, include the transaction hash; if a card charge failed, include the charge time and card network (never send us your card number), and we'll reconcile it from there. Requests to add other payment methods are outside our support scope.

USDTTRC20 VISA AMEX
portal://self-service

Already have a machine? Most things don't need a human

Renewals, adding a 1TB/2TB SSD or a Thunderbolt 5 daisy chain, resetting login credentials, reinstalling macOS, downloading past invoices — these are all instant, self-serve actions in the console, faster than opening a ticket. Save the two channels above for what actually needs a person.

Open the self-service console → Rent a cloud Mac now