nexus-rpc
Nexus Python SDK
Decision gist · record as of 2026-08-14
Yes, if you are building RPC services that need to handle both synchronous and asynchronous operations with a unified protocol. The low install friction, permissive license, and active maintenance make it a reasonable choice. However, be aware this is experimental software—expect breaking changes before a stable release, and verify that the SDK's current feature set fits your deployment model.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.10 or later; SDK is at experimental release stage with anticipated backwards-incompatible changes.
- Low install friction with a single lightweight runtime dependency.
- Active maintenance with recent release 170 days ago.
License · maintenance · safety
MIT (permissive) — MIT license permits commercial and private use with minimal restrictions, making this suitable for most projects.
last release 2026-02-25 (170 days)
0 known vulnerabilities (OSV.dev, 2026-08-14) · 27,795,261 downloads/mo, #846 on PyPI
Alternatives
Verify before relying
pip install nexus-rpc
from dataclasses import dataclass
@dataclass
class MyInput:
name: str
@dataclass
class MyOutput:
message: str- Whether the SDK provides a reference client implementation or if external tooling is required.
- Stability timeline and roadmap for moving from experimental to stable release.
- Performance characteristics and scalability limits for long-running operations.
What it is and what it does
Nexus RPC is a Python SDK for building synchronous RPC services that can handle both immediate and long-running operations. It lets you define service interfaces and operation handlers that respond either synchronously (returning results directly) or asynchronously (returning a token for tracking). Callers can check operation status, cancel in-flight work, or provide callback URLs for result delivery.
The SDK is designed for two main workflows: defining service interfaces with typed inputs and outputs, and implementing handlers that process incoming requests and dispatch them to operation methods. It currently does not provide a reference client or server implementation—you integrate the handler into your own server or worker process. The package is at experimental stage, so backwards-incompatible changes are expected before a stable release.
Use it for
- Build a service that handles both quick synchronous requests and long-running async jobs with unified RPC semantics.
- Implement a handler that accepts protocol requests and routes them to typed operation methods with automatic serialization.
- Create a worker that processes async operations and delivers results via callback URLs when ready.
- Define strongly-typed RPC service contracts that can be shared across multiple handler implementations.
- Integrate long-running operations into existing RPC infrastructure with operation cancellation and status polling.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you are building RPC services that need to handle both synchronous and asynchronous operations with a unified protocol.
The low install friction, permissive license, and active maintenance make it a reasonable choice. However, be aware this is experimental software—expect breaking changes before a stable release, and verify that the SDK's current feature set fits your deployment model.
Install
nexus-rpc on PyPI
Before you install
Low install friction with a single lightweight runtime dependency. Active maintenance with recent release 170 days ago. Requires Python 3.10 or later.
Requires Python 3.10 or later; SDK is at experimental release stage with anticipated backwards-incompatible changes.
License in practice
MIT license permits commercial and private use with minimal restrictions, making this suitable for most projects.
Quickstart
pip install nexus-rpc
from dataclasses import dataclass
@dataclass
class MyInput:
name: str
@dataclass
class MyOutput:
message: strVerify before relying
- Whether the SDK provides a reference client implementation or if external tooling is required.
- Stability timeline and roadmap for moving from experimental to stable release.
- Performance characteristics and scalability limits for long-running operations.
Package facts
| License | MIT permissive |
| Python support | Supports the current Python release >=3.10 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 1 packagetyping-extensions |
| Maintenance | Actively maintained 170 days since the last release |
| First released | |
| Downloads | 27,795,261 / month, #846 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
Evidence: nexus_rpc-1.4.0-py3-none-any.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 › “synchronous RPC protocol”
- nexus-rpcNexus Python SDK provides a framework for defining synchronous RPC…
- connectrpcConnect is a runtime library for building and consuming RPC APIs…
- thriftpy2ThriftPy2 is a pure Python implementation of Apache Thrift that lets…
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 connect-python · nebius · python-jsonrpc-server · python-logstash-async · ajsonrpc · janus · synchronicity · ncclient · unsync · python-lsp-jsonrpc