Skip to main content
Compute with Hivenet provides on-demand GPU and CPU resources for AI, software development, rendering, data processing, and other workloads that need more capacity than a local machine can provide. You choose an available location, hardware configuration, software environment, and connection method. Compute prepares the resource and charges for eligible usage while it runs.

​
How Compute is organized

Every Compute account operates within an organization. The organization is the shared boundary for:
  • People and their roles
  • Instances and other Compute resources
  • Prepaid credits
  • Billing and transaction history
An organization has one Owner and can also include Admins and Members.
  • The Owner controls credits, payment methods, auto top-up, people, and ownership.
  • Admins help manage people and organization settings and can view organization billing.
  • Members can create and use organization resources but cannot manage people or billing.
See How organizations work in Compute for the complete role comparison.

​
What you can create

Compute supports two main instance types.

​
Containers

Containers provide prepared software environments for application, development, AI, and inference workloads. You can use an available template or create a custom template for repeated configurations.

​
Virtual machines

Virtual machines provide a full operating system for workloads that need broader system-level control. Both types can use GPU or CPU-only configurations when those resources are available in the selected location.

​
How instance creation works

The creation flow guides you through the main choices:
  1. Confirm the organization you are using.
  2. Choose a container or virtual machine.
  3. Select an available location.
  4. Choose GPU or vCPU-only resources and a suitable size.
  5. Select a template or operating system.
  6. Configure SSH, HTTPS, TCP, UDP, or Jupyter access as needed.
  7. Name the instance and review the estimated cost.
  8. Create it and wait for the status to reach Running.
Charging begins after the instance is running. See Launch and connect to your first Compute instance for detailed instructions.

​
How billing works

Compute uses prepaid credits held in the organization balance. Running resources draw from that shared balance, and eligible Compute usage is charged per second. Only the organization Owner can add credits, manage payment methods, or configure auto top-up. Admins can review organization spending, while Members cannot see organization-wide billing.
If an Admin or Member reaches the creation review with insufficient credits, the organization Owner must add more before the instance can be launched.
See Billing information for payment, role, and transaction-history details.

​
How you access a workload

Connection options depend on what you enable during creation:
  • SSH for terminal access
  • HTTPS for secure browser or API access
  • TCP or UDP for applications that require those protocols
  • Jupyter Notebook for browser-based notebook workflows when available
Some connection settings cannot be changed after creation, so review them before launching.

​
Stop, start, and terminate

Use the instance lifecycle controls according to what you need next:
  • Stop pauses compute charges and preserves the instance temporarily for a later start.
  • Start returns a stopped instance to service when suitable capacity is available.
  • Terminate permanently deletes the instance and its local data.
Save important data before terminating an instance. Terminated data cannot be recovered from the instance.

​
Distributed infrastructure

Hivenet runs Compute across distributed infrastructure rather than relying on one central facility. Available locations and configurations depend on the capacity connected to the platform. You choose from the resources currently offered in the console. The creation screen shows availability, technical specifications, and active pricing before you launch.

​
Before you start

You’ll need:
  • A Compute account
  • Access to an organization
  • Enough organization credits for the selected resource
  • An SSH public key when you want terminal access
  • A plan for saving any data you cannot afford to lose
Continue with the Compute quickstart when you’re ready to create your first instance.