|Pivotal Web Services (PWS)
This article contains Frequently Asked Questions relating to the general usage and billing of the Pivotal Web Services Platform.
Q: Can we get usage report on orgs basis?
Example: "Let’s assume I have 2 Orgs and both Orgs are running 5+ apps. Is it possible to get the usage report separately for each org? If so, how can I get the usage report?"
A: Billing is done on an org by Org basis. One can go to the billing page and see a full breakdown of the charges on a space by space basis. The charges will be listed based on individual application usage and any services in each space.
Q: Is there any limitation on creating orgs and spaces on PWS?
A: There is no limit on creating Orgs on PWS as long as there is a valid credit card listed on file with each org. The credit card will be charged each month for the app usage and services consumed or subscribed for that org. There is no practical limit on the number of spaces that are created within an org.
Q: Do we have any app instance limit, if we are hosting it on Pivotal?
A: Each app instance should not be larger than 4 GB for reliable placement on deploys. It is possible to deploy larger apps on PWS, however there is no support provided for app instances larger than 4 GB and behavior may be unpredictable.
Q: Do we have any other payment option apart from credit card?
At this time credit cards are the only payment form for paying for PWS. If you desire other options for payment, please consider Pivotal Cloud Foundry by contacting our Pivotal Sales department (email@example.com
Q: If we have multiple user accounts under one Org, can we have billing details for all 10 user accounts or only for main user account.
A: Billing details are aggregated on the Org level not on the user level, as users may exist in multiple orgs. Within an Org, billing breakdowns are organized by the spaces within an Org. If one wishes to track usage per user for billing purposes, it's possible to assign a user to an Org or a user to a specific space. Pivotal Cloud Foundry (which is the base for PWS) can restrict deployment capabilities within a space. This ensures that charges within a space are that of the user.