Skip to content

Principles

StaffOps is built on a few core ideas that shape every decision — technical or otherwise.

Open by default

Code, documentation, architectural decisions, and operational learnings are all public. There is no "enterprise edition", no feature gating, no closed roadmap. What we build, we build in the open.

Collaboration over competition

Contributions are welcome from anyone — regardless of company, background, or experience level. We believe that the best operational knowledge comes from many perspectives, not from a single team.

This also means we respect and build upon other open source projects. We cite, integrate, and contribute back to the ecosystem we depend on.

AI as a tool, not an identity

Automation and AI are tools in the toolbox. They amplify what a small team can operate — they don't replace judgment, ownership, or collaboration.

StaffOps works with or without AI assistance. The knowledge and patterns we document are valuable independently of how they were produced.

Pragmatism over purity

We ship working solutions first, optimize second, and document always. A working tool that solves a real problem is better than a perfect architecture that never ships.

Reproducible and self-sufficient

Any person should be able to clone a StaffOps repository and get it running without depending on the original authors. This means:

  • Dependencies are explicit and versioned
  • Configuration is documented
  • There are no implicit tribal knowledge requirements

Read-only by default

Automation that touches production infrastructure is dangerous. All StaffOps agents and tools operate in read-only mode by default. Write operations require explicit opt-in, human approval, and audit trails.

Licensed for everyone

All StaffOps projects are licensed under Apache 2.0. This allows commercial use, modification, and distribution — with or without attribution. Copyright belongs to StaffOps Contributors, not to any single individual or company.