Deploy a template

Deploy a published template to create an independent stack in your project. You need project write permission and an existing active resource pool with a compatible architecture, current Crane support, and sufficient capacity.

1. Find and inspect a template

Browse Templates on the public site or open Templates in the dashboard. Search by application and use category or publisher filters to narrow the catalog. Only eligible published entries appear in public inventory. An empty result does not mean that private drafts are deployable.

Open a template and review:

• Publisher identity and any verification indicator.
• Software name, upstream version, edition, and license.
• The selected Template release, service layout, and release notes.
• CPU, memory, storage, resource assumptions, and tested architectures.
• Getting-started instructions and required external services.
• Operations, persistence, backup, and upgrade instructions.

Template version and application version can differ. Choose the release you intend to deploy; historical release pages describe that exact snapshot, not a moving latest configuration.

2. Keep the selected release

Select Deploy application from the template page and sign in if requested. The dashboard retains the selected release as you choose a workspace and project. Confirm that the deployment screen names the expected application and version.

If the release is unavailable, return to the template and choose an available release. A cached public page is not proof that deployment remains permitted: the backend checks current availability again.

3. Choose the destination

1. Enter the stack name, starting with a lowercase letter and using up to 40 lowercase letters, digits, or hyphens.
2. Choose an environment, or select Create environment.
3. Select a resource pool in the current project.

Pools below the release’s minimum CPU, memory, or storage requirements, or inactive pools, are unavailable for selection. The server’s actual architecture must match a declared tested architecture; it is checked again before deployment. Overall service allocations and normal application checks also apply.

If no pool is suitable, use Connect your server (new tab) or Create resource pool (new tab). Finish that flow, return, and select Refresh resource pools to retain the release and entered settings. Review any infrastructure charges in the pool setup flow.

4. Answer the setup inputs

The Private inputs section displays the release’s questions with labels and helper text. Inputs can be text, secrets, email addresses, HTTPS URLs, integers, booleans, or fixed choices.

• Provide all required values.
• Leave a generated-secret field empty to let Infralane create a fresh value privately, or supply your own appropriate value.
• Use the safe defaults and allowed choices where suitable.
• Follow requirements for external services such as SMTP or third-party accounts.
• Derived database URLs are assembled privately from other inputs and do not need manual entry.

Do not use a production secret in a test installation. Database initialization credentials may be different from an application’s administrator login. Follow the template’s getting-started instructions to complete application setup after deployment.

See Template input reference for the available types and behavior.

5. Review advanced changes if needed

Advanced service configuration is collapsed initially for registry installations. Expand it to inspect or edit services in Visual builder or Code.

Changing services creates a customized configuration while retaining the original release identity. The advanced editor still validates the supported Compose subset. A reviewed starting release does not mean your changes were tested or reviewed by the publisher.

Prefer the release’s input questions for normal setup. Advanced changes can affect health checks, persistence, compatibility, and future upgrade instructions.

6. Review and deploy

Select Review deployment. Verify the target environment and pool, each image, dependencies, public HTTP ports, volume counts, and service allocations. Review produces a plan and does not change applications. It expires after 15 minutes; changing configuration requires a new review.

Select the final Deploy application name action shown for that release. Infralane queues a stack operation and opens its progress page. Services deploy in dependency order, and deployment continues after navigation.

Availability is checked during selection, application of the plan, and before further service submissions. A release blocked during an operation can stop the remaining work while retaining earlier services and their data.

7. Complete application setup

1. Follow the stack’s Deployment progress until the operation completes, or inspect the current service if it fails.
2. Open each service’s deployment and logs to confirm the expected application is running.
3. Read Template origin → Getting started for instructions captured with the installed release.
4. Complete administrator setup, external account connections, and any application-specific setup described there.
5. Test the generated HTTP endpoint before adding a custom domain.
6. Configure independent backups and verify the restore procedure for persistent data.

For databases, use Connection details deliberately; the private hostname is for services in the same stack on the same pool. See Stack operations.

After installation

The stack retains its publisher, template version, release identity, and customization state. New template releases do not automatically update the installation. Read Releases and maintenance before planning upgrades.

For failures, inspect stack troubleshooting. To report an issue with the template itself, use Report a problem on its dashboard page and include the affected release and redacted recovery details.