Orbitarix FAQ

Orbitarix is a software platform used to deploy, supervise, and control workers from a central dashboard. It combines monitoring, task execution, alerts, and optional Telegram integration around an agent-based outbound-only architecture.

Orbitarix is aimed at operators who need to manage one or more remote machines from a single interface, especially in mining-oriented environments where monitoring, deployment, and remote actions must stay simple and centralized.

Yes. Orbitarix is an independent platform with its own architecture, interface, deployment logic, Telegram integration, and worker-based billing model. It is presented as its own product, built around Orbitarix workflows and operating choices.

Orbitarix is designed primarily for mining operations and CPU/GPU worker supervision. Some technical building blocks are broader, but the current dashboard, alerts, deployment flows, and pricing are clearly optimized for mining-related use cases.

Yes. The Orbitarix dashboard is designed to be usable on desktop and on phone. You can review worker status, follow alerts, check metrics, and access the main functions from a responsive web interface, without depending only on Telegram.

Each worker runs an authenticated agent on the supervised machine. That agent communicates with the Orbitarix server, reports telemetry, receives queued tasks, and executes authorized actions according to the configuration and available permissions on the machine.

No in the normal Orbitarix model. The platform is built around an outbound-only approach in which workers communicate toward the server, which helps reduce direct network exposure of supervised machines.

Yes. Orbitarix is built to centralize multiple workers inside the same workspace so you can supervise status, telemetry, tasks, and remote actions from one dashboard.

The worker is shown as offline once it stops communicating within the expected time window. Monitoring becomes stale, live actions may no longer execute, and the machine must reconnect before normal command flow resumes.

Yes. The current product and pricing model distinguish worker categories such as CPU-only and GPU-based setups, with billing aligned to the category associated with each worker.

Orbitarix provides installation commands and deployment flows from the dashboard. Depending on your context, you can use the generated outbound install link or a manual fallback flow to place the agent on the machine and register it in the workspace.

Yes. The platform includes multi-worker deployment workflows so the same operational rollout can be repeated across several machines without onboarding each worker manually from scratch.

Depending on the worker and available telemetry, Orbitarix can surface metrics such as status, hashrate, temperatures, fan speeds, power-related signals, load, and other operational indicators used to monitor machine health.

Orbitarix exposes operational feedback such as task status, audit information, and workflow-level diagnostics. Some environments also use live shell access for deeper investigation. The exact depth of visible logs depends on what the worker returns and the rights available on that machine.

Yes. Orbitarix is designed to speed up large-scale worker deployment. Depending on your network, your access, and how the machines are prepared, it is possible to launch the deployment of dozens of workers in less than a minute from a centralized interface, without configuring each machine manually one by one.

Telegram is primarily used to receive important operational alerts, for example when a temperature goes above a threshold, when a machine goes offline, comes back online, or restarts. The integration can also offer selected quick actions, but it complements the dashboard: the main interface remains Orbitarix, usable both on desktop and on phone.

No. Telegram is not the main Orbitarix interface. The dashboard remains the full control center, with a responsive interface that stays usable on mobile. Telegram is mainly an alert channel and an operational shortcut for certain situations.

Telegram control depends on a configured bot, authorized chat targets, and the same backend rules that govern remote actions in the workspace. It improves operational convenience, but like any remote control channel it should be configured carefully and kept under your control.

Yes. Telegram is optional. You can use Orbitarix only from the web dashboard, including from a phone, without enabling Telegram integration.

Billing is based on workers registered and active in your workspace. Each worker is billed according to the category associated with it, for example CPU, 1 GPU, 2 GPU, and so on, in line with the pricing grid currently displayed.

No. Orbitarix is not presented as a single flat subscription that includes a fixed number of machines. The pricing model scales according to the number of managed workers and the category linked to each worker.

The price depends on the worker category shown in the pricing grid. In practice, a CPU-only worker, a 1 GPU worker, and a higher-density GPU worker are not billed at the same level.

Deleting a worker removes it from your managed fleet for future billing cycles, according to the current billing state of your account. It does not cancel amounts that have already been validly invoiced or become due.

In case of non-payment, Orbitarix may suspend all or part of the service until the account is regularized, in accordance with the Terms of Use.

Orbitarix is designed to rely on secured web and API endpoints, authenticated agents, and encrypted transport in transit when deployed with the expected TLS setup. As with any infrastructure product, security also depends on your own server, endpoint, and account hygiene.

Orbitarix should not be used to store wallet recovery phrases or private keys. Users remain responsible for keeping highly sensitive secrets outside the platform unless a dedicated and clearly documented mechanism exists for a specific purpose.

You remain responsible for the machines, power, cooling, overclocking, scripts, wallets, network exposure, operating system, and operational decisions associated with your infrastructure.

Depending on the enabled features, Orbitarix may process account data, session and security data, worker identifiers, telemetry, task history, logs, deployment events, settings, and optional Telegram configuration or notification metadata, as described in the Privacy Policy.

No. Orbitarix is a supervision and control platform. It does not guarantee profitability, revenue, business outcome, or investment performance. You remain responsible for your hardware choices, wallet configuration, miner setup, and operational decisions.

No. Orbitarix does not guarantee hashrate, uptime, energy efficiency, deployment success, or uninterrupted availability. The platform helps you supervise and operate machines, but it is not a performance warranty.

No. Orbitarix does not take responsibility for hardware damage, overheating, instability, data loss, or operational interruption caused by your machines, configuration, environment, or usage choices, subject to the limits stated in the Terms of Use and applicable law.

No universal compatibility can be guaranteed. Some features may vary depending on the operating system, drivers, GPU stack, permissions, custom configuration, or hardware specifics of the supervised machine.