Skip to main content

Aquila

Single control plane for multi-node vLLM inference. Point-and-click deployments, an OpenAI-compatible gateway, warm caching, live GPU monitoring, and a full deployment lifecycle — without Kubernetes or a managed platform.

Quick start

uv venv && source .venv/bin/activate
uv pip install aquila

Host (management server):

aquila host up --host-ip 0.0.0.0 --host-frontend-port 5173 --host-discover-port 11400

Client (each GPU node):

aquila client up --host-ip <host-ip> --host-discover-port 11400

Open http://<host-ip>:5173 — client nodes appear within seconds. Add --service for persistent systemd services.

Features

  • Deploy and manage models across GPU nodes via Docker or rootless Podman — each runs in the official vllm/vllm-openai container with a specific version, nightly build, or commit hash.
  • OpenAI-compatible gateway (/v1) with stable URLs across node moves, API key auth with per-deployment scoping, and auto-expiring snippet keys.
  • Warm cache — pause idle models to RAM and resume on demand; LRU auto-eviction frees GPU VRAM while keeping weights ready for near-instant restart.
  • Local checkpoints and LoRA adapters — upload from the browser (streamed) or pull from a URL directly onto a node.
  • Live monitoring — GPU utilization, disk usage, deployment status, per-deployment usage metrics, and 48-hour metric history charts.
  • Usage tracking — lifetime tokens, request counts, and average prefill/generation speeds from vLLM's own metrics.
  • Reproducibility manifests — export model, HF revision, seed, vLLM version, image digest, and full config per deployment.
  • Notifications — Slack/webhook alerts when deployments become ready, fail, or are about to expire.
  • Per-GPU maintenance — cordon individual GPUs while the rest of the node keeps serving; optionally drain affected deployments.
  • Extra packages and plugins — install pip packages and upload vLLM plugins per deployment via cached derived images.
  • Reverse proxy support — deploy behind nginx at any sub-path with --base-path.

Best for

  • Research labs and university clusters
  • Teams sharing GPUs across projects
  • Self-hosted multi-model inference

Supported platforms

  • Python 3.10–3.14, Node.js ≥ 23 (host only)
  • Ubuntu 22.04 and 24.04
  • NVIDIA GPUs (H100, A100, L40, RTX 4090, DGX Spark)

Full documentation

Metadata

Release files for aquila 0.3.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for aquila 0.3.5
File Size Uploaded
aquila-0.3.5.tar.gz 1.5 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for aquila 0.3.5
File Interpreter ABI Platform
aquila-0.3.5-py3-none-any.whl Python 3 none any Details

Total release size: 1.8 MB

Release files / aquila-0.3.5.tar.gz

Download URL aquila-0.3.5.tar.gz
Size 1.5 MB
Tags Source
SHA-256 checksum
How to use checksums
a12f5db6d9a063ba70f54c1e031689460eac3a584384b195d63e8011a8985516
BLAKE2b-256 checksum
How to use checksums
595532f47207ce73fb29c42c3bd8b132d8c620dedef2f7a2422436184b8079d3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 24, 2026.

Transparency log

Release files / aquila-0.3.5-py3-none-any.whl

Download URL aquila-0.3.5-py3-none-any.whl
Size 263.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
87c1976b2ea4d702d70d1f61a37ef9309070bd4c702cbc67ce8c3e9d07eba8f1
BLAKE2b-256 checksum
How to use checksums
c53ca708db3da5c5c1fe7df758f60eed097b187667e1afeca601602dfa36aee2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 24, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.3.5 This release

2 release files

0.3.4

2 release files

0.3.3

2 release files

0.3.2

2 release files

0.3.1

2 release files

0.3.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page