Open source
How we open source
Selective openness, pragmatic licensing, and clear contribution paths.
01
Philosophy
ASPEC RACING opens source selectively where transparency, auditability, and community improve the product for operators. We do not open-source everything by default, and we do not treat open source as marketing theatre. When a surface is public, it should be useful to run, review, and extend.
02
Contributions
Community contributions are welcome on public projects through issues, discussions, and pull requests. We favour focused changes with clear intent: bug fixes, plugin work, docs, and hardening notes over large speculative rewrites.
03
Licensing
We choose pragmatic licenses that keep the core value of each product clear. For open-core products such as VarHaven, Community stays freely licensed while Business modules sit on a commercial boundary that does not move secret data off customer infrastructure.
04
Plugins
Where products support extension, we favour documented plugin surfaces, capability boundaries, and reviewable marketplaces over closed customization paths. Operators should be able to add delivery targets and integrations without forking the core.
05
Roadmap
We share direction when it helps users plan deployments and migrations. We avoid date theatre and feature promises that outrun engineering reality. Public roadmaps describe themes and priorities, not press-release calendars.
Community
Community projects
Public projects and collaborations we share with the community.
VarHaven Community
Apache 2.0 self-hosted environment variable, secrets, and configuration management for a single organization. Console, API, CLI, delivery worker, Linux agent, and a plugin SDK.