Your experience level

Three questions at first sign-in decide how your home page is laid out and how the assistant talks to you - and nothing else.

The first time you sign in, the console asks three short questions: how much you code, for how long, and how comfortable you are with networking. The answers place you in one of three levels. You can skip the questions, and you can change the level at any time.

The three levels

Level	Who it is for
Builder	You do not write code. You describe what you want and the assistant builds and publishes it.
Developer	You write code and deploy applications, databases and services.
Expert	You run infrastructure too: networks, clusters, Kubernetes.

How the answers decide: someone who does not code is a Builder, whatever else they answer. A developer who configures networks themselves is an Expert. Everyone else is a Developer - and so is anyone who skips the questions.

What the level changes

Two things.

Your home page. A Builder's home is a single box - What do you want to build? - with a few examples, their projects, and ready-made solutions. A Developer sees quick links to the deploy and data tools. An Expert sees every tool, infrastructure included.

How the assistant helps you. The AI Studio assistant and the DevOps Agent are told who they are talking to:

With a Builder they use plain words, make the technical choices themselves, and ask only about what you want the result to do or look like. They never ask you to run a command.
With a Developer they are concise and use normal technical vocabulary, and explain infrastructure choices in a sentence when one comes up.
With an Expert they skip the basics, name the trade-offs, give exact commands and configuration, and leave real architectural choices to you.

A change of level applies from your next message.

What it does not change

The menu is the same for everyone. Every section of the console - Integrations and Kubernetes included - is in the sidebar whatever your level. The level never hides a page.

It is not a permission. What you are allowed to do is decided by your role and your permission groups, described in Roles, permission groups and access. The level only decides what is put in front of you first.

Changing it

Open your Profile and find Experience level. Pick another level; the home page updates right away. The level belongs to you, not to the organization: each member has their own.

Guide

What ISOGrid is — A cloud platform built in Algeria, for teams who want to ship without running servers.

Getting started — From an account to something running on the internet.

Your experience level — Three questions at first sign-in decide how your home page is laid out and how the assistant talks to you - and nothing else.

Deploying an application — From a repository to a running address, and what happens at each step.

Git repositories — Connecting GitHub or GitLab, deciding who in the organization may build from your repositories, and what happens when you leave.

Addresses and domains — The address every application gets, using your own name instead, and what breaks when DNS is wrong.

Databases — Ordering one, what each arrangement survives, and why replication is not a backup.

Private clusters without lock-in — What runs on your machines is standard Docker Swarm or Kubernetes, and it keeps running if you leave.

Supabase — A complete backend on PostgreSQL in one deployment - what you get, which database to put behind it, and where your keys are.

Roles, permission groups and access — The three layers that decide what each member may do, the groups every organization starts with, and the rules that stop anyone climbing.

The AI Studio sandbox — The workspace behind every Studio project - starting, pausing and restarting it, what happens when it is left unused, and how your files come back.

The DevOps Agent and your code — How the agent deploys repositories you already have, what it asks before acting, and when the code it cloned is deleted.

When things go wrong — The failures you are most likely to meet, what each one actually means, and what to do.

Command line

Installing the CLI — One command on Linux, macOS or Windows, a checksum on every download, and how to update or remove it.

Command reference — Every command group, what it does, and where each one is explained in full.

Automating applications — Create, configure, deploy and remove applications from a terminal or a script, with every flag explained.

Deploying from CI/CD — Deploy on every push from GitHub Actions or GitLab CI/CD, with a narrow credential and a job that fails when the deployment does.

Repositories, groups and access — Decide who can build from a repository, manage permission groups and read who holds what, from the terminal.

Policy

Availability and support — What the platform commits to, what it does not, and how to reach a person.

Acceptable use — What you may run, what you may not, and what happens if a line is crossed.

Privacy — What personal data ISOGrid keeps, why, who else sees it, how long it is kept, and how to delete your account.