Accounts & projects

Create an account

Sign up through the GRN.CLOUD portal, or contact sales if you need a private cloud, a committed plan or an invoice-based agreement.

Scaffold status

The exact sign-up flow, verification steps and plan selection screens are being captured. This page describes the model; the click-by-click walkthrough follows.

Create a project

A project is a namespace with quotas, RBAC and network policy attached. Create one per environment — myapp-dev, myapp-staging, myapp-prod — rather than sharing one project across environments. Blast radius, quotas and access all follow the project boundary.

Web consoleCLIoc

1. Open the console and select Projects → Create project.
2. Give it a name, a display name and a description.
3. Choose the cluster and the plan it should draw quota from.

oc new-project myapp-dev \
  --display-name="My App (dev)" \
  --description="Development environment"

oc create namespace myapp-dev
oc label namespace myapp-dev environment=dev

Invite your team

Access is granted with RBAC roles bound inside a project. Every grant is a reviewable Kubernetes object, not a setting buried in a console.

Role	What it allows
view	Read objects in the project
edit	Create and modify workloads, but not change access
admin	Full control of the project, including granting access

oc adm policy add-role-to-user edit alice@example.com -n myapp-dev

To review who has access:

oc get rolebindings -n myapp-dev -o wide

Quotas and limits

Each project carries a ResourceQuota (how much the project may consume in total) and LimitRange defaults (what an individual pod gets if it does not ask). Check them before you debug a scheduling failure:

oc describe quota -n myapp-dev
oc describe limitrange -n myapp-dev

Next

Access the platform →