Guide: Charging

From bwCloud-OS
Revision as of 09:30, 27 January 2026 by As1844 (talk | contribs) (Created page with "{| class="mw-message-box mw-message-box-warning" | style="vertical-align:middle;" | '''⚠️ Please Note:''' This page is currently under development but kept up to date. |} All consumptions within the bwCloud-OS will generate costs the home organizations need to play. == Contract relationship bwCloud-OS == thumb|Contract relationship compared between bwCloud-OS and other IaaS providers The contract is closed b...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
⚠️ Please Note: This page is currently under development but kept up to date.

All consumptions within the bwCloud-OS will generate costs the home organizations need to play.

Contract relationship bwCloud-OS

Contract relationship compared between bwCloud-OS and other IaaS providers

The contract is closed between the bwCloud-OS and the institutes (customers), as illustrated in the picture. Due to this, one bill will be sent to the customer, including all generated costs from members/ projects related to this institute. Therefore, it is possible that an additional organizational or technical process within each institution may be necessary to manage the accounting relationship between the institution and its members.

Cost generation

A registered user can generate costs like follwing:

  1. A user brings a quota entitlement/ eligibility and requests a projects with quota.
  2. The project will be created, quota set, and members added.
  3. Every existing VM and volume will produce costs within this project.