Deploy your first app
This guide is for apps hosted on Caliber Node. You need an active Cloud Apps subscription with enough available CPU, RAM, and disk for your chosen app.
If you have not purchased capacity yet, open Cloud App subscriptions. For an explanation of how apps share a plan, read How Cloud Apps subscriptions work.
1. Choose your app
Open Deploy a Cloud App.
If you see Where should this app run?, select Caliber Node hosting. The Your own server option is for BYOH deployments.
Browse or search the catalog and select your app. Read its setup notes and resource requirements, then continue to the configuration step. An app marked as coming soon cannot be deployed yet.
2. Select a subscription and location
Choose the subscription that should provide this app's resources. If you have several, check the Available capacity shown on each one. A single app cannot combine unused capacity from separate subscriptions.
Choose a location from the available regions. Review any regional transfer information shown. If you attach a purchased dedicated IP, the app's host and region are fixed by that address.
3. Assign resources
Set the app's CPU, RAM, and disk allocation. The meters show how much is available from the selected subscription.
- Follow the app's recommended sizing and any app-specific setup notes.
- Leave capacity for other apps if you plan to deploy more later.
- Choose disk space carefully: it can be increased later, but cannot be reduced after deployment.
If the form reports that the allocation exceeds your available capacity, reduce it only if the app can run within the smaller allocation, select another subscription, or add capacity.
The panel may let you choose less than the app's recommended resources. That does not guarantee the app will start or run reliably with that allocation.
4. Choose networking and an address
For an ordinary public web app, keep the default protected connection unless you specifically need another networking option. Apps requiring a dedicated IP will show that requirement; choose a compatible address before continuing.
Under Name and address, enter a name and choose an available subdomain. Check the Deploys to preview for the actual address. Depending on the connection, it may include a host segment as well as the name you selected.
Most apps can have a custom domain added after deployment. If the form offers a permanent custom domain, decide before deploying and follow the DNS instructions shown there. Those apps cannot use the usual later domain-change workflow.
5. Review and deploy
Continue to Review. Check the selected app, subscription, location, resources, and address, then click Deploy app.
The deployment itself is covered by your active subscription when it fits within your available capacity; there is no additional checkout for that deployment. Separately purchased add-ons are not included in that statement.
6. Open the app
Wait for provisioning to finish on the app's page, then use Open app. Complete any first-run setup requested by the application. Login and setup requirements vary between apps, so follow the instructions shown for that app.
If it does not start, check its status and logs in the panel. Look for a resource shortage, missing configuration, or an app-specific setup error before trying another deployment. Avoid deleting an app containing data just to retry setup.
For help, send support the app name and the relevant error message, with passwords and tokens removed.
Next: Connect a custom domain.