Frequently asked questions
Everything you might want to know about dotcommoners — what it is, how the licensing works, self-hosting, the tech, and how to contribute.
dotcommoners is an open-source (MIT) organization building self-hostable infrastructure in Rust, Zig, and Python. Everything runs on your own hardware with no vendor lock-in. Public projects: Machineuse (browser automation) and RevenProx (SSE proxy).
What is dotcommoners?
dotcommoners is an open-source organization building high-performance, self-hostable infrastructure and systems software. It rebuilds the infrastructure most teams rent — orchestration, streaming, browser automation, observability — as MIT-licensed software you own and operate on your own hardware. Public projects include Machineuse and RevenProx.
Is dotcommoners really open source and MIT-licensed?
Yes. Every dotcommoners project is released under the permissive MIT license. You can read the full source on GitHub at github.com/dotcommoners, fork it, modify it, and run it in production with no proprietary control plane and no licensing fees.
Can I self-host these projects?
Yes — self-hosting is the entire point. Every project is designed to run on your own infrastructure, whether that is a single laptop, a homelab, or a fleet of edge nodes. There is no required SaaS backend and nothing phones home to a vendor.
What programming languages are the projects written in?
dotcommoners builds primarily in performance-first systems languages — Rust and Zig — and uses Python where an ergonomic control plane and a rich ecosystem matter. RevenProx is written in Zig; Machineuse is written in Python.
What projects does dotcommoners publish?
Two public projects today: Machineuse, a distributed container manager for browser automation at scale (Python, brokerless NNG messaging, snapshot-based dormancy); and RevenProx, a high-performance Server-Sent Events proxy (Zig, designed for 10M+ concurrent connections across a brokerless NNG mesh with JWT auth and topic-based routing). More systems software in Rust, Zig, and Python is in development.
How is this different from a managed SaaS product?
A SaaS product runs on the vendor’s servers, meters you by seat, connection, or request, and controls the roadmap and your data. dotcommoners projects run on your servers, cost only the hardware you already own, and can be forked and modified freely. You trade a managed dependency for full ownership and control.
Is there any vendor lock-in?
No. The code is MIT-licensed and self-hostable with no proprietary control plane. If dotcommoners disappeared tomorrow, you would still have the full source and could keep running and maintaining it indefinitely.
How do I get started?
Pick a project from the projects page, open its GitHub repository, and follow the README and quick-start. Full documentation lives at docs.dotcommoners.com. Each project is built to be cloned and run on your own hardware.
How do I contribute?
Browse the GitHub organization at github.com/dotcommoners, pick a project, get it running locally using the docs, then open an issue or a pull request. Each repository has its own contributing notes. You can also email contact@dotcommoners.com.
Who is dotcommoners for?
Platform engineers building internal platforms, self-hosters and homelabbers who run their own services, and systems-minded developers who want auditable, self-hosted building blocks instead of another metered dependency.
Read the full documentation, browse the source on GitHub, or get in touch — email contact@dotcommoners.com.