Apps
Coming from another cloud?
▸AWS·Marketplace AMI
This Quake AI feature maps to AWS’s Marketplace AMI.
▸DigitalOcean·ONE Click Apps
This Quake AI feature maps to DigitalOcean’s ONE Click Apps.
▸Google Cloud·Marketplace
This Quake AI feature maps to Google Cloud’s Marketplace.
▸Hetzner·Apps
This Quake AI feature maps to Hetzner’s Apps.
Apps
Apps is a deployment feature in the Compute section of the Console (Compute > Apps). You pick an app from the catalog, and the platform provisions an instance from a pre-built image with the application stack already installed. You skip selecting an OS image, configuring networking, and installing software by hand.
How Apps relates to instances#
An app deployment creates a standard Compute instance. The instance uses a pre-built image that ships with the application already installed and configured, along with supporting services (web server, TLS certificates, onboarding wizard). After deployment, the instance appears on the Console Instances page alongside manually created VMs.
When you create an instance through Instances in the Console, you select a base OS image and configure everything after boot. When you deploy through Apps, the image already contains the application stack, and your first interaction is the application's onboarding flow.
What the platform provisions#
When you deploy an app, the platform creates:
- A floating IP for external access, auto-allocated and associated with the instance
- A security group with inbound rules limited to the ports the application requires
- An SSH key pair if you do not already have one in the project (auto-generated during deployment)
- A root disk at the size specified by the template (25 GiB by default)
The resulting instance and Network objects are managed through the same Console pages, CLI commands, and API endpoints you use for any other instance.
Available apps#
| App | Description | Default flavor | Guide |
|---|---|---|---|
| OpenClaw | Open-source AI agent framework connected to Telegram, Discord, Slack, and 20+ messaging platforms | s1a.medium (4 shared vCPU, 4 GiB RAM) | Deploy OpenClaw |
See also#
- Apps Console reference: page layout, fields, and actions
- Instances: how instances work on Quake AI
- Flavors: CPU, memory, and disk presets
Quick answers
- Why does `openstack image save` write a 0-byte file for my boot-from-volume instance?CLI
- Why does `openstack server create` fail with "Only volume-backed servers are allowed for flavors with zero disk"?CLIAPITerraform
- Why does my project still have a 10 GiB Cinder volume after I deleted my instance?CLIAPI
Related content
Pages
Tutorials
Reference
Overviews