Host open-source applications
Host open-source applications with templates
Start with a template that describes the services an application needs. Compare the configuration before deployment, then take responsibility for account setup, application updates and durable data.
Configuration checklist
- Service composition: compare single-service, database-backed and worker variants rather than choosing by the application name alone.
- Compatibility: review importer warnings and unsupported requirements. Static catalog checks are not proof of a tested live deployment.
- Required inputs: prepare application credentials, external API keys, SMTP settings and initial account setup as applicable.
- Data and upgrades: identify database files, uploads and encryption settings that must persist. Read upstream maintenance and upgrade instructions.
From configuration to deployment
Compare templates
Browse the marketplace, category lists and focused collections. Read the service composition of each candidate template.
Review the application's requirements
Open the detail page and inspect configuration inputs, persistence, compatibility limitations and upstream documentation.
Configure your deployment
Sign in, choose a project and region, then review each service's variables, volumes and network access before submitting.
Complete application setup
Inspect logs, create the application's initial account and test its main workflow. Validate persistence and recovery before production use.
Keep the service running
- Maintain the application as well as its hosting configuration. Review upstream releases, authentication settings and third-party integrations as they change.
- Back up the application data that matters, including database contents and uploaded files where applicable. Test restoration instead of assuming a volume is a backup.
- Test updates in a separate environment when possible. Verify dependent services, persisted settings and important workflows after each upgrade.
Questions before deployment
Does deploying a template migrate my existing application data?
No. Plan the database export and import, uploaded files and application secrets separately. For a WordPress move, check both the database and uploaded media; for n8n, preserve the encryption key needed by stored credentials. Test a restored copy with compatible application versions before switching traffic, and keep the original data until validation is complete.
When is template hosting not the right choice?
If you need the application vendor to manage accounts, upgrades and data recovery for you, compare its managed offering first. Templates reduce configuration work but still need an application owner. Before deploying, decide who will manage administrator access, test updates, maintain external integrations and verify backups.
Does a template include everything the application needs?
A template describes a deployment configuration. Some applications still need external credentials, email delivery, paid APIs or manual initialization. Read the template detail and upstream documentation before deployment.
How do I choose between variants of one application?
Compare the service list, database choice, worker requirements and persistence model. Choose the composition that matches your expected workflow and ability to maintain it.
Does deployment automatically validate the application?
No. Inspect the deployment result, complete application setup and test important workflows yourself. A compatibility label or successful start does not replace application validation.
Configure in your workspace
Signing in opens your workspace. Resources are created only after you submit the deployment configuration.