Support
vespid-ai does not run a polished public sponsorship program yet, but support is welcome.
Current support paths
Section titled “Current support paths”Fund a specific milestone
Section titled “Fund a specific milestone”If you want to support the work financially, the best path right now is to start with a scoped conversation rather than a generic donation button.
Use GitHub Discussions in vespid-ai/vespid-ai to propose:
- sponsorship of a specific repository milestone
- implementation of a particular integration or workflow
- documentation or launch work that would unblock adoption
- advisory or architecture support around agent runtime, authorization, or operator portability
Contribute without funding
Section titled “Contribute without funding”You can also help by contributing:
- bug reports with real reproduction details
- documentation fixes and examples
- issue triage and implementation feedback
- discussion threads that sharpen the product and trust model
What support is most useful
Section titled “What support is most useful”The highest-leverage help is support that improves the real execution boundary of the stack:
- runtime control and protected actions in
vespid - delegated authorization flows in
skillauth - profile portability and sanitization in
hermes-profile-sync - public docs and launch surfaces in
vespid-ai
Expectation setting
Section titled “Expectation setting”If you open a support or sponsorship thread, include:
- the repository or milestone you care about
- the use case you want unlocked
- whether the need is open-source, internal tooling, or commercial deployment
- any timing or budget constraint that matters
That keeps the discussion concrete and lets support map to real work instead of generic “please sponsor” copy.