Skip to content

Commit 36c2e09

Browse files
authored
Overhaul billing page (#78)
* Overhaul billing page
1 parent bc6afad commit 36c2e09

File tree

3 files changed

+140
-102
lines changed

3 files changed

+140
-102
lines changed

docs/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -154,6 +154,7 @@ for improvements], and [source code contributions], are always welcome. {fab}`gi
154154

155155
Quick Start <tutorials/quick-start>
156156
Services <reference/services>
157+
Billing <reference/billing>
157158
Manage <howtos/index>
158159
Web Console <reference/overview>
159160
Croud CLI <tutorials/deploy/croud>

docs/reference/billing.md

Lines changed: 139 additions & 101 deletions
Original file line numberDiff line numberDiff line change
@@ -1,106 +1,144 @@
11
(reference-billing)=
22
# Billing
33

4-
This page documents the way billing and related subjects are handled by
5-
CrateDB Cloud. Since - depending on your chosen offer - billing and
6-
payment forms may appear in different places across the CrateDB Cloud
7-
interface, this guide should function as a single reference document for
8-
finding the information you need about billing, invoicing, and payments.
9-
10-
Your current accumulated bill can be always found under the billing tab
11-
in Organization section:
12-
13-
![Cloud Console billing meter](../_assets/img/billing-meter.png)
14-
15-
(billing-principles)=
16-
## Billing principles
17-
18-
CrateDB Cloud has three general principles for billing. Firstly, we only
19-
ever bill actual usage of any of the provided services. This means there
20-
are no flat fees or minimum payments.
21-
22-
Secondly, we only bill for a given period. This means any usage costs
23-
are rounded up to the nearest hour of use for Marketplace customers and
24-
to the nearest minute of use for customers directly deploying via the
25-
CrateDB Cloud Console.
26-
27-
Thirdly, Billing is done in $0.001 increments for the compute + storage
28-
usage.
29-
30-
(billing-info)=
31-
## Billing information & Payment methods
32-
33-
Your billing information consists of your (company) address, credit card
34-
details, country of residence, VAT info, and so forth. This information
35-
can be filled out whenever you make use of an offer on CrateDB Cloud
36-
that is not free (when you only use a free offer, the billing info page
37-
will not be visible to you). There are several ways you can provide the
38-
necessary billing information:
39-
40-
- You can add a new payment method even without deploying a new
41-
cluster. Simply navigate to the payment methods tab in the
42-
Organization section. You can then use this payment method when
43-
deploying a cluster later.
44-
- As part of deploying a cluster for a new organization. If you deploy
45-
a cluster that is not free, you will be prompted for your billing
46-
information as part of the configuration wizard.
47-
- By using the Billing tab in the Organization overview of the CrateDB
48-
Cloud Console. If you have a promoted cluster deployed and the free
49-
period expires, you can find the Billing tab by going to the
50-
Organization overview and clicking the fifth tab from the left. Here
51-
you can enter your billing details and your billing method (credit
52-
card). See the {ref}`CrateDB Console
53-
walkthrough <overview-org-billing>` for more information.
54-
55-
Address information, along with the payment methods can be edited in the
56-
payment methods tab, in Organization section:
57-
58-
![Cloud Console payment methods](../_assets/img/payment-methods2.png)
59-
60-
(billing-invoicing)=
61-
## Invoicing
62-
63-
Invoicing is handled variously depending on which deployment method you
64-
use. If you deploy your cluster directly via the CrateDB Cloud Console,
65-
you will be invoiced at the email address you provided when
66-
{ref}`signing up with CrateDB Cloud. <quick-start>`
67-
68-
If you use one of the marketplace offers, the invoicing is handled by
69-
the marketplace provider in question and will be part of your general
70-
invoicing for services via that marketplace.
71-
72-
Currently, for direct deployments, VAT charges for EU customers are
73-
handled by CrateDB and are added to the invoices described above. For
74-
deployments via the marketplaces, any VAT charges due are handled by the
75-
respective marketplace owners (Microsoft Azure and AWS).
76-
77-
(billing-custom-contract)=
78-
## Custom contract
79-
80-
Crate also offers a special type of payment method suited for large
81-
customers that don't want to use a credit card or marketplace
82-
subscriptions (AWS/Azure). With this type of subscription, a contract is
83-
created directly with Crate.
84-
85-
![Custom contract payment option](../_assets/img/custom-contract.png)
86-
87-
:::{note}
88-
This type of payment method does not show up in your Cloud console
89-
automatically as it needs to be configured specifically for every
90-
customer.
91-
92-
If you're interested in this option, don't hesitate and contact us at
93-
4+
CrateDB Cloud offers flexible billing options to accommodate various needs and
5+
preferences. We only bill for actual usage of services, meaning there are no
6+
flat fees or minimum payments.
7+
8+
## Billing Information
9+
10+
In the Billing tab under the Organization overview, you can add and edit your
11+
billing information, including your company address, country of residence, VAT
12+
info, invoice email, phone contacts, and more. You need to fill out this
13+
information whenever you use a paid offer on CrateDB Cloud, regardless of the
14+
payment method.
15+
16+
17+
## Subscriptions
18+
19+
After adding your billing information, you can add a subscription (payment
20+
method). We currently support the following payment methods:
21+
22+
- **Cloud Marketplaces**: Available on [AWS](https://aws.amazon.com/marketplace/pp/prodview-l7rqf2xpeaubk),
23+
[Azure](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/crate.cratedbcloud),
24+
and [GCP](https://console.cloud.google.com/marketplace/product/cratedb-public/cratedb-gcp) Marketplaces.
25+
- **Credit Card**: Available worldwide. We use Stripe as our payment provider.
26+
- **Bank Transfer**: Available in the EU. We use Stripe as our payment provider.
27+
- **Custom Contract**: For large individual deployments, [contact](https://cratedb.com/contact) our sales team.
28+
29+
:::{tip}
30+
**Marketplace Committed Spend:** All three marketplace offerings
31+
(AWS, Azure, GCP) can be applied towards any committed spend agreement (e.g., MACC)
32+
you have with the cloud provider. This effectively reduces your committed spend
33+
balance and allows you to use CrateDB as if it were a native service provided by
34+
the cloud provider.
35+
:::
36+
37+
### Setup New Subscription
38+
39+
::::{tab} Cloud Marketplaces
40+
<br>
41+
42+
1. Register for an account on the [CrateDB Cloud sign-in page](https://console.cratedb.cloud/).
43+
2. Navigate to the **"Billing"** tab on the right side.
44+
3. Add your billing information.
45+
4. Click on **"Add Payment Method"**.
46+
5. Select your preferred cloud marketplace.
47+
6. Follow the instructions to sign up for **CrateDB Cloud** through the selected marketplace.
48+
7. After completing the subscription in the marketplace, you will be redirected to CrateDB Cloud.
49+
8. Connect one of your organizations to the created marketplace SaaS subscription.
50+
51+
**You are now ready to deploy a cluster.**
52+
53+
When you deploy a cluster, the usage will be reported regularly to the
54+
marketplace as usage amount in USD, and it will appear on your regular cloud
55+
provider's invoice. Depending on your settlement currency, a conversion may be
56+
applied.
57+
::::
58+
59+
::::{tab} Credit Card
60+
<br>
61+
62+
1. Register for an account on the [CrateDB Cloud sign-in page](https://console.cratedb.cloud/).
63+
2. Navigate to the **"Billing"** tab on the right side.
64+
3. Add your billing information.
65+
4. Click on **"Add susbscription"**.
66+
5. Click on **"Pay with credit or debit card"**.
67+
6. Fill out the required information and click **"Save"**.
68+
69+
**You are now ready to deploy a cluster.**
70+
71+
The payment cycle is monthly and aligns with the calendar month. You will be charged
72+
for the previous period's usage and will receive an invoice at the email address
73+
you provided. If needed, you can add a new credit card to replace the current one.
74+
::::
75+
76+
::::{tab} Bank Transfer
77+
<br>
78+
79+
1. Register for an account on the [CrateDB Cloud sign-in page](https://console.cratedb.cloud/).
80+
2. Navigate to the **"Billing"** tab on the right side.
81+
3. Add your billing information.
82+
4. Click on **"Add Payment Method"**.
83+
5. Click on **"Ask to enable"** next to **"Pay via Bank Transfer"**. Complete
84+
the form, and our team will contact you to process your request.
85+
86+
**After** your request has been approved:
87+
88+
1. Click on **"Add Payment Method"**.
89+
2. Click on **"Pay via Bank Transfer"**.
90+
91+
**You are now ready to deploy a cluster.**
92+
93+
The payment cycle is monthly and aligns with the calendar month. You will be charged
94+
for the previous period's usage, and an invoice will be sent to the email address
95+
you provided. Payment is due within the specified terms.
96+
97+
:::{caution}
98+
**Bank transfer payment is currently available only within the EU.**
99+
100+
These payments are processed by Stripe and invoiced in Euros at a fixed USD/EUR
101+
exchange rate. You can find the current exchange rate within the CrateDB Cloud
102+
Console after setting up the bank transfer payment method.
94103
:::
95104

96-
## Payment processing {#billing-processing}
97-
98-
For clusters deployed in the {ref}`regular way
99-
<cluster-deployment-stripe>`, using the
100-
CrateDB Console cluster deployment route, payment processing is handled
101-
by [Stripe](https://stripe.com/). For clusters deployed through the
102-
[Microsoft Azure
103-
Marketplace](https://portal.azure.com/#create/crate.cratedbcloud/preview)
104-
and the [AWS
105-
Marketplace](https://aws.amazon.com/marketplace/pp/B089M4B1ND), payment
106-
is handled by Stripe on behalf of the respective marketplaces.
105+
::::
106+
107+
::::{tab} Custom Contract
108+
<br>
109+
110+
Custom contracts are individually tailored to your needs. Please
111+
[contact](https://cratedb.com/contact) our sales team to set up a custom contract
112+
that fits your requirements.
113+
::::
114+
115+
116+
## Usage Reporting
117+
118+
Whenever you use a paid offer in CrateDB Cloud, we collect your usage
119+
information, including the cluster compute and storage size and the number of
120+
nodes deployed. You can view this usage in the CrateDB Cloud Console, where
121+
you'll find a usage snapshot for the current calendar month, the current cost
122+
for the deployed service, and any available credits that might be applied to
123+
the current usage period. Be aware that the billing period might deviate from
124+
the shown calendar month usage.
125+
126+
127+
## Credits
128+
129+
Credits are another way to pay for CrateDB Cloud services and can be used together
130+
with other payment methods. Credits are applied to your account and are used up
131+
first before any other payment method is charged. This means that if credits are
132+
available, you will not be charged, nor will any usage be reported to your
133+
payment provider. You can see the remaining credits and their validity date on
134+
the Billing and Usage page.
135+
136+
There is also the option to purchase more credits at a discount by
137+
[contacting](https://cratedb.com/contact) our sales team.
138+
139+
:::{tip}
140+
**Free Trial Credits**: If you just signed up, you have the option to enable
141+
$200 of credits that can be used for any paid cluster. To enable these credits,
142+
you need to provide a valid payment method, which will only be charged if you
143+
have used up your credits.
144+
:::

docs/reference/index.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,6 @@ NoSQL with the power and simplicity of standard SQL.
1313
:maxdepth: 1
1414

1515
User Roles <user-roles>
16-
Billing <billing>
1716
API <api>
1817
Glossary <glossary>
1918
:::

0 commit comments

Comments
 (0)