NEF2: The AI Operating Substrate
A hardware-native, framework-independent intelligence stack for the next generation of autonomous systems.
NEF2: The AI Operating Substrate
A hardware-native, framework-independent intelligence stack for the next generation of autonomous systems.
The Vision
NEF2 is not a library; it is a Substrate. It eliminates the "framework tax" by bypassing heavy abstractions like PyTorch and JAX, communicating directly with the silicon through a custom-built hardware-native stack.
It is designed for a world where AI is not just a model, but a distributed, agentic system requiring zero-copy memory movement, hardware-peak performance, and intelligent memory virtualization.
Key Pillars
- Zero-Dependency Core: Pure Python/C++/Rust. No external ML frameworks.
- Hardware-Native Stack (NEF-HNS): Direct NVIDIA Driver API integration using raw PTX assembly.
- HyperCache Memory: Transparent virtualization of VRAM across System RAM and NVMe for trillion-parameter scale.
- Agent-Native Primitives: Built-in support for model-chaining, shared tensor buses, and streaming inference.
Feature Matrix
| Feature | Status | Technology |
|---|---|---|
| NEFCore Runtime | ✅ Production | Hybrid C++/Rust/Python execution |
| CUDA Driver Backend | ✅ Production | Raw PTX Kernel execution |
| HyperCache (VRAM/RAM) | 🚧 Beta | Intelligent memory paging |
| TurboQuant | 🚧 Beta | Adaptive precision (FP8, INT4, NF4) |
| Multi-GPU Fabric | ✅ Active | Unified logical accelerator |
| NEF Compiler | ✅ Active | Graph capture & kernel fusion |
Documentation Suite
For deep dives into specific areas of the NEF2 ecosystem:
- Getting Started: Installation, your first model, and basic training.
- Architecture Deep-Dive: Understanding NEFCore, HyperCache, and the Compiler stack.
- Hardware Support: Details on CUDA, HIP, Metal, and NPU integration.
- Developer Guide: Contributing, coding standards, and kernel development.
Quick Start
Installation
pip install nef2
Hardware-Native Tensors
from nef2 import Tensor
import nef2.gpu as gpu
# NEF2 automatically handles device placement
x = Tensor([[1, 2], [3, 4]], requires_grad=True)
if gpu.cuda_available():
# Direct hardware-native matmul
a, b = gpu.tensor([[1.0, 2.0]]), gpu.tensor([[3.0], [4.0]])
c = a.matmul(b)
print(f"Result on {gpu.device_name()}: {c.tolist()}")
Roadmap
- Phase 1 (Active): Establish the Foundation with NEFCore and custom CUDA kernels.
- Phase 2 (Active): Implement the Rust-based safe concurrency layer and distributed networking.
- Phase 3 (Active): Launch the HyperScale Multi-GPU Fabric for unified cluster execution.
- Phase 4 (Active): Realize Agent-Native Infrastructure for autonomous, model-agnostic intelligence.
Built for the future of Distributed Intelligence.
Join the revolution at github.com/Hexa08/NEF2
Metadata
Release files for nef2 0.2.3
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 | |
|---|---|---|---|---|
| nef2-0.2.3.tar.gz | 2.3 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nef2-0.2.3-cp312-cp312-manylinux_2_34_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.34+ x86-64 | Details |
Total release size: 4.7 MB
Release files / nef2-0.2.3.tar.gz
| Download URL | nef2-0.2.3.tar.gz |
|---|---|
| Size | 2.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cfa839a5921a8d92af9bc71ec390fc26258bf9f4e4cfc12196d97eb8506b4236
|
|
BLAKE2b-256 checksum How to use checksums |
c6ecf6f287e6a46cf4e44636eaa1889852402d412f88aeec2a789450ff2b59c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.1
|
Release files / nef2-0.2.3-cp312-cp312-manylinux_2_34_x86_64.whl
| Download URL | nef2-0.2.3-cp312-cp312-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 3.12 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
b0374a6b71301d128f0f823d1b2e5c3ca6fdbf5bfb8d294c4c068e900cce8bb5
|
|
BLAKE2b-256 checksum How to use checksums |
8cc4a1631c96ba8c74bb436af967555320f0e74539c5546d9e1bd71d8afce8db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.1
|
Security for nef2 0.2.3
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.