Hikube key concepts
This page presents what you need to know to use Hikube: how your resources are organized, how you manage them, and what the platform handles for you.
The Hikube console
All day-to-day operations take place in the web console: https://console.hikube.cloud. You sign in with your Hikube account (single sign-on). From the console, you create, modify and delete your resources, check their status and estimated cost, and retrieve connection details.
A project's side menu groups the services:
| Section | Services |
|---|---|
| Dashboard | Project overview, quotas, costs, recent resources |
| Infrastructure | VM Instances, Disks, S3 Buckets, Kubernetes, Networking |
| DB & Messaging | PostgreSQL, MariaDB, MongoDB, Redis, RabbitMQ |
Organization and projects
Organization
The organization represents your company. Hidora creates it when your account is opened; it groups your users and your projects. If you have access to several organizations, you switch between them from the profile menu (Change organization). The Organization ID is shown in My Account, with a copy button.
Project
A project is an isolated space within the organization. Each resource (VM, disk, cluster, database…) belongs to a single project. A project provides:
- isolation: a project's resources cannot see those of other projects;
- quotas: CPU, memory and storage limits that cap the project's consumption;
- cost tracking: the project dashboard estimates the monthly cost of its resources.
A common practice is to create one project per environment (production, staging, development) or per team.
The project settings show its Project ID, with a copy button: give it to support for any request about this project. If the platform could not apply the last change to a project, the project carries an Error badge in the project selector.
In previous versions of the documentation, a project was called a tenant.
Quotas
A project's quotas are set when it is created (Quotas step of the wizard) and can then be changed in the project settings. The creation wizards show the impact of each new resource on the quota before creating it. A quota cannot be lowered below what the project already consumes: free up resources first.
Deleting a project
Deleting a project (project settings → Danger Zone → Delete this project) permanently destroys all of its resources: VMs, Kubernetes clusters, databases, disks, S3 buckets and networks. This action is restricted to project or organization administrators.
Managed services
Hikube operates the underlying infrastructure of each service for you: high availability, storage replication across datacenters, platform updates. You choose the size and configuration; the platform provisions and maintains.
| Family | Services |
|---|---|
| Compute | Virtual machines, GPU |
| Containers | Managed Kubernetes |
| Storage | Disks, S3 buckets |
| Networking | VPCs and subnets |
| Databases | PostgreSQL, MariaDB, MongoDB, Redis |
| Messaging | RabbitMQ |
Sovereignty and availability
- Data in Switzerland: all data remains hosted on Swiss territory.
- Three datacenters: replicated storage is spread across three geographically separate datacenters.
- Network isolation: each project has its own network perimeter.
Next steps
- Quick start: create your first project and your first cluster
- Virtual machines: deploy a Linux or Windows VM
- FAQ: frequently asked questions