Email us about plan consultations, batch workflow evaluations, and partnerships. For existing orders, node access, or billing-related issues, sign in to the console and submit a ticket so the full record stays linked to your order.
This form does not submit data to the website server. After you click the button, it organizes the subject and body locally and opens the mail app on your device. You can review and send it to support@nowmini.com.
Our target first response time for plan and partnership inquiries is within 24 business hours. For complex batch workflow evaluations, we first confirm any missing details and then provide the next items to verify.
Please provide your primary use case, team size, target region, estimated rental term, concurrency, and desired start date. For CI/CD, also include the number of runners, build frequency, cache size, and artifact return method.
Send a support emailAfter signing in to the console, open the ticket entry point from the relevant order or instance. This keeps the order ID, handling history, and follow-up information in the same context.
Sign in to the console to submit a ticketEnvironment versions, concurrency models, and data paths are more useful for evaluation than saying you need a more powerful machine. The five information groups below can be added directly to the technical requirements section of your email.
Specify the target macOS environment, Xcode version range, command-line tools, package management method, and whether you depend on fixed versions of Ruby, Node.js, Python, or build plugins.
Acceptance details One minimal build command and its expected resultDistinguish the number of builds running simultaneously, daily peak workload, and maximum runtime for a single task. For CI/CD, also explain who schedules the queue and whether failed tasks are retried automatically.
Acceptance details Peak concurrency, average runtime, and timeout limitsEstimate the size of source code, dependency caches, model files, media assets, and build artifacts. Explain which data must be retained long term and which can be deleted after a task ends.
Acceptance details Initial data volume, daily growth, and return methodExplain whether your team mainly uses SSH, a graphical interface, or automated runners, and provide the approximate network regions from which users connect. Do not include real keys or passwords in email.
Acceptance details Connection method, number of users, and access boundariesProvide the planned start date, environment validation duration, and production handoff date. If migrating from a local Mac, also explain how long the old environment must remain available in parallel and how you will determine that migration is complete.
Acceptance details Target date, validation window, and success criteriaNowMini M4 is currently available to order in 4 nodes: Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong. All listed combinations can be ordered; actual availability is based on the console’s real-time response.
Well suited to Southeast Asian teams, cross-region CI queues, and workflows spanning multiple Asian office time zones.
Well suited to iOS releases, continuous integration, remote development, and localization testing in the Japan time zone.
Well suited to development sessions, automated builds, test tasks, and MLX experimentation for teams in South Korea and Northeast Asia.
Well suited to collaborative teams across southern China and Southeast Asia, and workflows that centralize code, assets, and build artifacts.
Your team’s primary working time zone, the approximate region where users connect from, and whether the workload involves interactive remote development or unattended builds. The team will use this to identify the network and collaboration factors to verify when selecting a node.
Handle node connectivity, order status, subscription, and billing-related issues through a console ticket. A complete timeline and reproduction steps reduce back-and-forth and keep follow-up details in the same handling record.
Provide the order ID, node region, and relevant instance name shown in the console. Do not write only “my machine,” and do not expose complete credentials in public screenshots.
Include your time zone, first occurrence, most recent reproduction time, and whether the issue is continuous or appears only during a specific task stage.
Organize the steps as “action taken → result observed → expected result.” For connectivity issues, add the local network, access origin, and client type; for build issues, add the minimal command.
Keep error codes, timestamps, and necessary context. Remove passwords, private keys, access tokens, signing materials, and information identifying individuals or team members.
Orders support only USDT-TRC20 and Visa / Mastercard / Amex (via Stripe), and are billed exclusively in USD. The available payment gateway is determined by the real-time response from the backend. To purchase a new node, start the ordering process; for an existing order, sign in to manage it or submit a ticket.