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.

Some organizations cannot hand a cloud provider a key to their servers, and cannot let their secrets leave their network. The ISOGrid Nomad agent is for them. You run it on your own cluster; it connects to ISOGrid, never the other way round, and executes the deployments you order from the console.

What stays with you

Your machines. ISOGrid holds no SSH key and registers no node. The agent is the only thing that touches your cluster, and it runs on a manager you control.
Your secrets. ISOGrid knows the names of your secrets, never their values. You enter the values in the agent's own console on your network, and the agent keeps them in your HashiCorp Vault or OpenBao.
Your logs. Build and container logs stay on your network and are read in the agent's console only.
Your web tier. You keep your own NGINX or HAProxy. The platform writes no web server configuration and allocates no port on an agent cluster.

The agent's code is public, so your team can read exactly what it does before running it: github.com/ISOGrid-by-SkyVault/isogrid-nomad-agent.

How it connects

The agent opens one outbound connection to ISOGrid over HTTPS, the same address and certificate as this console, and proves who it is with the certificate issued for your cluster. ISOGrid accepts it only from the addresses you declared. Every order ISOGrid sends is signed with a key that belongs to your organization; the agent verifies the signature before it looks at the order, and refuses anything else.

Setting it up

Open Integrations and choose ISOGrid Nomad agent.
Enter the public addresses your agents connect from, one per line, and enable the integration.
Add a cluster: a name and whether it runs Docker Swarm or Kubernetes. The price per cluster is shown before you confirm.
Download the cluster's bundle: five files, including the certificate and the signing key the agent needs.
On a Swarm manager, unzip the bundle in a directory and run the installer:

curl -fsSL https://raw.githubusercontent.com/ISOGrid-by-SkyVault/isogrid-nomad-agent/main/install.sh -o install.sh
sudo bash install.sh

The installer asks which networks the agent joins, where its console listens, where the bundle is, and how to reach your Vault. Once the agent connects, the cluster shows as connected on the Integrations page.

If the certificate is lost

Use New certificate on the cluster: the old bundle stops working and the new one must be installed. Removing a cluster from ISOGrid changes nothing on your machines.

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.

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.