Nexura Studio
The older local workflow Studio and its nexura-studio launcher.
Install
pip install nexura-studio
Alpha (0.4): pip install nexura-studio. See package installation.
Minimal example
This example uses an in-process ASGI transport and a disposable database, without a listener. Runs use the real workflow engine; built-in demo data is synthetic. The React Studio/API uses nexura-runtime[studio] instead. Without this package, nexura_runtime.studio.create_app() raises MissingDependencyError naming nexura-studio.
import asyncio
import tempfile
from pathlib import Path
import httpx
from nexura_studio import create_app
async def main() -> None:
with tempfile.TemporaryDirectory() as tmp:
app = create_app(db_path=Path(tmp) / "studio.sqlite3")
async with httpx.AsyncClient(
transport=httpx.ASGITransport(app=app),
base_url="http://127.0.0.1",
headers={"X-Nexura-Session": app.state.session_token},
) as client:
modules = (await client.get("/api/v1/modules")).json()["modules"]
print(len(modules), "modules, for example", sorted(m["name"] for m in modules)[0])
page = await client.get("/")
assert page.status_code == 200 and "nexura-session" in page.text
asyncio.run(main())
Status and limits
Status: alpha (0.4), Python 3.12 (the same as
nexura-runtime). Single user, local use; it has not had an external security review.
Single user, this machine only. The launcher defaults to 127.0.0.1 and refuses non-loopback --host without NEXURA_STUDIO_TOKEN or the explicit insecure opt-in. State changes require the session token: it stops other web pages, not local programs that can read it. An insecure opt-in does not make a public endpoint safe.
Documentation and licence
Main documentation · Full guide. MIT, Copyright (c) 2026 Liceron. See LICENSE. Bundled Noto Sans Devanagari is SIL OFL 1.1; see its OFL.txt.
Metadata
Release files for nexura-studio 0.4.0
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 | |
|---|---|---|---|---|
| nexura_studio-0.4.0.tar.gz | 377.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nexura_studio-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 762.3 kB
Release files / nexura_studio-0.4.0.tar.gz
| Download URL | nexura_studio-0.4.0.tar.gz |
|---|---|
| Size | 377.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8f9d1cba2377c9618de7f4c4410a376cf9f6400183ae14f77bb11686129f3e7e
|
|
BLAKE2b-256 checksum How to use checksums |
a12ec339a2b45d6bd7653c996fc0e882d49abfff01e258d44f3d603e375c3106
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.8 {"installer":{"name":"uv","version":"0.12.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / nexura_studio-0.4.0-py3-none-any.whl
| Download URL | nexura_studio-0.4.0-py3-none-any.whl |
|---|---|
| Size | 384.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2d07fe18fcbf26273da1d9374bccf55f335c8e6d9a814c9128942afba89ba836
|
|
BLAKE2b-256 checksum How to use checksums |
bd34de3fd84ff4c36cf0bbb88a664aa857a83b2a7cb27fbfc9f55bbe9d173241
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.8 {"installer":{"name":"uv","version":"0.12.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for nexura-studio 0.4.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.