Naylence Runtime
Message fabric, connectors, listeners, and security primitives that power Naylence agents, nodes and sentinels. This package provides the runtime substrate—not the high‑level Agent SDK or tutorials.
What this is
naylence‑runtime is the foundational library that implements:
- FAME fabric (in‑process and networked) for routing envelopes between clients, agents, and sentinels.
- Connectors & listeners for WebSocket/HTTP transports, back‑pressure, flow control, and streaming.
- Profiles & admission: pluggable admission flows (e.g., token‑based), logical addressing, and attach APIs.
- Security building blocks: envelope signing, overlay encryption, JWT/JWKS helpers, and identity hooks.
- FastAPI utilities used by sentinels and auxiliary services (JWKS, OAuth token router, etc.).
It is meant to be embedded by the Agent SDK, sentinels, and security add‑ons. Most users should not call it directly unless they’re extending transports, writing custom admission, or integrating Naylence into an existing control plane.
When to use (and when not)
Use naylence‑runtime if you need to:
- Build or customize transport connectors/listeners.
- Implement or extend admission/identity flows.
- Operate a bespoke sentinel or welcome/CA services.
Prefer the higher‑level packages for day‑to‑day development:
- Naylence Agent SDK (Python) — idiomatic agent APIs & ergonomics. → https://github.com/naylence/naylence-agent-sdk-python
- Naylence Examples (Python) — runnable learning path & patterns. → https://github.com/naylence/naylence-examples-python
If you’re just getting started, learn with the Agent SDK and Examples first; drop down to Runtime only when you need lower‑level control.
Security profiles
The runtime exposes security primitives used by sentinels and agents through profiles:
- direct — no admission; useful for local/dev.
- gated — OAuth2/JWT‑gated admission; TLS via your reverse proxy.
- strict‑overlay — sealed, end‑to‑end overlay encryption with SPIFFE/X.509‑style identities.
Important: The strict‑overlay profile is supported only when the
naylence‑advanced‑securitypackage is installed. Install that add‑on to enable sealed channels and SVID‑backed identities.
Relationship to other repos
- Runtime (this repo): https://github.com/naylence/naylence-runtime-python
- Agent SDK (Python): https://github.com/naylence/naylence-agent-sdk-python
- Examples (Python): https://github.com/naylence/naylence-examples-python
- Advanced Security add‑on: https://github.com/naylence/naylence-advanced-security-python
What this README intentionally omits
This page explains purpose and scope only. It does not include code samples, quick starts, or container recipes. For that:
- Start with the Agent SDK docs and examples to learn the development model.
- Refer to the Examples repository for runnable demos from simple to distributed to security‑hardened.
Support & license
- Issues: open tickets in the corresponding repository (Runtime, SDK, Examples, or Advanced Security) based on where the problem belongs.
- License: Apache‑2.0.
1 maintainer
Metadata
1 maintainer
Release files for naylence-runtime 0.4.13
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 | |
|---|---|---|---|---|
| naylence_runtime-0.4.13.tar.gz | 341.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| naylence_runtime-0.4.13-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 851.4 kB
Release files / naylence_runtime-0.4.13.tar.gz
| Download URL | naylence_runtime-0.4.13.tar.gz |
|---|---|
| Size | 341.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
175ec1edfd4a1799fa1083cf04945192e2c2259d13cf7c725001208668111d20
|
|
BLAKE2b-256 checksum How to use checksums |
5568c9637d06c305f5033482f14e8c4e216615b05c15c54bff7253df3a3d52dc
|
| 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 Apr 18, 2026.
Transparency logRelease files / naylence_runtime-0.4.13-py3-none-any.whl
| Download URL | naylence_runtime-0.4.13-py3-none-any.whl |
|---|---|
| Size | 510.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
07a7bd2dcf7f26f0715126e1dda6238302070158e4e88df57b135caf08292b1c
|
|
BLAKE2b-256 checksum How to use checksums |
9e4be98c5a9565167b60ea61653946e7d365aadef297636d89fd52df69fd89e5
|
| 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 Apr 18, 2026.
Transparency logSecurity for naylence-runtime 0.4.13
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 naylence_runtime-0.4.13.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 Apr 18, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
