Provide the full context at once

Tell us where the problem occurs

Pre-sales selection, technical support, node inquiries, and billing questions require different information. Choose a topic first, then add your device, node, toolchain, and reproducible evidence so we can prioritize your request based on completeness.

Generate support email Log in to submit a console ticket

Support email: support@numacs.com. For existing orders, use a console ticket first so we can link the relevant device records.

Structured email

Organize the key details into an email ready for troubleshooting

This form does not submit content to the website backend. After you click Generate, it opens a draft addressed to support@numacs.com in your system email app for your review and sending.

Support context

Basic information

Required fields define the scope of the issue. Enter an order number only for existing orders, device issues, or billing questions.

Issue type

Choose the option closest to your current goal.

Preferred node

If you have not chosen a node, select “Need a recommendation.”

Technical information template EVIDENCE / 06

Six essentials for a technical issue

  1. 01
    System and tool versions

    macOS, Xcode, runtime, package manager, and key dependency versions.

  2. 02
    Incident time

    Include your time zone and an approximate time window so we can correlate device and network records.

  3. 03
    Reproduction steps

    Start from a working state and list the commands, actions, and trigger conditions step by step.

  4. 04
    Expected and actual results

    Explain separately what should happen and what you currently observe.

  5. 05
    Key logs

    Keep error codes, process names, and surrounding context; redact sensitive data before submitting.

  6. 06
    Actions already tried

    Record the results after retries, cache clearing, network changes, or version rollbacks.

When to email us directly

For configuration advice, node selection, pre-purchase requirements, and general billing questions before ordering, email support@numacs.com. Put the issue type in the subject and include your target workload and preferred node.

Email the support team

When to submit a console ticket

For existing-order device status, remote connectivity, build failures, billing records, and recurring issues, log in and submit a console ticket first. Tickets link directly to your order and device context.

Log in to submit a console ticket

Redact before submitting

Logs can reproduce an issue, but must not expose credentials

Keep only the error codes, path structure, process names, and key context needed for diagnosis. Before sending, check the text, screenshots, command history, and configuration files line by line.

Do not submit

  • Login passwords, one-time codes, or recovery codes
  • SSH private keys, access tokens, or repository keys
  • Complete payment credentials or full card details
  • Unredacted certificates, signing files, or configuration contents
  • Complete logs containing customer data, source-code secrets, or personal information

Recommended to retain

  • Order number, node code, and device issue type
  • macOS, Xcode, and dependency versions
  • The shortest reliably reproducible steps
  • Error codes and the necessary logs immediately before and after the error
  • Actions tried and the actual result of each step

Node inquiry scope

Four available nodes—include your connection origin

Both NUMACS M4 Core and NUMACS M4 Plus are available in Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong. These catalog configurations can be ordered; actual availability is returned in real time by the console.

SG

Singapore

For connection-quality inquiries, provide your local network environment, target service address, test window, and diagnostic results.

Choose the Singapore node
JP

Japan (Tokyo)

Suitable for development workloads involving network paths to Japan and nearby regions. Include the target address and reproduction window for connection issues.

Choose the Japan (Tokyo) node
KR

South Korea (Seoul)

For network inquiries, distinguish the target paths used for remote desktop, SSH, code repositories, and dependency downloads.

Choose the South Korea (Seoul) node
HK

Hong Kong

For connection problems, include your local egress, target address, incident time, and consecutive test results rather than a single screenshot.

Choose the Hong Kong node
Configuration confirmed

Choose your model, term, node, and add-ons

NUMACS offers two Apple Silicon dedicated physical machines, both non-virtualized. Rent by the day, week, month, or quarter, then proceed directly to checkout once your workload is confirmed.

  • NUMACS M4 CoreM4 · 16GB · 256GB
  • NUMACS M4 PlusM4 · 24GB · 512GB
Rent a cloud Mac now View full pricing and configurations
Existing order

Manage device and support records in one console

After signing in, view order-linked information and submit tickets for device connectivity, build failures, or billing records. Include the node, incident time, and shortest reproduction steps in your ticket.

Device issueOrder number + node + time
Build failureTool version + steps + logs
Billing verificationTerm + payment type + records
Log in to manage devices

All prices are charged in US dollars (USD). We accept only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe). The actually available payment gateway is returned by the console.

Response expectations

Complete requests enter the actionable queue first

Handling order depends on issue impact and context completeness. Technical requests missing the order, node, incident time, or reproduction evidence must be completed before diagnosis can begin.

STEP 01

Define the issue scope

First identify whether this is pre-sales selection, a device technical issue, node connectivity, or billing verification, and check whether an order must be linked.

STEP 02

Verify reproducible evidence

Technical issues require the node, incident time, tool versions, reproduction steps, expected result, actual result, and redacted logs.

STEP 03

Enter the appropriate support path

Continue pre-sales and general inquiries by email; follow up on existing-order device, build, and billing issues through console tickets.

What to include for an urgent build failure

In your console ticket, provide the order number, node, failure start time, affected task, reliably reproducible steps, most recent successful time, and redacted logs. “Build failed” without evidence cannot be directly traced to the toolchain, resources, network, or script layer.

Prepare the context, then choose the right channel

Send pre-sales and general inquiries to support@numacs.com; for existing-order device, build, and billing issues, log in and submit a console ticket.

Send a support email Log in to submit a console ticket