I want something running in five minutes
Use Quick Deploy. Pick a prepared template, choose a runtime, run it. No image to name, no resources to size.
AiQu documentation
Pick a Docker image, choose how much GPU you need, and queue it.
AiQu finds a node, runs your container, and bills you for the time it used.
Find your way in
Section titled “Find your way in”Using AiQuQueue jobs, mount storage, expose ports, open a terminal, and keep an eye on what your tokens are paying for.
Administering a tenantUsers, groups, projects, queues, storage and nodes inside one tenant. What a tenant admin can change, and what they cannot.
Operating the platformTenants, global nodes and queues, system-wide settings. The superadmin view across every tenant.
ReferenceRoles and permissions, job states, limits, the REST API, and the glossary.
Start with the question you actually have
Section titled “Start with the question you actually have”I have my own image
Create a job from any image on Docker Hub or a registry your tenant has configured.
My data keeps disappearing
A container’s filesystem is discarded when the job ends. Anything you want to keep has to live on a mounted folder.
My job will not start
Usually the queue, the tokens, or a permission. Troubleshooting goes through them in order.
How the pieces fit
Section titled “How the pieces fit”A job is one or more containers, called services, that AiQu schedules onto a node. You submit the job to a queue; the queue decides which nodes are eligible and what resources you may ask for. While the job runs it spends tokens, either yours or a project’s. Everything you want to survive the job goes on a storage bucket that you mount into the container.
That is the whole model. Core concepts says it more carefully, and the glossary defines each word on its own.