HyperNet Core + Suite / 0.9.0
A network with explicit authority.
Publishing, communication and application connections within boundaries your network defines.
Core provides authority, hosting and runtime services. Suite provides the native applications, terminal viewer, CLI and integration tools. Together they support the workflows below.
Pages and discovery
HyperPages are reviewed publications with text, layouts, forms and static media. Authors can use panels, rows, scrolling areas and optional decorative motion. Readers choose when to reveal images and can inspect a form before submitting it.
Pages contain no scripts. Reading one cannot automatically submit a form or choose local credentials. Native and terminal views use the same Page format and permission checks.
Search an approved network catalogue or an explicitly selected local catalogue. Private local queries stay on the client; remote catalogue searches have their own disclosure boundary.
Write a Page · Use the native browser · Use the terminal viewer
Private communication
Mail exchanges encrypted letters through owner-controlled addresses, separate devices and recipient-selected storage. Sealed Pages share encrypted publications with selected recipient devices and hosts that consent to storing them.
Native Transfers lets a sender offer an encrypted file and a recipient review and accept it. Downloads can resume, and retained receipts describe delivery. The current native transfer object limit is 8 MiB of ciphertext, within a 64 MiB vault; it is not a general large-file transfer service.
Applications such as FICC implement larger transfers over application streams using their own verified ranges and recovery protocol. That does not change the native Transfers limit.
Native Mail · Native Transfers · Sealed Pages
Application streams and agents
Version 0.9.0 adds reusable, relay-only duplex connections for admitted application services. The native companion and packaged Python SDK handle the local connection boundary. Attached endpoints and remote authority access support applications that connect outward through their approved infrastructure.
Applications use separate identities and scoped grants. A grant does not hand an application the user's private keys, and receiving applications keep control of their own operations. Agents can use the same explicit interfaces; HyperNet does not supply an AI model or inference engine.
Streams are finite: the current connection ceiling is 1 GiB and one hour. Application protocols must handle cancellation, expiration and reconnects. Large objects need application-level chunking, integrity and recovery.
FICC uses these interfaces for selected cross-cluster inference, delegated operations and verified model-file transfer within one approved HyperNet network. The API is reusable by other services.
Application stream workflow · Python SDK · Remote authority access
Services and hosting
Hosts choose what software runs, what they store, how much resource they offer and how long it remains available. Local runtime controls govern admitted services. A host can withdraw without waiting for network consensus.
Approved OpenSSH services expose fixed commands under separately granted authority. This capability does not give clients an arbitrary remote shell. Normal remote Page and communication traffic uses authenticated, pinned TLS routes rather than SSH.
Host requirements · Service runtime · Shared SSH services
Network federation
Independent networks can share approved Pages through agreements. Authors opt in and the destination reviews the publication. Each network retains its membership and administration.
Page federation is distinct from application-stream access. An agreement to share publications does not create unrestricted application connections between networks.
Federation model · Publication workflow
Authority and recovery
Replicated authority records membership, permissions and approved changes. Operating a network requires four appointed authority replicas, current clock observations, accepted trust and explicitly admitted services.
Administration includes scoped application access, audit, backups and recovery. Authority state, private keys and host-local operational records have distinct custody requirements. Follow the upgrade and recovery procedures before replacing an existing deployment.
Authority · Backups · Upgrade and recovery
Security and platform boundaries
Authenticated, pinned TLS routes and explicit permissions protect different parts of a connection. A relay hides the reader's address from the destination connection. Privacy from the destination operator also depends on independently operated, noncolluding infrastructure.
The published release is qualified on native Ubuntu 24.04 x86_64 within the documented kernel, library and graphics requirements. Other platforms require their own qualification. No independent security certification is claimed.
Private routes and assumptions · Security model · Supported deployment