Create an App
Create an App from the Team that should own it. Owners, admins, and billing members can complete the purchase flow.
Before you begin
Section titled “Before you begin”Confirm that:
- you are working in the Team that should own the App;
- you know the framework and the minimum resources the workload needs;
- you can use a saved Team payment method or provide a new card and billing address.
Purchasing creates the App and starts asynchronous provisioning. It doesn’t connect a repository or deploy code from Git or Workspace.
Open App onboarding
Section titled “Open App onboarding”- Open the Team’s App list.
- Select New app.
- Wait for Configure your app to load the available plans, resource limits, frameworks, and payment methods.
If the options don’t load, select Try again. If the payment form is unavailable, refresh once; if it remains unavailable, contact support instead of submitting from another tab.
Name the App
Section titled “Name the App”App name is optional and can contain up to 100 characters. Leave it blank to use the portal’s generated identifier, or enter a short name that Team members will recognize.
Don’t put passwords, API tokens, customer records, or other secrets in the name.
Choose a resource shape
Section titled “Choose a resource shape”Select a plan preset to seed the controls, or select Custom to start from the platform minimums. You can then adjust:
- CPU
- Memory, including the seven reservable-service sliders and supported service toggles
- Database storage
- Workspace storage
- Object storage
The price updates with the selected values and billing cycle. Monthly shows the recurring monthly base. Annual — save 10% shows the discounted monthly equivalent and the prepaid total charged for the 12-month term. The purchased shape is the App’s resource envelope; a preset is a starting configuration, not a different enforcement model.
Storage can grow after purchase but can’t be reduced through self-service. Choose database, workspace, and object storage with that one-way change in mind.
CPU controls allow temporary burst for traffic spikes. Memory uses two classes: database, cache, search, message-broker, and page-cache services reserve the amounts you select and don’t burst. NFS reserves what you select but can use up to 1 GiB, or your reservation if larger, when the Workspace has many files. PHP-FPM, Nginx, Scheduled Jobs, and the WAF use the remaining headroom without a customer memory limit. The Burst controls therefore don’t include memory settings for those dynamic workloads. Review How usage becomes cost before purchasing when variable usage would affect your budget.
If the page says the configuration exceeds the largest plan, reduce CPU, memory, or storage before continuing.
Choose a framework
Section titled “Choose a framework”Every framework card is unavailable until you select a plan preset or Custom. Then select the framework that matches the application you plan to deploy. A framework remains unavailable when the selected CPU or memory is below its minimum requirement. The unavailable card states the minimum it needs; increase the shape to that floor before selecting it.
Changing the shape after selecting a framework can clear the framework selection if the new shape is too small. Re-select the framework after increasing the resources.
Magento and Shopware currently require at least 1 CPU and 7 GiB memory. Optional services can require a larger shape; the portal validates the complete selection.
Choose a database and optional services
Section titled “Choose a database and optional services”After selecting WordPress or Magento, review the preselected database engine and version. The available pairs come from the platform’s published version catalog. You can keep the framework default or select another listed pair.
The database engine choice doesn’t change the purchased resource shape or base price. Optional services are separate: enabling one can increase the required memory or storage, and the portal updates the shape and price before purchase.
Confirm payment
Section titled “Confirm payment”If the Team has saved payment methods, choose the card to charge. The Team’s default card is preselected. Select Use a different card to capture a new card. The card you purchase with becomes the Team’s default billing card — every App on the Team, including existing ones, bills it from their next charge.
When adding a card, complete the card form and every required billing-address field. Choose Monthly or Annual — save 10%, then review the displayed charge and selected payment method. An annual purchase charges the full prepaid term amount now; usage and burst charges remain monthly.
Accept the Terms of Service and Privacy Policy, then select Purchase Plan. The button remains unavailable until a shape and eligible framework are selected, payment requirements are complete, the shape is within platform limits, and consent is checked.
Follow provisioning
Section titled “Follow provisioning”After the purchase is accepted, the portal opens the new App and shows its provisioning progress. For an annual purchase, this screen also confirms the term amount charged. Wait for setup to finish before connecting a repository or starting a deploy.
The provisioning card on Overview is the source of truth:
- While setup is running, leave the App in place and wait for the next stage.
- If the card offers Retry, use that action on the same App.
- If it reports a terminal failure without a recovery action, contact support with the App name or identifier and the visible error ID.
If the purchase request is rate-limited, wait for the time shown and retry the same form. Don’t repeatedly select Purchase Plan or open a second purchase tab while a request is processing.