Strongly Cloud
Strongly Cloud is Strongly run for you. You sign up, choose a plan, and your organization's workloads run on Strongly's cloud, paid for from your plan's credits. These pages are for the people who use a Strongly Cloud organization: its owner, its developers and its app users.
Strongly Dedicated works differently: it has no plans or credits, and nothing on these pages applies to it unless the page says so.
| Page | What it covers |
|---|---|
| Plans and sign-up | Signing up with email or Google, the Individual, Pro and Team plans, credits, and changing or canceling a plan |
| Credits | Buying credits, when purchased credits expire, the low-balance alert and auto-refill |
| Your team | Inviting developers (Team) and app users, and what each plan allows |
| Costs | What each person in your organization sees in the Cost Explorer |
| Apps on your own address | Where your apps open, and serving them at your own domain |
Your organization is yours alone
Your organization's data, files, network and apps are not visible to other organizations. People in other organizations cannot find, open, list or reach anything of yours, and you cannot reach theirs. Sharing works only inside your own organization.
- Sharing with a person reaches only people of your organization, and sharing with all users (making a project, app, data source or Library item available to everyone) reaches every user of your organization.
- Agents send messages only to agents of your organization.
- Self-hosted models are deployed in your organization, and requests to manage them carry your organization's ID in the
X-Organization-IDheader. - Work Discovery is not offered on Strongly Cloud.
Launching and running workloads
Every workload you start (an app, a workspace, a job or workflow run, an add-on, an agent, a self-hosted model) belongs to your organization and is paid from its credits:
- Without a plan, nothing can launch. Until your organization has an Individual, Pro or Team plan, every launch is refused and you are sent to Billing & Credits to choose one.
- When your credits run out, running workloads are stopped and nothing new launches until credit is added. See Credits.
Waiting for a machine
Workloads run on machines that are added as they are needed. When no machine of the size a workload asked for is free yet, the workload waits for one instead of failing, and says so:
- An app shows in its status bar that it is waiting for capacity, with the reason. An app's build does the same while there is no machine free to build on.
- A workspace shows that it is waiting for capacity while it starts.
- A job or workflow run stays Pending and shows that it is waiting for capacity.
- An add-on or a self-hosted model shows the same while it starts.
Each starts on its own as soon as a machine is free; you do not need to press anything again. In the REST API and the Python SDK the same workload carries a waiting field while it waits: reason (WaitingForCapacity) and detail, the same reason in plain words. It is absent or null once the workload is not waiting.