Gigakube wiki
How to use gigakube.ch to run your cloud: from your first login to servers, networking, DNS, API keys and AI agents.
What Gigakube is
Gigakube is a Swiss cloud run by Daiko Lab SA. It gives you:
- Linux virtual machines (servers), with public IPv4 addresses and, where the network has it, IPv6;
- a firewall on every server, closed until you open a port;
- a private network for each project, separate from every other customer's;
- DNS: zones and records on our nameservers (
ns1.gk01.ch,ns2.gk01.ch) or on your Cloudflare account, plus reverse DNS for your public addresses; - domain registration;
- managed Kubernetes: we run the control plane and it is free, you only pay for the nodes;
- attack protection you can see: the attacks on your public addresses, and what was done about them;
- API keys and an MCP server, to drive everything from a program or from an AI agent such as Claude;
- a prepaid account (top-up credit) or, by agreement, end-of-month billing.
Today there is one zone, Zurich (code gk01). Varese (gk02) is on the way. Your cloud lives in one zone: choosing the zone in the panel will come with the second one.
One principle holds everywhere: anything you can do in the panel you can also do with the API and with the matching MCP tool. The panel has no secret powers.
How this wiki is organised
Menu, button and field names are written exactly as they appear in the panel (for example New server, Switch it on). Each page has a part for everyone and, where useful, a For developers section with the API calls and the MCP tools.
Getting started
- Getting started: signing up, first login, profile and billing details, switching on the cloud.
- Projects and people: what projects are for, roles, inviting someone.
- The panel and its three modes: AI, Normal, Nerd, and how to ask the assistant for things.
The cloud
- Virtual machines: creating, starting and stopping, console, SSH, deleting.
- Networking and public addresses: private network, IPv4 and IPv6, getting out to the internet, L2 networks.
- Firewall: opening and closing ports, from where, the special rules.
- Kubernetes: clusters, node pools, kubeconfig.
- Importing a VM: bringing in machines from VMware, Proxmox or a file.
- Attack protection: what you see when one of your addresses is attacked.
Names and domains
- DNS: zones, records, nameservers to give your registrar, Cloudflare.
- Reverse DNS (PTR): the name of your public addresses, for example for a mail server.
- Domains: searching, registering, renewing, transferring.
Access, programs and agents
- SSH keys.
- API keys and the JSON-RPC API: creating a key, roles, revoking, calling every service with
curl. - MCP: connecting Claude and other agents.
- Plans and change requests: seeing what will change beforehand, and letting an agent ask without acting.
Money and good practice
- Billing and invoices: prepaid, top-ups, end of month, VAT, usage, prices.
- Security and good practice.
- FAQ and help.
Short glossary
| Term | What it means |
|---|---|
| Project | The container for everything: servers, network, DNS zones, clusters. Every account has a default one; you can create more and invite other people into them. In the code and the API it is called tenant. |
| Zone | A data center with everything it needs to run on its own. Today gk01 (Zurich). Not to be confused with a DNS zone. |
| Switching on the cloud | The first time, in each project, you switch on the cloud module: the project gets its private network and its quota. It costs nothing. |
| Server / VM / machine | A virtual machine. The panel says server. |
| Size | How many vCPUs and how much memory the server has, with a name like s-2-4 (2 vCPU, 4 GB). |
| Image (Operating system) | The operating system the server starts with, for example ubuntu-24.04. |
| System disk | The server's disk. It is deleted together with the server. |
| Public address | The IPv4 address (and, if there is one, IPv6) reachable from the internet, routed straight to the server: no NAT, no port forwarding. |
| Private network | The project's network: servers in the same project talk to each other on it, and no other customer can see it. |
| NAT gateway | The way out to the internet for servers without a public address, when the project has one. |
| Firewall / open ports | The rules that say what may come into a server. On Gigakube the firewall belongs to the server: there is no separate "security group" to create and attach. Everything going out is always allowed. |
| Quota | The most a project can use (servers, vCPUs, memory, disk, addresses). You can see it in the panel. |
| Role | What a person or a key can do in a project: Can view (viewer), Can edit (operator), Can manage (admin), and the owner. |
| API key | A gk_… credential for a program or an agent: it is valid in one project only, with one role. |
| MCP | Model Context Protocol: the way an AI agent (for example Claude) uses Gigakube's tools. |
| Plan (dry run) | The answer to "what would happen if…": what would be created, changed or destroyed, and the quota afterwards. It changes nothing. |
| Change request | What a change becomes when it is asked for with a key that requires approval: it waits for a yes from a person in the project. |
| Job | A long-running operation (creating a server, a cluster): it has a state, queued, running, succeeded, failed. |
| DNS zone | The set of records for a domain, for example example.ch. |
| Nameserver | The servers that answer for a DNS zone. Ours are ns1.gk01.ch and ns2.gk01.ch. |
| Reverse DNS (PTR) | The name returned to anyone asking "what is this address called?". |
| Kubeconfig | The file kubectl uses to get into a Kubernetes cluster, with full rights. |