Open source · self-hostable · performance-first

Own your infrastructure.
Don't rent it.

dotcommoners rebuilds the infrastructure most teams rent — orchestration, streaming, browser automation, observability — as MIT-licensed software you own and operate on your own hardware. Written in Rust, Zig, and Python.

Rust Zig Python MIT · No lock-in
In one line

dotcommoners is an open-source organization that rebuilds the infrastructure most teams rent — orchestration, streaming, browser automation, observability — as MIT-licensed software you own and operate on your own hardware.

2
Public projects
Machineuse & RevenProx
3
Systems languages
Rust · Zig · Python
MIT
License
Permissive, no lock-in
100%
Self-hostable
Your hardware, your rules

The thesis

Rent an infrastructure stack, or own one

Modern platforms are increasingly assembled out of metered SaaS. dotcommoners takes the opposite bet — that the core building blocks should be open source, self-hostable, and yours.

Renting it

Metered SaaS

  • Someone else's servers, pricing, and roadmap
  • Metered by seat, connection, or request
  • Your data leaves your control
  • Pieces you depend on can change or vanish
Owning it

dotcommoners

  • Runs on hardware you already control
  • Cost is the hardware, not a subscription
  • Full source you can read, fork, and patch
  • Nothing phones home — no lock-in

Read the manifesto and philosophy →


What we're building

The rented layers, rebuilt as a commons

We focus on the load-bearing parts of a stack — the systems that must be fast, correct, and horizontally scalable.

Building

Orchestration

Scheduling and managing distributed workloads across a fleet — placing work on the right node without a central bottleneck.

Shipping

Real-time streaming

Moving events to clients at scale — Server-Sent Events, fan-out, and topic routing over a brokerless mesh.

RevenProx →
Shipping

Browser automation

Running isolated browsers at fleet scale — creating, scheduling, and parking instances across many nodes.

Machineuse →
Building

Observability

Understanding what your systems are doing — metrics, traces, and signals you own rather than ship to a vendor.

Projects

Open-source building blocks

Each project is production-oriented, documented, and self-hostable. Pick a piece, run it on your own hardware, and read the source.

PythonBrowser automationMIT

Run browser automation at fleet scale, on hardware you own.

  • Isolated browser instances across many worker nodes
  • Brokerless NNG messaging — no central broker to bottleneck
  • Intelligent scheduling places work on the right node
  • Snapshot-based dormancy parks idle instances and reclaims resources
ZigReal-time streamingMIT

Fan out real-time events to 10M+ connections, brokerless.

  • Designed for 10M+ concurrent connections across 100+ instances
  • Brokerless NNG mesh — no single point of failure
  • JWT authentication built in
  • Topic-based routing: publish once, deliver to the right subscribers

See all projects and full descriptions →

Principles

Software you own, not rent

The values behind every project. Read more on the principles page.

Open source, permissively

Everything is MIT-licensed. Fork it, patch it, ship it — no proprietary control plane, no licensing fees.

Self-hostable by default

On-premise deployment is the design goal, not a paid tier. Run it on a laptop, a homelab, or a fleet of edge nodes.

Performance-first

Rust and Zig where microseconds and memory matter; Python where an ergonomic control plane and rich ecosystem win.

Brokerless & scalable

Brokerless architectures with no central bottleneck and no single point of failure. Horizontal scale is built in.

No vendor lock-in

Nothing phones home. If dotcommoners vanished tomorrow, you would still have the full source and could run it forever.

Readable & documented

Real docs at docs.dotcommoners.com, clear architecture notes, and source you can actually follow and contribute to.

One stack, your hardware

Deploy the pieces you need, side by side

No proprietary control plane, no metered backend. Pull the images, point them at your nodes, and run production-grade streaming and browser automation entirely on infrastructure you own.

Read the deployment docs →

docker-compose.yml
# Self-host the whole stack on your own nodes
services:
  revenprox:
    image: dotcommoners/revenprox
    connections: 10_000_000   # across the mesh
    mesh: brokerless-nng
    auth: jwt
  machineuse:
    image: dotcommoners/machineuse
    workers: 64
    dormancy: snapshot   # park idle browsers
Who it's for

Built for people who run their own stack

Platform engineers

Teams building internal platforms who want auditable, self-hosted building blocks instead of another metered dependency.

Self-hosters & homelabbers

People who prefer to run their own services and want production-grade infrastructure they fully control.

Systems-minded developers

Engineers who care about how things work under the hood and want source they can read, extend, and contribute to.

FAQ

Questions

What is dotcommoners?

dotcommoners is an open-source organization building high-performance, self-hostable infrastructure and systems software. Its public projects include Machineuse, a distributed container manager for browser automation at scale, and RevenProx, a Server-Sent Events proxy written in Zig.

Is dotcommoners software free and open source?

Yes. dotcommoners projects are open source under the permissive MIT license and are designed to be self-hosted on your own infrastructure with no vendor lock-in.

What languages does dotcommoners build in?

Projects favour performance-first systems languages — primarily Rust and Zig — with Python where an ergonomic control plane and rich ecosystem matter, as in Machineuse.

How do I get started or contribute?

Every project has a public GitHub repository with documentation and a quick-start. Browse the projects, read the docs at docs.dotcommoners.com, or email contact@dotcommoners.com.

Read the full FAQ →

Build on the commons

Own the core of your stack

Explore the source, read the docs, or get in touch. Contributions and questions welcome.

github.com/dotcommonersContact us