Contact

Contact Us

We would be glad to hear from you. If your team is trying to understand what open source you depend on, decide what to adopt, prepare for SBOM or compliance review, make a governance path easier to follow, evaluate AI tooling, or work with an ecosystem you rely on, send a short note and we can talk through a useful first step.

General inquiries: howdy@therangergroup.org

What to send

A short note is enough.

  • The decision, review, or policy gap in front of your team
  • Whether this involves dependency visibility, SBOMs, adoption, governance, contribution, AI tooling, community, or stewardship
  • Any timeline, procurement process, grant requirement, or internal review that matters

What happens next

We clarify the shape of the work.

We will read what you send, clarify the shape of the work, and suggest a practical next step. That may be a focused assessment, a small pilot, a practice review, a stewardship planning conversation, or a note that another path would serve you better.

Engagement shape

We scope around the first useful step.

We do not publish a fixed rate card because the right scope depends on the decision, stakeholders, timeline, procurement path, and deliverable your team actually needs. We will clarify the shape of the work before proposing a budget.

Understand

A short, fixed-scope review of an open source dependency question, SBOM need, AI tooling concern, or ecosystem risk.

Adopt

A small evaluation or decision-support pilot for a project, tool, framework, vendor path, or shared component.

Sustain

Practical help turning policy into ownership, review paths, workflows, training, and operating routines.

Steward

A focused plan for contribution, maintainer support, sponsorship, peer collaboration, or shared investment.

Comfortable starting small.

For state, local, education, and government-adjacent teams, a pilot, assessment, or limited purchase order can be a better first step than a broad proposal. We aim to be a practical partner: understand the procurement context, communicate value to both technical and non-technical stakeholders, and avoid asking teams to buy more than they are ready to use.

We work with public sector teams, universities, nonprofits, civic technology groups, government contractors, and mission-driven enterprises. Public-sector teams can also review the state and local open source readiness path.

Not ready to reach out?

Start with the dependency guide.

The guide can help your team gather useful context when a dependency, compliance review, adoption decision, SBOM conversation, governance effort, stewardship question, or AI tooling evaluation becomes important.

Read the guide

AI questions

Looking at AI tooling or provider choices?

Review the AI and open source governance path if the decision involves models, frameworks, dependencies, licensing, procurement, or internal use policy.

View the AI path