BrandForge for HestiaCP
An open-source HestiaCP plugin for BrandForge provisioning, built with the community.
Open source
MIT
Community
Supported
84
Languages
Full lifecycle
Every event
How BrandForge fits HestiaCP
Native HestiaCP plugin
A proper HestiaCP plugin. Provisioning, suspension, and termination all go through it.
Open source
Source is public. Fork, extend, or contribute back. Pull requests welcome.
White-label experience
Customers see your domain, logo, colours, and SSL. The BrandForge name never appears.
SSO from HestiaCP
Customers log into HestiaCP and step into BrandForge without a second login.
From cart to brand kit
-
Customer opens HestiaCP
The BrandForge plugin appears in the HestiaCP interface.
-
Click to launch BrandForge
One-click SSO takes the customer into your white-labelled BrandForge instance.
-
Brand kit is generated
The customer creates their brand assets inside your BrandForge.
-
Provisioning syncs with Hestia
User creation in HestiaCP can auto-provision a BrandForge account.
Under the hood
Setup
A handful of steps to go from install to first sale.
-
Register interest
Let us know you want it so we build it against real needs.
-
Clone from GitHub
When released, clone the repository into the HestiaCP plugins directory.
-
Add your API key
Enter your BrandForge API key from the partner portal.
-
Configure per package
Map each HestiaCP package to a BrandForge plan tier.
-
Enable and go live
New HestiaCP users get BrandForge access with SSO.
Who this is for
Open-source hosting community members and self-hosters running HestiaCP who want an integration they can read, fork, and contribute to.
- HestiaCP 1.8 or later
- Root or admin access
- BrandForge partner plan (any tier)
- Outbound HTTPS to api.brandforge.com
Integration FAQ
When will the HestiaCP plugin be live?
It is planned. Register interest and we prioritise the build based on demand from the community.
Will it be open source?
Yes. The plugin will ship on GitHub under an open licence. Fork, extend, and contribute back.
Can I self-support it?
Yes. Source is public, API is documented, and the community can maintain it alongside BrandForge.
Is the customer experience white-labelled?
Yes. Customers see your domain, logo, colours, and SSL. The BrandForge name never appears.
Does SSO work securely?
Yes. SSO uses signed short-lived tokens scoped to the customer's HestiaCP user.
Who handles customer support?
You handle L1 with your customers. BrandForge handles L2 and L3 platform issues for partners.
Open-source BrandForge for HestiaCP
Register interest so we prioritise the build. Community-supported, GitHub-hosted, free forever.
- Open source
- Community-supported
- Free for partners
- GitHub-hosted