Pre-sales recommendations, technical support, team purchasing, billing questions, and partnership inquiries each have a dedicated contact path. You can email support@pingmini.com ; if you already have an order or are using the service, sign in to the console and submit a ticket so we can link the instance and case history.
Classify your request first, then include information we can verify.
For pre-sales recommendations, team purchasing, billing details, and partnership inquiries. Include your use case, scale, timeline, and the outcome you need.
support@pingmini.comFor connection interruptions, failed builds, performance issues, order status, or problems with an active service. Tickets can link directly to your order and instance.
Submit a ticket in the console“It doesn’t work” or “We want to purchase” is usually not enough to start. These categories show the most useful input for each request and the contact path to use first.
Describe the Xcode projects, automation, model tests, or transcoding work you’ll run, how long you expect to use it continuously, and whether you need extra SSD capacity or Thunderbolt 5 daisy chaining.
Provide the order number, node, time, exact error, reproduction steps, and checks you’ve already performed. Use a console ticket first for active-service issues.
Specify how many tasks must run simultaneously, team roles, usage period, project handoff process, and whether work directories should be separated by node or project.
Provide the order number, payment type, billing items to verify, and the current page status. Do not include complete payment credentials or sensitive authentication details in the email.
Describe the development workflow, expected deliverables, participating teams, timeline, and technical boundaries you need PingMini to confirm. We’ll first assess whether the execution requirements are clear, then continue by email.
After you complete it, your system email client will open a draft. Your information is not sent to another online form service, and you can review and edit the message before sending.
Instead of “I need high performance,” share the project size, build frequency, concurrent task count, model size, asset resolution, and data volume to retain.
PingMini offers three fixed configurations across five nodes. If your workload boundaries are clear, go straight to configuration; the console will return live availability.
If you’re using the service, submit a console ticket first so we can link the order and instance. If you need to email us, include at least the fields below, but never send passwords, private keys, or complete authentication credentials.
Tickets preserve issue status, added records, and follow-up context, and make it easier to identify the related order and physical node.
Record whether the same action reproduces the issue consistently, and distinguish local networking, remote sessions, macOS toolchains, project dependencies, and automation scripts.
For CI/CD teams and multi-member development groups, the key issue is usually not a single configuration but how tasks queue, projects stay isolated, members hand off work, and which artifacts must be retained during the term.
Provide the number of builds, tests, archives, or inference tasks running simultaneously at peak, and note which tasks require an exclusive working directory.
Explain how development, testing, release, and operations members hand work off, whether directories should be separated by project, and who will migrate data before the term ends.
Distinguish a short release peak, a fixed iteration cycle, and long-running continuous builds. Include the expected start time, end condition, and any need for phased capacity increases.
Handling order depends on whether the issue affects an active service, whether the information is complete, and whether the order or reproduction can be confirmed. We do not promise unverifiable fixed response times.
Submit the order number, node, time, error details, and reproduction steps through a console ticket. Complete active-service reports enter technical review first.
For existing orders, use a console ticket first and specify what you want checked and the current page status. If you temporarily cannot access the console, email the necessary context from your support address.
Use the support email for the routine inquiry queue. We’ll first check whether the information is sufficient; if workload size, node, term, or expected outcome is missing, we’ll ask you to add it.
Add new evidence to the same email thread or ticket, keeping the order, node, and error context together. Avoid creating multiple unlinked requests for the same issue.
Pre-sales requests should receive a configuration or term recommendation; technical requests should receive the next check, required evidence, or a clear handling status.
Your email address, order details, node, error logs, and reproduction steps are used only to answer inquiries, deliver services, and troubleshoot issues. Remove project data unrelated to the failure and redact passwords, private keys, tokens, and complete authentication materials.
Three fixed configurations cover everyday development, continuous builds, and large-model inference. Use a console ticket for active-service issues; send a structured email for pre-sales and partnership questions.