Services

Depending on the application, your deployment may require service dependencies - databases, caches, message queues, or other infrastructure components. The setup interface guides you through any service decisions.

​

How It Works

The application defines what it needs (for example, “a relational database”). During configuration, the setup interface shows you the concrete options available in your environment and lets you choose. For example, if the application needs a relational database and you’re deploying to AWS, you might see options like:

• Amazon RDS (PostgreSQL) - Managed by AWS
• Self-hosted PostgreSQL - You manage it yourself

​

Service Categories

​

Managed Services

Cloud-provider-managed services (like RDS, ElastiCache, or Cloud SQL). These are provisioned automatically as part of the deployment. You choose the service, and the controller handles the rest.

​

Self-Hosted Services

Services you manage yourself. If you choose a self-hosted option, you’ll provide connection details (hostname, port, credentials) during the secrets configuration step.

​

Pre-Existing Services

If you already have a compatible service running (for example, an existing PostgreSQL database), you can connect the application to it instead of provisioning a new one.

​

Making Selections

The setup interface shows only the options relevant to your environment and deployment. Select the services you want, and the rest happens automatically during deployment. If the application doesn’t require any service selections, this step is skipped entirely.

​

Changing Services Later

Service selections can be modified after initial setup. Contact us to discuss changes - some service switches may require data migration.