Docs Search docs

Legal

Short version: HoBo is MIT-licensed open source, this site collects nothing, and every third-party product named here belongs to its own owner.

Licence

HoBo is released under the MIT Licence. The authoritative text is LICENSE in the repository, and it travels with every published HoBo distribution.

The licence includes a warranty disclaimer and limitation of liability. Those terms govern — nothing on this site adds to, narrows, or replaces them.

This website

This site is a static build served by GitHub Pages. It runs no analytics, sets no cookies, embeds no tracking pixels, and contains no forms. It does not collect, store, or share anything about you.

The one thing that does happen is outside our hands: GitHub serves these pages and keeps its own server logs of the requests. That processing is GitHub’s, described in the GitHub Privacy Statement.

If HoBo later offers a hosted product, it will carry its own terms of service, privacy notice, and data-processing agreement. Those do not exist yet, and nothing on this site should be read as them.

Pre-release status

HoBo is pre-release. The surfaces documented on this site are the contract the product is being built to, not a description of shipped, supported software. Some documented capabilities are design-pinned rather than implemented; the trail map is the honest breakdown. Nothing here is a warranty, a service-level commitment, or a compliance certification.

We do not claim SOC 2, ISO 27001, GDPR, HIPAA, PCI, or any other certification.

Trademarks

All third-party product and company names mentioned on this site or in the HoBo repository — including GitHub, Blacksmith, Depot, Namespace, BuildJet, Actuated, WarpBuild, Ubicloud, RunsOn, Cirun, Cirrus, Amazon Web Services, Microsoft Azure, Google Cloud, Cloudflare, Vercel, Pulumi, Terraform, Crossplane, Argo, and Open Policy Agent — are the trademarks or registered trademarks of their respective owners.

HoBo names these products only to describe interoperating with them. HoBo is not affiliated with, endorsed by, sponsored by, or certified by any of them.

Using HoBo with third-party providers

HoBo routes work to the cloud and CI providers you register, using credentials you supply for accounts you hold. Your own agreement with each provider governs that usage, including its free-tier and acceptable-use terms.

HoBo never holds a provider account on your behalf, never pools or resells free-tier capacity across users, and never creates or rotates accounts to reset a free tier. That boundary is a recorded architectural decision, not just a practice. See the trail map.

Contact

Security reports follow SECURITY.md. Everything else: open an issue.