Your Subscription
A subscription belongs to a team, and a new account is a team of one. You create the account and subscribe on the BYODt Portal. The portal's Deployment page then holds what your deployment needs to connect.
Before you start
| Prerequisite | Why |
|---|---|
| A business | We sell to businesses only. Before a team's first purchase you give its business details, and its tax number is checked against the register that issued it, where one can be asked. No payment is taken while a check waits. Every purchase is made under our terms of service. |
| A payment card | You pay by card, through Stripe. |
You do not need a running deployment to subscribe. The software is free, and the subscription buys the content it mounts.
Create an account
- On the BYODt Portal, click Create an account.
- Sign up with an email address and a password, or with Google.
- On your first sign-in, accept the terms.
You now have a team of one: yours.
Subscribe
- Open Catalog.
- Click Subscribe on the package you want. A team that already subscribes adds a package with Add to subscription instead.
- Before your team's first purchase, give its business details. The tax number is checked as described above.
- Pay by card, through Stripe. You return to the portal's Billing page.
With Add to subscription, no payment page opens: your saved payment method is used, and the charge appears on your next invoice.
Give it a few seconds. Entitlement follows Stripe's confirmation rather than the redirect back, so the Billing page can say the subscription is still being confirmed. It updates on its own once it is. When the subscription is in place it reads, for example:
Your subscription is active. Your deployment picks it up within about a minute.
When the page knows which package you bought, it names the package in place of "Your subscription".
A connected deployment needs nothing redone. It reads your subscription as it needs it, so a package you subscribe to later is available to it without reconnecting. Click Refresh on the console's Content tab to mount it: see Refresh.
Buying a team edition creates a new team. It does not move a deployment you already run. Read Moving a deployment to a new team before you choose what to do with it.
Where your deployment's values are
The portal's Deployment page holds what your deployment needs from the portal, one block per team. Its numbered sections match the numbers on the console's Cloud tab, so you can work through the two side by side.
| Section | What it holds | Who sees it |
|---|---|---|
| Before you start | Where to download the bundle, and the commands that start it. | Everyone on the team |
| 1 · Access and callbacks | The team's deployment access, and the Callback URLs you paste from the console. | The team's owner |
| 2 · Configuration | The recipe: the Environment block you paste into the console. | Everyone on the team |
| 3 · Team | Who is on the team: members, roles and invitations. | The team's owner |
| 4 · Software | The software your packages include. Shown only when one of them includes any. | Everyone on the team |
Sections 1 and 3 are the owner's alone, so another member sees Configuration and Software without their numbers.
What to do with the callbacks and the recipe on the console side is in Connecting the deployment to the cloud. Section 3 · Team on the portal and section 3 · Who may sign in on the console are different decisions: selecting someone on the console is not inviting them to the team. See Changing who may sign in.
Related
- Moving a deployment to a new team — after you buy a team edition.
- Check the connection — three checks that tell you the subscription reaches your deployment.