SUSTAIN THE OPEN-SOURCE LAYER

Support DirectSpool

Sponsorship profile and public repositories are pending setup. This page is a funding proposal and does not collect payments.

What we're building

DirectSpool is a local-first bridge between modern web applications and printers, scales, scanners, cash drawers and related hardware. A small native Windows agent has already produced physical multi-line thermal test receipts and includes secure local access patterns. Our public-source focus will be SDKs, browser integrations, examples, compatibility profiles and documentation.

Why sponsor?

Businesses and developers repeatedly spend time solving browser-to-hardware connectivity and printer compatibility. Sponsorship helps fund reusable developer tools, validated printer reports, documentation, example POS integrations, security maintenance, and contributor support.

Hybrid model transparency

Our Rust agent core is proprietary, while independently licensed SDKs and browser connectors are planned as public open-source projects. Sponsorship supports the genuinely public contributions, not an assertion that the entire product is open-source. Business Cloud will offer optional paid fleet services.

Proposed funding tiers

Monthly tierIntended benefit
$5 — CommunitySupport documentation and compatibility work.
$25 — DeveloperSupport SDK examples, tests and bug triage.
$100+ — OrganizationSupport public device compatibility and open-source maintenance.

These amounts are proposals only; actual tiers and rewards will depend on GitHub Sponsors approval. No support SLA or special licensing rights are implied.

Corporate collaboration opportunities

Thermal and label printer manufacturers, POS/ERP vendors, retail integrators and hardware distributors can sponsor independent compatibility work, provide test hardware or fund open integration examples. Any sponsored test results should be transparently labeled and not presented as unbiased certification without evidence.

What remains before public sponsor onboarding

  1. Audit publishable SDK/connectors and remove secrets/internal code.
  2. Choose open-source licenses and add README, security policy, contributing guide, license notices and usable examples.
  3. Create public repositories with demonstrable commits and releases.
  4. Enable GitHub account 2FA, apply for Sponsors, complete approved bank and tax information privately.
  5. Publish approved Sponsor URL and tested download links only after they exist.

About GitHub Sponsors →