Email works best for
Send a blank email
Pre-order configuration questions
Use it for plan and region selection, storage expansions, Thunderbolt 5 linking requirements, rental terms and enterprise purchasing details.
Two ways to reach us
Get your request to the right team from the start
Send presales questions and enterprise requirements to our support inbox. For connection, hardware status or billing issues on an existing order, sign in to the console and open a ticket so your order number, instance and support history stay linked.
Within 1 business day
Target for the first presales email reply
Within 4 business hours
Target to confirm an existing-order ticket
REQUEST ROUTING
Choose a request type first
A
Presales planning
Use case, concurrency, region, term and storage needs
B
Technical support
Connection failures, instance status, storage and build environments
C
Enterprise & CI/CD
Runner count, build frequency, access boundaries and delivery dates
D
Billing questions
Order totals, payment records, billing periods and add-ons
For existing orders, open a new request under “Tickets” in the console. Email is best for configuration questions and enterprise discussions before you place an order.
Presales email draft
Describe the workload once—we’ll recommend from our three-plan catalog
This tool only assembles the email in your browser; no information is submitted to the website. When you’re done, it opens your system email app so you can review and send the message to support@zonemini.com.
Tickets work best for
Open a console ticket
Existing orders tied to an instance
Use tickets for connection issues, instance status, hardware checks, disk mounts, payment records and order configuration checks. Include the order number and redacted logs.
Enterprise & CI/CD
Frame requirements around queues, access and delivery dates
Enterprise setups are still built from the three plans currently available; we do not add out-of-catalog specifications. We use task duration, concurrent queues and memory pressure to determine whether you need a persistent single-host environment or a multi-host Runner setup.
TEAM BUILD SHEET
6 data points to include in your email
01
Runner count and labels
List always-on Runners, peak concurrency and the label rules used by project, branch or release task.
02
Build frequency and duration
Share workload on a typical business day and release day, plus approximate time for testing, archiving and export.
03
Repository and team location
Choose among Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong and US East based on proximity to your repository and main collaborators.
04
Access boundaries
Explain who maintains the Runner, who can read build logs, who handles signing, and how access is revoked when someone leaves or changes teams.
05
Cache and storage growth
Estimate growth for dependency caches, archived artifacts, model files or media assets to determine whether included storage or an SSD add-on is appropriate.
06
Delivery date and acceptance criteria
Specify when you want to start running workloads and whether acceptance is based on the first successful archive, Runner connection or completed inference task.
ZoneMini M4 Core
M4 · 16GB · 256GB
For automated builds of a single project, periodic testing and low-concurrency archiving.
ZoneMini M4 Plus
M4 · 24GB · 512GB
For dependency caching across multiple projects, persistent Runners and longer development pipelines.
ZoneMini M4 Pro
M4 Pro · 64GB · 2TB
For large-model inference, high-load parallel tasks and larger local working sets.
Ticket template
Give support enough detail to start troubleshooting in round one
For an existing order, sign in to the console and create a request under “Tickets”. Put the issue type and order number in the subject, then provide facts in the order below. Avoid sending only “cannot connect” or “build failed”.
SUPPORT REQUEST
Copy-ready issue structure
Issue type: Connection / Build / Storage / Billing
Order number:
Plan:
Region:
Date, time and time zone:
Expected result:
Actual result:
Steps to reproduce:
1.
2.
3.
Error code or key logs:
Troubleshooting completed:
Impact:Order and plan details
Include the order number and identify the actual plan as ZoneMini M4 Core, ZoneMini M4 Plus or ZoneMini M4 Pro.
Region and system time
Specify Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong or US East, along with the date, time and time zone when the issue occurred.
Shortest reproduction path
Start from a known point and list each action, command and observed result. Say whether the issue is consistently reproducible and what conditions applied during the last successful run.
Redacted logs
Keep timestamps, error codes, tool versions and required paths. Replace usernames, repository addresses, tokens, certificate contents and passwords with clear redaction markers.
Support scope
Separate host, connection and toolchain issues first
Different issues call for different evidence. We handle matters involving ZoneMini hosts, orders and connection paths, and can help identify which layer of a third-party development tool is involved.
Configuration advice
We recommend a plan, region and storage add-on from the three-plan catalog based on memory pressure, working-set size, concurrent tasks and rental term.
- Contact channel
- Support email
- First reply target
- Within 1 business day
Connection assistance
We check instance status, access addresses, SSH ports, local networks, screen-sharing settings and firewall rules, then narrow the issue using redacted logs.
- Contact channel
- Console ticket
- Confirmation target
- Within 4 business hours
Hardware and storage status
We check the operating status of your rented physical host, local storage, attached SSD mounts and Thunderbolt 5 linking details. All hosts operate normally 365 days a year.
- Contact channel
- Console ticket
- Submit
- Order number, region, time and logs
Third-party development tools
We can help determine whether Xcode, dependency managers, CI Runners or build scripts are affected by the host environment. Tool behavior, platform interfaces and review outcomes remain the responsibility of their respective providers.
- Contact channel
- Ticket for existing orders
- Recommended details
- Version, command, error code and minimal reproduction
| Issue type | Preferred channel | Required details | Starting point |
|---|---|---|---|
| Presales planning | support@zonemini.com | Use case, concurrency, region, term, storage and start date | Compare the three plans with task duration |
| Enterprise CI/CD | support@zonemini.com | Runner count, build frequency, repository location and access boundaries | Plan a single-host or multi-host setup |
| Connection and instance | Console ticket | Order number, plan, region, time of occurrence and redacted logs | Check the instance and access path |
| Billing and payment | Console ticket | Order number, billing period, add-ons and payment record summary | Check order configuration and payment status |
Data and payment notes
Send only what we need to handle the request
Keep contact requests focused on configuration, order and troubleshooting facts. Payment methods and settlement currency are fixed; use the checklist below before submitting.
Share the minimum
Presales email only needs your use case, workload size, region, term, storage and delivery date. Technical tickets only need order details, reproduction steps and redacted logs.
- Do not send SSH private keys or full passwords
- Do not send repository tokens or signing certificate contents
- Redact usernames, paths and addresses in logs first
- Keep attachments to the smallest set needed to reproduce the issue
All orders settle in USD
All orders are settled in USD. Only the following two payment options are supported; the console determines which payment gateway is currently available.
- USDT-TRC20
- Visa / Mastercard / Amex (via Stripe)
Keep order issues linked
Submit tickets for existing orders through the console so requests stay linked to the plan, region, billing period and payment records. Do not put a fictional order number for an order that has not been created in a presales email.
- Presales and enterprise requests: Support email
- Connection and hardware status: Console ticket
- Billing and payment checks: Console ticket
- Commercial and compliance documents: Support email
Next step
Existing order? Open a ticket. Not ordered yet? Send an email.
Include the order number, plan, region, time of occurrence and redacted logs in a ticket. For presales email, include your use case, concurrency, term, storage needs and preferred start date.