Pabawi Support and Sponsorship

Two ways to work with Pabawi

Pabawi is a self-hosted, open source web interface for Puppet, OpenVox, Bolt, Ansible, SSH, PuppetDB, Hiera, Proxmox, AWS, and Azure. It’s free to run and Apache 2.0 licensed. This service covers the two things that fall outside “download it and read the docs”: getting it working in your specific environment, and keeping it maintained if your infrastructure depends on it.

Support: getting Pabawi running in your environment

• Installation and first integration. Setting up Pabawi against your actual PuppetDB, Puppet Server or OpenVox Server, Bolt inventory, Ansible inventory, or SSH estate — not the demo dataset.
• Multi-source inventory design. Deciding how nodes from PuppetDB, Ansible, SSH, and cloud/hypervisor sources should merge, group, and deduplicate for your topology.
• RBAC and command whitelisting. Setting up per-operation permissions, JWT sessions, and command whitelists so delegated access matches your actual security requirements.
• Provisioning integrations. Connecting Proxmox, AWS EC2, or Azure provisioning to the configuration-management side so new nodes land in inventory already managed.
• Custom extensions and models. Pabawi’s model and extension system is built to be extended; if you need an integration that doesn’t exist yet, it can usually be built rather than worked around.
• Upgrade assistance. Moving between Pabawi versions without losing custom configuration, extensions, or RBAC setup.

Sponsorship: for teams that already depend on Pabawi

If Pabawi is already running in your production environment, a sponsorship is a way to fund its continued development instead of treating it as a free dependency with no relationship attached. Sponsorship can take a few shapes:

• Ongoing sponsorship. A recurring arrangement that funds maintenance and gives you a direct line for questions and priority attention on issues that affect you.
• Roadmap sponsorship. Funding a specific integration or feature — a provisioning target, a monitoring integration, an authentication method — and having it prioritized on the public roadmap.
• One-time development sponsorship. A single funded milestone, for example hardening a specific integration for production use ahead of the general release.

None of this changes the license or creates a private fork: sponsored work lands in the open source project, same as everything else.

What to send

For support requests: what you’re running (Puppet or OpenVox, PuppetDB version, Bolt/Ansible if relevant), what you’re trying to connect, and what “done” looks like for you.

For sponsorship: roughly how you’re using Pabawi today, the scale of your infrastructure, and whether you have a specific roadmap item in mind or want general ongoing support.