Custom Domains & HTTPS

Slasha comes with a built-in Caddy reverse proxy that handles routing public HTTP/HTTPS traffic directly to your running web containers.

Platform Subdomain Routing

When you set up your Slasha server, you define a base SLASHA_PLATFORM_DOMAIN (e.g. slasha.example.com). By default, every app you create is instantly assigned a platform subdomain based on its slug.

For example, an app named my-cool-api will be automatically routed and accessible at:
https://my-cool-api.slasha.example.com

Custom Domains

You can attach any custom domain to your application using the dashboard or via your terminal. For detailed CLI usage, see the CLI Domains Reference.

When a custom domain is added, Slasha calls Caddy's dynamic admin API to add the corresponding route.Note: If you add a custom domain, it takes precedence. The app will be reachable on both the custom domain and the platform subdomain.

Automatic TLS/HTTPS

Caddy automatically issues and manages free Let's Encrypt or ZeroSSL TLS certificates for all of your configured domains (both platform subdomains and custom domains). There is no need for manual cert renewal or complex configuration.

Configuring DNS & Troubleshooting

To use a custom domain, you must point your domain's DNS A record (or CNAME) at your server's public IP address.