nu – the interaction primitive
Build apps in one primitive that spans your whole stack — databases, UIs, AI agents, and services.About • Build • Quickstart • Nu STD • Spec • Examples • Docs • Community
ℹ️ About
The primitive Nu is built on, in three words.
A tiny script keeps its values in memory and calls functions on them. Real apps don't stay there. Values live in a database, arrive from a browser form, render into a dashboard, get recomputed by a background job. Almost none of the code is about the values anymore — it's all interaction between systems.
Nu makes interaction the primitive.
- Ref: a name for a value, wherever it lives. A KV slot, a text block in the browser, an LLM endpoint, a remote object.
- Interaction: what you do with a Ref. Read, write, branch, iterate, compose.
- Fabric: binds Refs to a real system. Bind as many as you need, they all speak the same primitive.
Same primitive, different system. One Ref for any resource, one Interaction for any op. Setting a browser text block is the same interaction as setting a KV slot.
Nu is the Python implementation of the interaction model.
Build with Nu
Four fabrics from nustd, the same code shape in each.
Persistent state
Persistent state. Stores any Python type.
Reach any value by name; it survives restarts. Same code local or sharded across a cluster.
- Serverless, scales to terabytes
- Store any Python type
import nu
import nustd
class DB(nu.Shape):
hits = nustd.kv.IntRef.slot()
# +1 to a persistent counter, starting at 0
op = DB.hits.init(0) >> DB.hits.inc() >> nu.print(nu.str(DB.hits))
app = nu.With(
nustd.kv.rocksdb_navigator(".db"),
body=nustd.kv.auto_flow_atomic(op),
)
nu.run(app) # 1, then 2 on the next run, then 3
Powered by virtuals · rdbpy · RocksDB · LMDB.
Live browser UIs
Reactive UIs from Python. No JS, no build step, no websocket you had to write.
A text block, a chart, a form — set them like variables, they render. Update the value, the browser updates itself.
- 50+ components out of the box
- Live updates for free
import asyncio
import nu
import nustd
class Home(nustd.ui.Page):
hello = nustd.ui.TextRef.slot()
# renders live in the browser
op = Home.hello.set("Hello, browser.")
asyncio.run(nu.arun(nustd.ui.serve(Home, op)))
Distributed execution
Same code runs local or across the cluster. No worker pool to run.
Teleport any Nu tree to any worker; it runs there and returns the result. Where it runs is a binding, not a rewrite.
- Same code, local or remote
- Distribute with a single line
import asyncio
import nu
from nustd.cluster import RayCluster, RayService, Teleport
# any Nu tree
op = nu.print("hello from a worker")
# a local ray instance with two workers; "auto" joins your cluster instead
app = nu.Provide(RayCluster, {"address": None},
nu.ProvideList(RayService, [{"num_cpus": 1}, {"num_cpus": 1}],
nu.Parallel(
Teleport(op, target=0),
Teleport(op, target=1),
),
),
)
asyncio.run(nu.arun(app))
Powered by Ray. For local processes, nustd.mp and nustd.mp_pool take the same shape.
LLM calls
One wire, N providers. Ollama, OpenAI, OpenRouter, Groq, xAI — same call.
LLM chat as a Ref. Swap the model string, keep the code. Local models and hosted APIs meet at the same interface.
- Add intelligence to any Nu app
- 7 providers out of the box
import nu
import nustd
class Bot(nu.Service):
chat = nustd.llm.ChatRef.method(temperature=0.7)
# ask the model
op = Bot.chat(prompt="one-line haiku about rust")
app = nu.With(
nustd.llm.ollama(Bot, host="localhost", model="qwen2.5:7b"),
body=nu.print(nu.str(nu.dict(op)["text"])),
)
nu.run(app)
And more
HTTP, remote fabrics over the network, Python objects as Refs, Claude Code sessions, local worker pools, websocket servers. Same model, same shape. See all of nustd.
Quickstart
Install
Python 3.10 or newer.
pip install "nustd[all]"
nustd pulls in nucore, the kernel. [all] adds every backend.
Run an example
Run one from examples/.
- A live counter, persistent across restarts
python examples/counter.py - An infinite series, live-sampled into a line chart
python examples/sampled.py - A movie tracker: form, filterable table, detail pages
python examples/movies.py
Next
- Your first app: a tutorial from a counter to a live page.
- Docs: tutorials, how-tos and the full reference.
- Examples: every demo above, plus more programs to take from.
Nu STD
The kernel, nucore, holds the language, the engine and one fabric of its own: nu.mem, in-memory state over plain dicts. Everything that talks to the outside world lives in nustd.
Fabrics. Bind one and every Ref inside the bracket reaches a real system.
| Module | What | Extra |
|---|---|---|
nustd.kv |
Persistent state over RocksDB, LMDB or SQLite | kv |
nustd.ui |
Live web UI | ui |
nustd.cluster |
Run trees across a Ray cluster | cluster |
nustd.mp / mp_pool |
Run trees in local worker processes | mp |
nustd.llm |
OpenAI-compatible chat, seven providers | llm |
nustd.cc |
Claude Code sessions as Refs | cc |
nustd.http |
HTTP calls | http |
nustd.proxy |
Any fabric, used from another process | proxy |
nustd.service |
Python objects as Refs | - |
nustd.queue |
A queue between the event loop and threads | queue |
nustd.ws_server |
A websocket host | ws_server |
nustd.valkey |
A private Valkey server, for change notifications across processes | valkey |
The standard library. Python's stdlib, same names and call shape, except a call returns a tree that composes into the rest of the program: math, cmath, random, time, datetime, itertools, functools, asyncio, logging, pathlib, uuid, decimal, fractions, plus Nu's own fin. No extra needed.
pip install "nustd[all]" # everything
pip install "nustd[kv,ui]" # just what you need
Full list in the nustd README and the reference.
Spec
Nu implements the interaction model, a language-agnostic specification of what an interaction is, how Refs name locations and how Interactions compose into programs.
Community
Badge
Building on Nu? Add the badge to your README:
[](https://github.com/nustackdev/nu)
Contributing
Open an issue or a PR. The codebase is small and readable, and the model is stable enough to build on.
Questions
License
Apache-2.0. See LICENSE.md.
Metadata
Release files for nucore 0.6.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| nucore-0.6.4.tar.gz | 300.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nucore-0.6.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 720.2 kB
Release files / nucore-0.6.4.tar.gz
| Download URL | nucore-0.6.4.tar.gz |
|---|---|
| Size | 300.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
58be1177ee9ef46d317e9cdb8482199ed1879c45422aa2103dbd6c0e5df522b6
|
|
BLAKE2b-256 checksum How to use checksums |
84b7fba8f0163f58d549947423d42b0f2c85c97dd42a7f554536b0d480b643ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 16, 2026.
Transparency logRelease files / nucore-0.6.4-py3-none-any.whl
| Download URL | nucore-0.6.4-py3-none-any.whl |
|---|---|
| Size | 420.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1f7ff00c8d7b08594a3181f5e9769962156bf30a6dd248c37b95a081c223ba0a
|
|
BLAKE2b-256 checksum How to use checksums |
9c9a9d1c1e526a5d20e065174ad3abeac3b1af1bee100888e5b73cec3d7778bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 16, 2026.
Transparency logSecurity for nucore 0.6.4
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for nucore-0.6.4.tar.gz
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 Oct 16, 2026.
Transparency logA 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.