NeMo Platform
Make the agents you ship faster, more accurate, and safer.
NeMo Platform brings NVIDIA NeMo libraries together under one CLI, Python SDK, and web UI. Hardening, evaluation, and tuning for the agents you put in production.
What's here today
- Secure agents. Guardrails (content safety, jailbreak detection, PII redaction), Auditor (red-teaming via garak), Anonymizer (PII handling for training data).
- Evaluate agents. LLM-as-judge, deterministic, agentic, and RAG benchmarks. Harbor-backed eval suites for regression testing.
- Tune agents. Skill optimization, prompt and hyperparameter tuning, Switchyard model routing.
- Build agents. NVIDIA NeMo Agent Toolkit (NAT) for LangGraph-based agents. Shared infrastructure: Inference Gateway, Secrets, Files, Entity Store, Jobs.
- Generate synthetic data. Generate synthetic data for training or evaluation purposes using Data Designer.
- NeMo Studio (alpha). Browser UI for chat, monitoring, and reviewing optimization suggestions. Studio's agent-focused features are still a work in progress; the CLI is the primary surface today.
Install
Prerequisites: Python 3.12–3.13 and an API key for an inference provider (NVIDIA Build, OpenAI, Anthropic, Google Gemini, or a local Ollama instance).
The nemo-platform distribution is a convenience wrapper that bundles the SDK, shared runtime packages, default first-party plugins, and platform services into a single wheel. The all extra adds the platform services; drop it for the SDK and CLI alone.
Recommended — one command, nemo available everywhere, nothing to activate:
uv tool install "nemo-platform[all]"
Use a virtual environment instead when you also import the SDK from your own code. nemo then works only while the environment is active:
uv venv
source .venv/bin/activate
uv pip install "nemo-platform[all]"
Plain pip install "nemo-platform[all]" works in an environment you manage yourself.
Then bring up the platform:
nemo setup
nemo setup starts local services, registers your LLM provider, discovers available models, installs agent skills, and (optionally) deploys a sample agent.
Verify:
nemo services status
The recommended developer setup is to clone the repo and use make bootstrap instead of installing from PyPI — see the setup playbook for the full walkthrough, including local data dir, DB reset, and troubleshooting.
Where to go next
After nemo setup completes, the CLI prompts you to pick one of two paths. The same two paths are the recommended starting points if you came in via PyPI:
- Build and optimize agents. Open a coding agent session inside your agent's project directory and ask: "Build and optimize an agent using NeMo Platform." The shipped skills will scaffold the agent, deploy it, run evaluations, suggest optimizations, and add guardrails on request.
- Explore the platform. From any coding agent session, ask: "What can I do with NeMo Platform?" to get a guided tour of the capabilities surfaced through skills.
NeMo skills work with Claude Code, Codex, Cursor, OpenCode, and other coding agents. Install or refresh them with nemo skills install --agent <agent>, for example:
nemo skills install --agent claude
Operating the platform
A few useful CLI commands once setup completes:
nemo --help # All commands
nemo models list # Available models
nemo services status # Platform health
nemo skills list # Skills installed on the platform
Every capability is also available via REST API. Model inference uses the model IDs returned from nemo models list and is available at:
http://localhost:8080/apis/inference-gateway/v2/workspaces/default/openai/-/v1/chat/completions
Links
- Source: https://github.com/NVIDIA-NeMo/nemo-platform
- Documentation: https://docs.nvidia.com/nemo-platform/
- Setup playbook: https://github.com/NVIDIA-NeMo/nemo-platform/blob/main/SETUP.md
- CLI reference: https://docs.nvidia.com/nemo-platform/documentation/reference/cli-reference
- API reference: https://docs.nvidia.com/nemo-platform/documentation/reference/api-reference
- Issue tracker: https://github.com/NVIDIA-NeMo/nemo-platform/issues
License
NeMo Platform is licensed under the Apache License 2.0. Third-party open-source dependencies have their own licenses; review them before use.
Metadata
Release files for nemo-platform 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nemo_platform-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / nemo_platform-0.5.0-py3-none-any.whl
| Download URL | nemo_platform-0.5.0-py3-none-any.whl |
|---|---|
| Size | 12.5 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
04aa4e81c016b66fae4e31842d0510346e987691e29ba4344b219099aa666b68
|
|
BLAKE2b-256 checksum How to use checksums |
6d88ad606e6b4ac3a3506428e765fce50c432f87dd38e727fcedf612b369b1ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for nemo-platform 0.5.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.