Guides¶
One subject per page of the GRN.CLOUD console, each in three parts:
| Page | What it is for |
|---|---|
| Overview | What the thing is, how it fits together, and what cannot be changed later. Start here. |
| Step-by-step guide | Create, list, change and delete as YAML you can apply with oc or commit to Git. |
| Console walkthrough | The same four operations in the console, with screenshots. |
The console and the CLI are the same objects. The forms build the manifests shown in the
step-by-step guides, so anything created in the console can be read, edited or recreated
with oc, and anything applied with oc shows up in the console.
Every page in this section has a guided tour in the console
Open the page and click Start the tour beside the create button. The tour highlights each field as you go and checks your work at each step.
All guides¶
Type to narrow the list. The filter matches the name and the description, so key,
public IP or postgres each land on one row.
| Guide | Area | What you get |
|---|---|---|
| PostgreSQL | Databases | A database on your project's PostgreSQL server |
| MariaDB | Databases | A database on your project's MariaDB server |
| Redis | Databases | A private in-memory cache with its own storage |
| S3 buckets | Storage | Object storage, with credentials issued to your project |
| Volumes | Storage | Block and file storage attached to workloads |
| Load balancers | Networking | Publish a service outside the cluster |
| Firewalls | Networking | Restrict what may reach a service |
| Subnets | Networking | An isolated network, optionally reachable from outside |
| VM with a direct public IP | Networking | A virtual machine addressable from the internet without a load balancer |
| Fixed address for a pod or VM | Networking | One subnet address that survives pod restarts |
| Identity domains | Identity | The realm that holds your users and groups |
| Users | Identity | People who can sign in |
| Groups | Identity | Collections of users that permissions are granted to |
| Clients | Identity | Applications allowed to authenticate against a domain |
| Two ways to run models | AI | Whether to use the platform's gateway and serving, or run your own |
| LLM gateways | AI | One OpenAI-compatible endpoint for your team, with keys and budgets |
| Virtual keys | AI | Scoped access for a teammate, app or agent, with a spend limit |
| Model providers | AI | An upstream provider or your own endpoint, behind a model name |
| Self-hosted models | AI | Open-weight models served on EU GPUs |
| Workbenches | AI | A JupyterLab or VS Code environment beside your models |
| Coding agents | AI | OpenCode, Claude Code or Codex, running on your own gateway |
| MCP servers | AI | The tools an agent calls |
| Agent sandboxes | AI | Isolated execution of agent-generated code |
| Managed applications | Managed applications | GRN.CLOUD installs and upgrades the application, you change its settings |
| Invoices and payment | Account | Where invoices are, and how an overdue invoice pauses the account |
| Paused accounts and restore | Account | Pause after the last order ends, deletion 10 minutes later, restore from backup |
| The compliance check | Account | Sanctions screening, and what a possible or confirmed match means |
AI & machine learning describes how the AI pieces fit together.
Where these fit¶
The product pages say what each capability is and how it fits together. These guides say how to operate it.