Open Source
Public projects you can inspect, use, and follow.
Many Vib Tools projects are developed in public, from Windows utilities and self-hosted services to automation packages and reusable development frameworks.
Browse GitHubProjects
Current public open-source work.
Portable Account Browser
vibtools/PortableAccountBrowser
Portable Windows multi-account browser with isolated profiles for mail, messaging, social platforms, and everyday web apps.
ContextVault
vibtools/ContextVault
Windows app for saving fully loaded ChatGPT conversations as portable, integrity-checked, RAG-ready archives.
VibraPilot
vibtools/VibraPilot
Browser automation desktop application for workflow-driven tasks with managed sessions and Windows-focused runtime controls.
MailStack
vibtools/MailStack
Open-source, self-hosted mail server and shared team inbox for controlled receive-only business email.
Licora
vibtools/Licora
Self-hosted central license management system for software licensing, device limits, API validation, and audit operations.
InvoiceRouter for n8n
vibtools/n8n-nodes-invoicerouter
n8n community-node package for guarded provider invoice lifecycles, account allocation, retries, reporting, and workflow automation.
Vibrix
vibtools/vibrix
Reusable PySide6 desktop UI framework for building consistent, scalable, production-oriented Python applications.
Vib Project Template
vibtools/vibproject-template
Technology-neutral project structure template with clear boundaries for source, tests, documentation, scripts, assets, and internal work.
Source available in public
Browse implementation, documentation, release history, and project decisions directly in the repositories that ship the work.
Project-level licensing
Licensing is defined by each repository. Review the project license before using, redistributing, or embedding a project.
Issue-driven collaboration
Use repository issues and discussions to report problems, propose improvements, and provide reproducible technical feedback.
Contribution-ready
Where a repository accepts contributions, changes can be reviewed through normal GitHub pull-request workflows.
Contribute
Start with the repository that owns the project.
Review its README and contribution guidance, then open an issue or pull request with focused context and reproducible evidence.