
Assign project owners without changing organization roles
Give a teammate responsibility for a Polyaxon project while keeping their organization role and your team's access restrictions in place.
The latest guides, tutorials, and product updates.

Give a teammate responsibility for a Polyaxon project while keeping their organization role and your team's access restrictions in place.

Restrict a Kubernetes notebook workspace PVC to one Pod, mount it in a Polyaxon service, and hand access to a replacement notebook.

Generate predictions from a JSONL prompt file with vLLM, schedule the work on a Polyaxon GPU agent, and save the results as run artifacts.

Limit aggregate GPU requests with ResourceQuota, supply CPU and memory defaults, and align Polyaxon resource profiles and queues with namespace budgets.

Use completed trial results to guide hyperparameter choices with native TPE, run GPU training trials, and compare validation loss in Polyaxon.

Use Polyaxon's organization and team APIs to inspect GPU workloads by agent, count model versions, and calculate job failure rates across projects.

Deploy two task-specific LoRA adapters over one Qwen base model, select them by name, and measure quality and shared GPU capacity with Polyaxon.

Start a background process, save its execution ID, reconnect to status and logs, and distinguish command limits from the lifetime of a Polyaxon sandbox.

Use an ordered Polyaxon mapping for a curated list of experiments, control concurrency, and distinguish scheduling order from dependencies and completion order.

Scope Polyaxon Python clients and CLI commands to a team, review runs across its projects, and keep explicit project targets and saved defaults clear.

Reuse Polyaxon's termination specification to bound notebook and inference service lifetimes, stop idle services, and distinguish inactivity from ongoing work.