Skip to content
Digital Nestby Ulises Jeremias

Digital Nest · sponsor & partner

Support the work behind Digital Nest

I maintain open-source developer tooling across four areas: agent tooling for coding assistants, a Linux desktop, scientific computing for V, and app scaffolding. Sponsorship buys time for maintenance, testing, and integrations — it never buys a recommendation.

Sponsor on GitHub (opens in new tab)Discuss a partnershipExplore the work

Partnerships start with an email to ulisescf.24@gmail.com. There are no fixed packages; GitHub Sponsors handles individual support.

where support goes
Project areas and the work that support can help enable
AreaCan help enable
Agentic Developer Stackassistant compatibility · desktop + local API · integrations
Hornero Linux Desktophardware testing · installer work · packaging
Create Awesomeplatform templates · template CI · examples
V ecosystem worknumerics + GPU · autograd · CI tooling

the projects exist without sponsorship; support can create more time for maintenance, testing, and hardware

Why sponsor

What support pays for

  • Maintenance and releases

    Triage, dependency updates, security fixes, and release work across the active repositories.

  • Compatibility testing

    Keeping skills, templates, and desktops working as assistants, runtimes, and Linux packages move.

  • Hardware and CI

    Test devices for the Linux desktop work, plus CI minutes and release infrastructure.

  • Packaging and distribution

    npm, PyPI, AUR, Homebrew, container, and binary channels that stay in sync with releases.

  • Documentation

    Install guides, architecture notes, ADRs, and examples that let people adopt the tools without help.

  • Community time

    Reviewing contributions, answering questions, and mentoring first-time contributors.

Areas you can support

Four bodies of work

Support can go to the work in general or to one area. Each area lists what support enables and the kinds of organizations that tend to be a good fit — categories, not a list of sponsors.

Agentic Developer Stack

Agent Toolkit · Agentic Workstation · Agentic Harness

Portable skills, agents, loops, and MCP templates for many coding assistants, with a native CLI, local API, and desktop app — plus machine provisioning and a persistent workspace.

Support enables

  • Compatibility work as coding assistants change their plugin, skill, and MCP formats
  • Desktop app and local API development
  • Provider, observability, and evaluation integrations
  • Packaging across npm, PyPI, AUR, Homebrew, and plugin marketplaces
  • Regression testing of skills, loops, and swarm recipes

Good fit for

  • Coding-agent and AI IDE teams
  • Model and API providers
  • Evaluation and observability platforms
  • Developer-tool and infrastructure platforms
Read about Agentic Developer Stack

Hornero Linux Desktop

HorneroConfig · Hornero OS

HorneroConfig, a long-running Hyprland and Quickshell desktop configuration, and Hornero OS, an early-stage Arch-based desktop OS extracted from it.

Scope: Hornero OS is a development preview: there is no installer or ISO yet. Support goes to building it, not to a shipped distribution.

Support enables

  • Testing on real laptops and desktops, including ARM devices
  • A hardware compatibility record for Wayland, Hyprland, and Quickshell
  • Installer and image work for Hornero OS
  • Packaging and reproducible configuration
  • Accessibility and visual polish of the shell

Good fit for

  • Linux laptop and desktop vendors
  • ARM and single-board computer makers
  • Linux infrastructure and mirror hosts
Read about Hornero Linux Desktop

Create Awesome

Create Awesome Node App · Create Awesome Python App · Create Awesome V App · Create Awesome Rust App

Scaffolding CLIs for Node.js, Python, V, and Rust that compose a template with extensions into a project that already builds, lints, and tests.

Support enables

  • First-class templates and extensions for real platforms
  • Keeping every template passing CI as frameworks release
  • Deploy, database, queue, and observability integrations
  • Documentation and runnable examples

Good fit for

  • Hosting and deployment platforms
  • Database and queue providers
  • Observability and email services
  • Cloud and developer-infrastructure companies
Read about Create Awesome

V ecosystem work

VSL · VTL · setup-v · RxV

VSL scientific computing, VTL tensors and autograd, setup-v for CI, and RxV reactive streams — plus contributions to the V compiler.

Scope: V, VSL, VTL, and setup-v belong to the vlang organization. Support here funds my maintenance and contribution time — it does not buy anything from the V project.

Support enables

  • Numerical correctness, benchmarks, and backend coverage in VSL
  • GPU backends (CUDA, OpenCL, Vulkan) and autograd work in VTL
  • CI tooling for V projects through setup-v
  • Examples and documentation for scientific users

Good fit for

  • Scientific-computing groups
  • Compute and GPU infrastructure providers
  • CI providers
  • Accelerator and toolchain vendors
Read about V ecosystem work

Ways to support

Two ways in

Direct support

Open-source supporter

Recurring or one-time support with no integration or promotion attached.

  • Monthly GitHub Sponsors tier
  • One-time contribution
Sponsor on GitHub (opens in new tab)

Partnerships · start with a conversation

  • Project sponsor

    Support tied to one project area, disclosed where the project is presented.

    Listing on this page · Acknowledgement in a project README or site, where agreed · Funding for a specific milestone

  • Integration partner

    For products that make a project better for its users. The work ships only if it passes normal review.

    Tested integration or extension · Template or example project · Joint technical documentation

  • Infrastructure partner

    Credits or services used directly for open-source development.

    CI minutes and runners · Model/API credits for agent testing · Hosting, storage, or observability

  • Hardware partner

    Devices donated or loaned for Linux compatibility testing.

    Laptops and desktops for Hornero testing · ARM boards · Peripherals with Linux driver gaps

  • Community partner

    Support for the open community around these projects.

    Contributor events and hackathons · Workshops on developer tooling · Community infrastructure

Discuss a partnership

Community partnerships run through the Digital Nest community — contributor events, workshops, and the shared Discord.

Signals, with caveats

A few measurable signals

Each figure comes from a public source for a stated period. Downloads count package fetches — including CI and mirrors — not people. Agent Toolkit download counts are left out until its packages have a longer history.

Create Awesome Node App npm downloads, trailing 12 months
21,722 package downloads
– · npm downloads API (opens in new tab) · retrieved
Counts every download, including CI pipelines, mirrors, and the project’s own smoke tests. Downloads are not users.
Create Awesome Python App PyPI downloads, trailing 30 days (mirrors excluded)
1,382 package downloads
– · PyPI Stats (opens in new tab) · retrieved
Includes CI and automated installs; about half fall on release days. Downloads are not users.
Create Awesome Node App Contributors besides the author
18 contributors with commits on either default branch
– · GitHub contributors API (opens in new tab) · retrieved
Union across Create-Node-App/create-node-app and Create-Node-App/cna-templates (also: https://github.com/Create-Node-App/cna-templates/graphs/contributors). Counts accounts that authored at least one commit on the default branch of either repo, excluding the author and bots. Size of contribution varies.
HorneroConfig Contributors besides the author
10 contributors with commits on the default branch
– · GitHub contributors API (opens in new tab) · retrieved
Counts accounts that authored at least one commit on the default branch, excluding the author and bots. Size of contribution varies.

Figures as of or later · refreshed by a reviewed script, never fetched live.

Sponsorship principles

What sponsorship does not buy

People adopt these tools because they trust the recommendations in them. These rules protect that.

  • Support is not endorsement

    Sponsoring a project does not mean I recommend your product, and funding does not change what the projects recommend.

  • Integrations earn their place

    An integration, template, or example ships only if it holds up to the same technical review as any other contribution.

  • Paid relationships are disclosed

    Paid and material relationships are listed on this page with their scope and dates. Sponsored links are labelled and marked rel="sponsored".

  • No hidden influence

    Sponsors do not review, edit, or veto technical writing, benchmarks, or recommendations.

  • Nothing exclusive by default

    A relationship is exclusive only when that is negotiated explicitly and disclosed.

  • Users come first

    If a relationship would compromise the trust of the people using these tools, I will not take it.

Sponsors & partners

Supporters and partners

There are no sponsors or partners yet. Early supporters will be listed here with what they support, since when, and whether the relationship is paid.

Become an early supporter (opens in new tab)

Start with whichever fits

Individual support takes a minute on GitHub Sponsors. For a company, send a short note about what you have in mind — an integration, credits, hardware, or project support — and I will reply with what is realistic.

Sponsor on GitHub (opens in new tab)Discuss a partnership