ciris-server
The fabric node — the federation's headless cohabitation runtime (registry + lens [+ node] over one shared substrate), as the abi3 wheel CIRISAgent consumes. agent = fabric node + brain.
Decision gist · record as of 2026-08-14
Yes, but with conditions. Install if you are building or testing a decentralized federation using the CIRIS ecosystem and can tolerate early-stage software (first release 2026-08-08, 2 repository stars). The AGPL-3.0-or-later license is suitable for open infrastructure but incompatible with proprietary deployments. No known security vulnerabilities, active maintenance, and zero runtime dependencies reduce friction. However, scalability claims are modeled rather than proven, and the package's maturity is unproven—treat as experimental for production use.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python >=3.10; compiled wheels are platform-specific (Android, macOS, Linux, Windows).
- Node identity and configuration must be provided at boot via signed CEG claims, not environment variables.
- Medium install friction due to compiled wheels across multiple platforms (Android, macOS, Linux, Windows).
License · maintenance · safety
AGPL-3.0-or-later (agpl) — AGPL-3.0-or-later license requires that any modifications or derivative works distributed to others must be released under the same license and include source code. Suitable for open infrastructure but incompatible with proprietary deployments or closed-source integrations.
last release 2026-08-14 (0 days) · last repo commit 2026-08-14 · 2 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 85,441 downloads/mo, #13,922 on PyPI
Alternatives
Verify before relying
pip install ciris-server
import ciris_server
node = ciris_server.Node(home='/path/to/node', key_id='your-identity')
node.start()- Actual scalability at claimed participant counts; topology is modeled but not yet tested at scale
- Performance characteristics and throughput under realistic federation load
- Stability and breaking-change risk given the package's very recent release history
- Interoperability guarantees with other CIRIS ecosystem components (ciris-persist, ciris-edge, ciris-verify)
What it is and what it does
ciris-server is a headless federation node that composes three Rust libraries—ciris-persist (corpus and admission control), ciris-edge (transport and replication), and ciris-verify (post-quantum cryptography)—into a single runnable service. It is shipped both as a standalone binary and as a PyO3 abi3 wheel that agents can embed. Unlike its component libraries, which make cryptographic and admission decisions in isolation, the server runs control loops that reconcile a live node to a signed claim graph (CEG), exposes every decision to an operator, and manages a decentralized mesh without privileged parties.
The node's defining constraint is that it does not reason, decide, or act on its own—it attests, stores, replicates, scores, and serves. Configuration is entirely claim-driven and signed; no environment variables are used. The architecture claims to solve the open problem of building a mesh that is simultaneously decentralized (no privileged relay), moderatable (graded consent ladders at every hop), and scalable (ALM tree with bounded per-node fan-out and logarithmic depth). Replication uses AEAD encryption such that relays cannot read the payloads they forward, and moderation is applied by authoring claims rather than by external policy.
Use it for
- Run a federated node in a decentralized mesh where you control admission and consent topology without a central authority.
- Embed the node as a library in a CIRISAgent to provide the fabric infrastructure that agents depend on for attestation and replication.
- Build a moderatable P2P network where every hop is an operator-accountable node with its own consent edges and graded moderation ladder.
- Store and replicate signed claims across a network where relays cannot inspect or tamper with encrypted payloads in transit.
- Operate a node in a federation where configuration is entirely versioned as signed claims and can be updated hot without restart.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, but with conditions.
Install if you are building or testing a decentralized federation using the CIRIS ecosystem and can tolerate early-stage software (first release 2026-08-08, 2 repository stars). The AGPL-3.0-or-later license is suitable for open infrastructure but incompatible with proprietary deployments. No known security vulnerabilities, active maintenance, and zero runtime dependencies reduce friction. However, scalability claims are modeled rather than proven, and the package's maturity is unproven—treat as experimental for production use.
Install
ciris-server on PyPI
Before you install
Medium install friction due to compiled wheels across multiple platforms (Android, macOS, Linux, Windows). Active maintenance with recent releases, but very new package (first release 2026-08-08) with minimal adoption signal—only 2 repository stars warrant caution in production use.
Requires Python >=3.10; compiled wheels are platform-specific (Android, macOS, Linux, Windows). Node identity and configuration must be provided at boot via signed CEG claims, not environment variables.
License in practice
AGPL-3.0-or-later license requires that any modifications or derivative works distributed to others must be released under the same license and include source code. Suitable for open infrastructure but incompatible with proprietary deployments or closed-source integrations.
Quickstart
pip install ciris-server
import ciris_server
node = ciris_server.Node(home='/path/to/node', key_id='your-identity')
node.start()Verify before relying
- Actual scalability at claimed participant counts; topology is modeled but not yet tested at scale
- Performance characteristics and throughput under realistic federation load
- Stability and breaking-change risk given the package's very recent release history
- Interoperability guarantees with other CIRIS ecosystem components (ciris-persist, ciris-edge, ciris-verify)
Package facts
| License | AGPL-3.0-or-later agpl |
| Python support | Supports the current Python release >=3.10 |
| Install friction | Medium. Platform-specific wheel |
| Runtime dependencies | None |
| Maintenance | Actively maintained 0 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 85,441 / month, #13,922 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
Evidence: ciris_server-0.5.172-cp310-abi3-android_24_arm64_v8a.whl; ciris_server-0.5.172-cp310-abi3-android_24_armeabi_v7a.whl; ciris_server-0.5.172-cp310-abi3-android_24_x86_64.whl; ciris_server-0.5.172-cp310-abi3-macosx_10_12_x86_64.whl; ciris_server-0.5.172-cp310-abi3-macosx_11_0_arm64.whl; ciris_server-0.5.172-cp310-abi3-manylinux_2_39_aarch64.whl; ciris_server-0.5.172-cp310-abi3-manylinux_2_39_x86_64.whl; ciris_server-0.5.172-cp310-abi3-win_amd64.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “federated node mesh networking”
- ciris-serverEmbeds a Rust-based federation node that composes cryptographic…
- meshtasticA Python library and CLI for communicating with Meshtastic mesh radio…
- ciris-edgeA Rust-based transport and replication layer for the CIRIS Epistemic…
Give your agent the search over MCP, or paste the wish link into any chat.
More Distributed Computing packages
gRPC Python is an HTTP/2-based RPC framework that enables you to define and call remote procedures across network boundaries using protocol buffers for serialization.
Install it if you need RPC communication in a distributed system or are integrating with existing gRPC services.
execnet lets you spawn and communicate with Python interpreters across local processes, remote hosts, and different platforms, using a simple API for task distribution and inter-process messaging.
However, the aging maintenance status (275 days since last release) means you should verify it meets your concurrency and performance needs before committing to a…
Cloudpickle extends Python's standard pickle module to serialize lambda functions, interactively-defined functions and classes, and other constructs that the default pickle cannot handle, making it suitable for cluster computing and remote code execution.
Install it if you need to serialize lambda functions, interactively-defined code, or non-standard Python constructs for cluster computing or distributed execution.
Provides a unified, open()-compatible Python API for streaming large files from remote storage (S3, GCS, Azure, HDFS, SFTP, HTTP) and local filesystems, with transparent compression support.
Install it if you work with large files on cloud storage or remote systems and want to avoid writing boilerplate around multiple SDKs.
Portalocker provides cross-platform file locking with support for exclusive and shared locks, plus Redis-based distributed locks and process-aware PID file locking.
Install it if you need file or process coordination; the optional extras (pywin32, redis) are only required for specific lock types.
Ray is a distributed computing framework that scales Python applications from a single machine to multi-node clusters, providing abstractions for parallel tasks, stateful actors, and shared objects.
See also ciris-edge · ciris-persist · ciris-verify · matrix-synapse · agentrust-trace · service-identity · agent-governance-toolkit-core · Fabric3 · browser-use-core · ua-parser-rs