Sell VMs from your own Proxmox clusters
Nebla's open core is multi-tenant from the start, so you can put customers on your hardware today. A commercial module for billing and branding is in development.
In the open core today
- Projects and members
- Each customer gets projects with their own members and roles. They see their own servers and nothing else.
- Quotas
- Cap servers, vCPU, memory, disk and IPs per project, with defaults for new projects and a limit on how many projects one user can own.
- Isolation between tenants
- The Proxmox firewall filters each server by its own IPs and MAC address. The console proxy checks project membership on every connection.
- Invites and sign-up control
- Invite customers by link or email. Open sign-up stays off unless you turn it on.
- Scoped API tokens
- Customers automate their own project with read-only or read-write tokens, with rate limits per token.
- Many clusters, one panel
- Add each Proxmox cluster or standalone node as a location. Customers pick a location and Nebla handles placement.
The reseller module
A commercial add-on for hosting businesses. It is a separate build on top of the open core, activated with a licence key, so the core stays complete for everyone else.
It is still in development. Follow the project on GitHub to hear when it is ready.
Billing integration
Events for servers created, deleted and resized, plus hourly usage, sent to your billing system.
Customer self-signup
A sign-up flow that replaces the built-in invite-only model.
White-label branding
Your logo, colours, product name and domain on the panel.
Usage metering
Per-project records of what ran and for how long.
Resellers and sub-customers
A hierarchy for resellers who manage their own customers.