1.6 KiB
weight, title, description, icon, date, lastmod, draft, toc
| weight | title | description | icon | date | lastmod | draft | toc |
|---|---|---|---|---|---|---|---|
| 220 | Bundles | article | 2025-08-25T12:39:03-06:00 | 2025-08-25T12:39:03-06:00 | false | true |
Bundles are great ways to package software for use by a type of business, a size of business, or a job function, among many other go-to-market motivations for bundling software.
The Federated Core Provisioner can spin up Federated Cores based on a software manifest that can be created "just in time" or based on a predefined collection of software and virtual machine. This allows you to fully manage the the expects margins for a sale.
You can even specify ranges of virtual machines depending on the type of cloud to which you are provisioning. For example: you may want to package one set of software for your Ampere-based Cores, versus another set of software based on X64-based Cores.
Further, bundles are useful to introduce more software to a customer and incentivize him to try more functionality. You may discover, in time, that, for example, customers purchasing CRM (EspoECRM) also want Mailing List management. You can build a bundle called "Digital Marketing" and sell that to customers with it defined as a bundle in Federated Core Platform.
Technically, bundles are simply a software dependency tree. You define them for provisioner using a YAML file such as:
[Good]
Mini # not required. always inferred.
Nextcloud
Nextcloud-Talk
Wordpress
Valutwarden
Headscale
Simple-VPN
Thereafter, you only need to call "Good" to provision a Core with the specified software.