Starter templates
Create reviewed starter applications with generated secrets and private database references, then deploy each service deliberately.
Starter templates create an application project from reviewed source. They prepare services, a Production environment and a Blueprint so you can inspect the configuration before deploying. Creating a project does not start compute, charge a payment or prove the application is live.
Available starters
| Starter | Creates |
|---|---|
| Next.js | A web application |
| Django with PostgreSQL | A Python web application and private PostgreSQL database |
| Laravel with MySQL | A PHP web application and private MySQL database |
| Python worker | A background worker |
| Python scheduled job | A cron job |
The template screen shows its stack versions, selected plans and estimated compute total. Treat that total as a configuration estimate; review the final service quote for storage and capacity changes.
Create a project
- Select your workspace in the dashboard and open New → Start with a template.
- Choose a starter and enter a project name.
- Review the services, private database connection and generated application secrets.
- Choose Create project.
- Inspect each service's source, environment variables, plan and commands before deploying.
A workspace owner or admin can create template projects. Generated values are stored as secret variables. Do not replace a generated application encryption key after the application has begun encrypting data unless you have a deliberate migration plan.
Deploy in dependency order
For a database starter, deploy the database first and wait until it is ready. Then deploy the application. The application receives the database connection through private service references in the same environment.
Paid services need their own confirmed service-month purchase before deployment. A template does not bypass checkout or authorize an automatic charge. Review free and paid choices in Pricing.
For Laravel, verify APP_URL is the final HTTPS application address. For any starter, add your real email, payment, queue or external API configuration as secret variables and test the application's important flows after deployment.
Workers and cron jobs need application-specific commands and configuration. A successful cron build prepares an image; the command runs later according to the configured schedule. See Cron jobs.
Make the starter your own
Template source is an immutable uploaded archive. To replace it with your application, open Settings → Source and choose a Git repository, new ZIP or container image. Review and deploy the new source; the saved configuration alone does not update the live release.
Use ZIP source for downloadable application packages, or GitHub deployments when you want commit-triggered releases and pull-request previews. The project's Blueprint records its service configuration; inspect Blueprints before applying later changes.
Keep separate backups of source and application data. Template creation and application builds do not import an existing database or upload directory. Use database migration and persistent disks or object storage for those needs.