Resources Overview

A resource is anything you actually run - a server, a storage volume, a transit port, an addon. Every resource lives inside a project, every project lives inside an organization, and every charge against a resource flows up to that organization's invoice.

• Resources are organized by category in the sidebar under each project - Cloud, GPU Cloud, Metal, Clusters, Storage, Transit. A category only appears under a project if that project has at least one resource of that type.
• The Order new action under each project is the universal entry point for adding any kind of resource. See Creating a Resource.
• Most resource actions are role-gated. Owners and admins can do everything; technical (member) can manage resources in projects they're scoped to; read-only can view but not change.

Every resource is reached through the sidebar:

1. The active organization sits at the top of the sidebar.

2. Projects under that org are listed in the Projects section.

3. Expanding a project shows its resource categories.

4. Clicking a category opens the list of resources of that type.

5. Clicking a row opens the resource detail page.

The path is always: organization > project > category > resource. If you ever land somewhere and aren't sure what you're looking at, follow the breadcrumb at the top of the page back to the org.

Virtual private servers (VPS), and Virtual dedicated servers (VDS) running on Synteq's hypervisors. 

Use Cloud for general-purpose workloads - web servers, databases, application servers, control planes, anything that doesn't need a whole physical machine or a GPU. They deploy in seconds.

• Order: Creating a Resource
• Manage power: Managing power options
• Reinstall: Reinstalling the OS
• Resize: Resizing a Resource

VPS with a GPU attached - usually for AI / ML inference, fine-tuning, or rendering. The host hardware is the same idea as Cloud, but with a passthrough GPU.

Use GPU Cloud when you need GPU compute but don't want to manage a whole physical server. You pay only for the time the instance exists.

Dedicated baremetal and instant metal servers.

Use Metal for workloads that need raw performance.

Clusters are coming soon.

You don't "order a cluster" directly; you order cluster-eligible dedicated servers and group them. Each node is still a Metal resource underneath.

Block storage volumes that attach to one of your servers.

Volumes are sized in TB and billed monthly. They live in a region, so they can only attach to a server in the same region.

IP transit ports - uplink ports for customers running their own network. Includes BGP services, ASN registration, and prefix announcement. Quoted in committed Mbps with burst.

Use Transit when you need to announce your own IP space, run BGP with us, or peer with the wider internet.

Click any resource row and you land on its detail page. The layout is consistent across categories:

• Hero card at the top: name, status badge, IP addresses, region, plan summary.

• Tab row across the top: Overview, Usage Graphs, Network, BGP, Power, Settings, Storage. Tabs vary slightly by category.

• Main panel below the tabs: content for the selected tab.

• Action buttons in the top-right of the hero 

The seven tabs:

• Overview: quick summary of spec, resize, billing, and recent activity.
• Power: start, stop, reboot, force-stop. 
• Storage: disks, volumes, attach / detach / resize. 
• Network: interfaces, IPv4 / IPv6, rDNS, bandwidth graphs. 
• Settings: hostname, notes, reinstall, root password reset, rescue mode.
• Activity: per-resource action log (power events, reinstalls, rebuilds).
• Billing: line items from past invoices for this specific resource.

Every resource has a status badge on its detail page:

• Provisioning: being set up. The portal polls in the background; this lasts seconds to a few minutes depending on category.
• Running / Active: up and billable.
• Stopped: powered off but the resource still exists and is still billable.
• Suspended: powered off due to billing or abuse. Not running but still billable.
• Pending cancellation: cancelled and scheduled to be reclaimed at the end of the current cycle.
• Awaiting crypto payment: the order was placed with a crypto payment and is waiting for blockchain confirmation to provision. Provisioning starts the moment the payment confirms. 

Status flows are documented per-category, but the pattern is consistent.

The four most common things people do with resources, mapped to where:

Two things to remember:

• Resources can't be moved between organizations. They belong to whichever org owned them at creation. To "move" one, cancel and re-order in the target org.
• Resources can be moved between projects within the same org. Useful if you reorganize how you carve up your hosting. 

Billing always flows up: a resource invoices to its project's org, regardless of which project it sits in.

You can cancel any resource you own. The cancellation flow charges through the rest of the current cycle and stops auto-renewal - the resource keeps running until the cycle ends, then is reclaimed.

The full walkthrough is Cancelling a service. Related:

• What happens to your data - data lifecycle after cancellation.
• Refund Eligibility - when you can ask for a partial refund instead.

• Cloud and GPU Cloud: no hard per-org cap on instance count, but stock varies by location.
• Metal: no per-org cap; subject to availability of the spec you want at the location you want.
• Storage: volumes attach 1-to-1 to servers in the same region.
• Transit: quoted per-port; BGP sessions per ASN.

If you're hitting a limit, the order flow will tell you and route you to the Support ticket form.