schipper.io

What It Is

Schipper.io is an independent software studio operated by SCHIPPER.IO LLC, positioned around building “ceremony-free” developer infrastructure. Its currently active public product is IonStream, a distributed streaming queue platform based on .NET 10, Raft consensus, and a gRPC-native protocol. It emphasizes a single Native AOT binary, zero external dependencies, and clear environment-variable configuration, with the goal of reducing the operational burden associated with traditional infrastructure such as Kafka/ZooKeeper/JVM.

Core Capabilities

IonStream supports message production and consumption, topics, partitions, consumer groups, append-only logs, retries and DLQ, static clusters, dynamic scaling, cross-cluster replication, and TLS by default. For observability, it provides OpenTelemetry metrics, a Prometheus endpoint, Grafana dashboards, and a Docker Compose stack that includes Prometheus, Grafana, cAdvisor, and node-exporter. SDK coverage includes .NET/C#, Go, TypeScript/JavaScript, Python, Rust, and Java. The .NET client is the most complete; Go uses REST; TypeScript supports Node gRPC; and browsers can connect via REST or gRPC-Web.

Open Source, Deployment, and Pricing

Its openness strategy is mixed: client SDKs are MIT-licensed and can be used freely; the server binary is free for non-commercial users and smaller companies; full server source code is available for audit only to paid enterprise licensees. The available text does not disclose specific revenue thresholds, enterprise pricing, payment methods, or SLA terms. For deployment, IonStream supports building from source as well as win-x64/linux-x64 Native AOT builds. Target machines do not need the .NET runtime, ZooKeeper, Kafka, agents, or sidecars, making it suitable for self-hosted and containerized environments.

Pros and Cons

The strengths are its clear architectural philosophy, simple deployment, broad documentation coverage, and first-class treatment of production concerns such as Raft, replication, crash recovery, TLS, metrics, and DLQ. The drawbacks are that IonStream is marked as Early Access, while advanced features such as mTLS, SASL, and an admin CLI are still on the roadmap; the current product line has only one active product; community adoption, case studies, performance benchmarks, and commercial support information are limited; and the server is not fully open source.

Who It’s For and Access from China

It is suitable for small and mid-sized teams or platform engineering teams that want a self-hosted, lightweight message queue, favor a .NET-oriented stack, and need low-dependency deployment. If an organization already depends heavily on the Kafka/Pulsar ecosystem, the value of migration should be evaluated carefully. For access from China, the collected text does not provide information on availability, mirrors, payments, or local support, so this remains unknown. Alternatives to consider include Apache Kafka, Redpanda, NATS JetStream, RabbitMQ, Apache Pulsar, and Redis Streams.