community Build in public. Review in public. Ship with care.
Community
Zypher is designed to be read and contributed to. If you care about explicit design, auditable internals, and performance that stays predictable as the codebase grows, you’ll feel at home here.
Contribution philosophy
Small PRs, clear intent, and decisions recorded where future maintainers will find them.
When Zypher gains a feature, it should also gain tests, docs intent, and a predictable maintenance cost.
Open-source values
Respect users’ time. Prefer clarity over cleverness. Optimize for longevity.
Zypher aims to be a framework you can audit, fork, and evolve—without needing permission or folklore.
How you can help right now
API review Propose an explicit, minimal surface area for routing, middleware, and response building.
Benchmarks Add repeatable perf tests that measure tail latency and memory behavior.
Docs scaffolding Turn design notes into examples that teach, not just reference.