ISOGrid documentation

How ISOGrid works: deploying applications, managed databases, domains, access control, the command line and the platform's commitments.

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.
• Your own cluster with the Nomad agent — Deploy from the ISOGrid console on a Docker Swarm or Kubernetes you run yourself, without giving ISOGrid any access to your machines or your secrets.
• 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.

Tutorials

• Your first deployment — A repository to a working address, with the mistakes pointed out before you make them.

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.