Choose and configure the app
1
Open the marketplace
Select an app and read its description, configuration requirements, recommended resources and license. Check the marketplace guides for app-specific setup.
2
Choose your VM
Select a running VM in your project with enough free memory and disk space for the app and its data.
3
Fill in the configuration
Supply the fields requested by this app. These can include API keys, initial credentials, provider choices and other settings. Fields that support automatic secret generation are identified by the form.
4
Review public access and deploy
For an HTTP app that supports public exposure, choose its subdomain. Use the public URL shown by the dashboard after deployment. Some apps use direct TCP ports instead, and others have no public endpoint.Submit the install and follow its status. Deployment time depends on image downloads and the app’s startup work.
Complete the app’s setup
Once the install is running, open its address and follow the app’s setup instructions. Some apps need an administrator account, a token-bearing first-connect link or device pairing. A running container can still be initializing or waiting for configuration. Use the instance’s Logs, Terminal and Files tabs, selecting the app where applicable, to diagnose problems. The install page shows the deployed version and available restart, upgrade and configuration actions.Secrets and configuration changes
Secret configuration is encrypted in Suji’s database. Authorized users can reveal supported secrets from the app’s Variables controls. Apps need their configuration at runtime, so credentials may also be present in environment files on the VM and accessible to someone with root access. This is not a full-disk encryption guarantee. Use the app’s configuration controls for supported changes. A change can redeploy or restart the app, so allow for interruption. Installs with a custom Compose file have restrictions on template configuration and upgrades; review the dashboard’s message before changing them. Preserve and back up app data before any operation that requires reinstalling.External integrations
- Webhooks and OAuth: use the endpoint and setup method required by that app. Some integrations use polling or an outbound connection instead of a webhook. After changing a domain, update registered callback URLs and test the integration.
- External services: API usage, email delivery, paid app licenses and other third-party services may be billed separately by their providers.
- Email: upstream network or account restrictions can block outbound SMTP, including ports 25 and 465. Use your mail provider’s supported configuration, such as an authenticated relay on port 587 or an HTTPS email API, and test connectivity. Adding a VM firewall rule does not remove an upstream restriction.
Next
Marketplace guides
Find the setup instructions for your app.
Custom domains
Use your own domain for an exposed HTTP app.