Core + Suite / Linux 0.9.0
Choose your starting point.
Use Suite to connect. Use Core to operate the infrastructure.
Both components are published as stable Linux 0.9.0 releases. The downloads below link to those releases and their versioned manuals.
Use a network
Start with HyperNet Suite. Install the client, try a local example Page, then follow the connection guide for an existing network. A local Page preview needs no account or network connection.
Suite includes native Browser, Mail and Transfers applications, a terminal viewer, command-line tools and the Python application-stream SDK. You do not need Core just to read Pages.
Operate a network
Start with HyperNet Core. Plan the host requirements, accepted trust, four authority replicas, current clock observations and admitted services. Installing Core alone neither creates a working network nor grants membership.
Use the network preparation guide alongside the hosting and security manuals. Four replicas on one machine do not provide independent failure domains. Normal network administration is command-line work.
Get the release files
Choose the correct product release. Each provides its archive, signatures, target metadata, publisher key, checksum inventory and source accompaniment. Use the full verification procedure before installation.
CLIENTS + INTEGRATION
HyperNet Suite 0.9.0
Native and terminal clients, command-line tools, examples and Python SDK.
AUTHORITY + HOSTING
HyperNet Core 0.9.0
Network authority, hosting services, runtime management and operating manuals.
Verify the publisher, then install
Package tools need Python 3.11 or newer and OpenSSH ssh-keygen with Ed25519 SSHSIG support. Use the trusted package helpers from the matching source release.
Authenticate the publisher through an independently trusted key or pin, then verify signed checksums, target metadata and the package. A public key downloaded beside a signature does not by itself establish trust.
The release guides distinguish the publisher root pin from the SSH key fingerprint and provide the exact commands. Core and Suite keep separate package-trust directories. Preserve existing trust during upgrades.
Core verification and installation · Suite verification and installation
Platform requirements
The qualified profile is native Ubuntu 24.04 x86_64, including GNU libc 2.39 and the documented runtime requirements. Other Linux distributions depend on compatible libraries and capabilities; AArch64, macOS, Windows and SELinux-enabled operation remain unqualified.
| Component | Before you install |
|---|---|
| Core | Rootless Podman, delegated cgroup v2 controls, seccomp and Landlock ABI 6 or newer. Check the complete hosting requirements. |
| Suite native apps | X11 or Wayland, usable EGL/GLX libraries and a working graphics driver. |
| Suite terminal tools | A supported runtime environment; a graphical desktop is not required for terminal or plain output. |
| OpenSSH service access | Separate consent and service grants, plus OpenSSH 10.6 or newer. |
Core qualification · Host requirements · Suite supported platforms
Integrate an application
The Suite package includes SDK/hypernet_streams-0.9.0-py3-none-any.whl. Follow the companion, identity, grant and route setup before opening streams. Matching protocol support is required at the relevant endpoints.
Upgrade an existing installation
Back up the required state and follow the component's release and recovery guide. Do not reinitialise trust to bypass a failed upgrade check. Keep the old installation and compatible backups until the replacement is verified.