Slate FAQ

Absolutely! Catalyst Slate allows you to easily map custom domains to your deployed applications, giving you full control over your brand and online presence.

You can define environment variables directly in the Catalyst console, where they are encrypted and stored. This gives you secure, centralized access to separate configurations for your Development and Production environments.

Catalyst Slate provides native support for all popular JavaScript frameworks, including Next.js, React, Angular, Astro, Vue, SolidJS, Svelte, Vite and more. Also, you can seamlessly deploy applications built with other front-end frameworks as well.

Yes, Catalyst Slate allows you to preview every deployment in a sandboxed environment where you can view and test your application before it goes live. This ensures you can catch any issues early and maintain high-quality standards for your applications.

Catalyst Slate prioritizes security with features like automatic SSL provision and robust infrastructure. Your applications are protected with industry-leading security measures, ensuring peace of mind for you and your users.

Yes, you can deploy your application to Slate using our CLI commands. Check out this help page to learn about the deploy commands and their usage in detail.

Yes, you will be able to pull code from any public Git repositories, deploy and preview the full working application live using Catalyst Slate. You can check out our public Git integration feature in Slate help documentation.

If you have edited your Slate access URL after mapping your custom domain, make sure to redo the mapping with the updated access URL. Note that this may not be the only issue, but it should be verified before troubleshooting other potential problems.

No. Catalyst Slate custom domains work with subdomains, such as www.zylker.com or app.zylker.com, not with a root domain. The mapping uses CNAME records, and many DNS providers do not allow a CNAME record on a root domain. Map a subdomain, then redirect the root domain to it at your DNS provider.

1. In your Slate app, open the deployment’s Deployment Overview and click Add Domain in the Domain Mapping section.

2. Enter a subdomain such as www.zylker.com and click Next.

3. Add the Step 1 and Step 2 values as CNAME records at your DNS provider, clicking Verify after each.

4. Click Request to request the Group SSL certificate.

5. At your DNS provider, set up domain forwarding from zylker.com to www.zylker.com over HTTPS.

Note: The Catalyst certificate covers only the subdomain you mapped, so opening the root domain over HTTPS shows a certificate error unless your DNS provider serves the redirect over HTTPS.

Refer to the Custom Domains help page for more information.

In Catalyst Slate, Step 2 passes only when you click Verify and Catalyst finds the second CNAME record with exactly the host name and value shown under Step 2. Catalyst checks the record when you verify, so if your record is correct and resolves publicly, verify Step 2 again.

1. In the deployment’s Deployment Overview, open the domain in the Domain Mapping section.

2. Compare your record with the Step 2 host name and value, character for character. If your DNS provider adds your domain to host names automatically, enter only the part before your domain.

3. Create it as a CNAME record, not an ALIAS, ANAME or URL redirect record. If your provider proxies records, set it to DNS only.

4. Click Verify for Step 2. When both steps are verified, click Next, then Request to request the SSL certificate.

5. If Step 2 still fails, contact Catalyst support with the domain, the app and deployment, the exact error and a screenshot of your DNS records.

Refer to the Custom Domains help page for more information.