---
title: "Launch FAQs"
description: "Launch FAQs"
url: "https://www.contentstack.com/docs/launch/faqs"
product: "Contentstack"
doc_type: "guide"
audience:
  - developers
  - admins
version: "current"
last_updated: "2026-04-30"
---

# Launch FAQs

## General FAQs

### Will my site have downtime for new deployments?

No. Your last successful deployment will remain active until it is replaced by a subsequent successful deployment. However, redeploying your site will clear the CDN cache for your site, so previously cached pages will be served as uncached requests the first time they are accessed.

### Does Launch support custom domains?

Yes. [Custom domains](/docs/developers/launch/custom-domain) may be added and configured in each environment’s settings.

### Does Launch support serverless functions?

Yes. [Launch](/docs/developers/launch/about-launch/) deploys server-side functionality as serverless functions. This includes SSR-rendered pages, and [Cloud Functions](/docs/developers/launch/cloud-functions).

### Does Launch support hosting static websites?

Yes. To deploy a [static site](/docs/developers/launch/host-a-static-site/), follow the process specified in your framework code for static site generation (SSG) rendering.

### Does Launch support Edge Functions?

Yes. You can execute your code in proximity to your user’s location before a request is processed using [Edge Functions](/docs/developers/launch/edge-functions) in Contentstack Launch.

### Does Contentstack Launch support forwarding project logs to specific endpoints?

Yes. The [Log Targets](/docs/developers/launch/log-targets) feature in Contentstack Launch allows you to forward the logs produced by [Launch Cloud Functions](/docs/developers/launch/cloud-functions/) or by [Launch-supported frameworks](/docs/developers/launch/launch-framework-support#launch-framework-support-matrix) to third-party monitoring services that support GRPC OTLP endpoint.

### What frameworks can be used to deploy on Launch?

You can find the frameworks supported by Launch in the [Launch Framework Support Matrix](/docs/developers/launch/launch-framework-support#launch-framework-support-matrix).

### Does Launch support read and write operations to the filesystem at the runtime?

Launch runtime operates in a read-only file system, except for the designated /tmp directory, which facilitates write operations. The /tmp directory is a temporary file system accessible to every Launch serverless runtime, offering up to **500 MB** of storage.

**Note**: The data stored in /tmp is non-persistent and is automatically deleted upon request completion.

### Can I integrate Launch with other services and products?

Yes. [Automate](/docs/developers/automation-hub-guides/about-automation-hub/) includes triggers and actions for common Launch activities. Launch also includes [deploy hooks](/docs/developers/launch/deploy-hooks/) functionality, allowing you to trigger rebuilds via a URL. Launch can also use the Marketplace app to set up an SSO at the edge.

### What support can I expect when hosting my site on Launch?

[Launch](/docs/developers/launch/about-launch/) technical support is offered through the same technical support channels used for all other Contentstack products.

### What regions is Launch available in?

Launch is available in [AWS NA](https://app.contentstack.com/#!/launch), [AWS EU](https://eu-app.contentstack.com/#!/launch), [AWS AU](https://au-app.contentstack.com/#!/launch), [Azure NA](https://azure-na-app.contentstack.com/#!/launch), [Azure EU](https://azure-eu-app.contentstack.com/#!/launch), [GCP NA](https://gcp-na-app.contentstack.com/#!/launch), and [GCP EU](https://gcp-eu-app.contentstack.com/#!/launch) regions.

### Will my site have a downtime when migrating to Launch from a different hosting provider?

Depending upon your specific architecture and change process, migrating your existing site to Launch can be achieved with zero or minimal downtime.

### What Git providers does Launch support?

Launch currently supports deploying sites via [GitHub](/docs/developers/launch/import-project-using-github/), [BitBucket](/docs/developers/launch/import-a-project-using-bitbucket-cloud), and direct [zip file uploads](/docs/developers/launch/import-project-using-file-upload/). GitLab support will be available shortly.

### Does Launch support CI/CD?

Yes. Launch can be configured to [automatically redeploy](/docs/developers/launch/redeploy-automatically-when-content-is-published-on-CMS/) when code updates are committed in GitHub and when webhooks are accessed. Launch commands are also available via [Contentstack’s CLI](/docs/developers/cli/cli-for-launch/).

### Does Launch support deploying code automatically?

Yes. [Automatic deployments](/docs/developers/launch/redeploy-automatically-when-content-is-published-on-CMS/) can be configured in your environment’s settings screen.

### Does Launch support creating test environments?

Yes. Each Launch project includes 5 environments by default, which you can use to deploy environments for staging, testing, content review, and more.

### How do I debug my websites on Launch?

Launch features deployment and server logs to help you troubleshoot deployments and functionality. Serverless functions can also be tested locally.

### Does Launch need access to my GitHub account?

If you wish to deploy sites to Launch directly from GitHub, then you must authenticate with your GitHub account. However, Launch also supports deployments directly from a zip file upload, which does not require GitHub access.

### Does Launch support bulk publishing/deployments?

Bulk site deployments can be achieved via the [CLI](/docs/developers/cli/cli-for-launch/) and through local scripting.

### Can I run a Docker container on Launch?

Launch is a front-end hosting and deployment platform for websites built on the Contentstack CMS instantly, but it **cannot** run Docker containers.

Please refer to this [documentation](/docs/developers/launch/docker-support-in-launch/), for more information about Docker containers and why Launch does not support them.

### What NodeJS Runtime version does Launch support?

Currently, Launch supports Node.js versions 18.x (discontinued as of August 1, 2025), 20.x and 22.x for running website builds during deployment. For more information, please refer to the [supported Node.js versions](/docs/developers/launch/supported-nodejs-versions/).

**Warning**: Support for Node.js version 18 is discontinued for Launch as of August 1, 2025. Update to a supported Node.js version to avoid disruptions in your projects.

### Can Launch be used for mobile?

Launch cannot be used for native mobile apps, such as those installed from an app store. However, you can use Launch to host mobile-friendly and responsive websites or web apps. Additionally, it can be used to support backend needs, such as building APIs that your mobile app can access.

### What is the maximum number of logs that Launch can forward in a single request?

Launch can forward up to **1000 log lines** in a single request.

### What is the maximum size of a single log line?

Each log line can be up to **64 KB**.

### Is there an overall log size limit per request?

Yes. There is a hard cap of **1 MB of total logs per request**, which takes precedence over the other limits.

### Why do I see a “warming up” screen on my Launch site?

When a Launch-hosted site or application has not been accessed for an extended period, the environment may temporarily scale down. When someone visits again, the environment needs a few seconds to warm up before it can serve content. During this brief period, you may see a **“warming up”** screen. This is expected behavior and indicates that your environment is starting up.

**What happens next?**

*   The environment initializes in the background.
    
*   The page automatically reloads once it is ready.
    
*   You do not need to take any action.

### How long does the Launch site warm-up take?

In most cases, the warm-up completes within a **few seconds**.

### Does the “warming up” state impact my production site?

No, sites with consistent production traffic do not reach an idle state. However, if your application is expected to receive no traffic for extended periods, you can keep your environment warm by setting up automation in Contentstack.

## Caching FAQs

### How does caching improve my website’s performance?

Caching reduces latency and load times by storing copies of your content closer to your users on CDN servers. This results in faster page loads, improved user experience, and reduced load on your origin servers.

### How long does Launch cache my content?

Caching duration depends on the [Cache-Control](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Cache-Control) headers you set. You can specify caching durations using headers like max-age and stale-while-revalidate.

### Can I control caching for dynamic content?

Yes. You can control caching behavior by setting specific HTTP headers in your responses.  
Refer to the [Dynamic Content with Cache Headers](/docs/developers/launch/caching-guide-for-contentstack-launch#dynamic-content-with-cache-headers) section in the _Caching Guide for Contentstack Launch_ doc for details.

### Does Launch support Next.js ISR (Incremental Static Regeneration)?

No. Launch does not support Next.js ISR or native caching APIs like revalidatePath or revalidateTag. For more details, see [Next.js limitations](/docs/developers/launch/nextjs-on-launch#limitations).

### How do I disable caching completely?

Use the following header to disable caching:  
Cache-Control: no-store

### How can I manually purge or invalidate cached content?

Refer to the [Purging Cache](/docs/developers/launch/caching-guide-for-contentstack-launch#purging-cache) section in the _Caching Guide for Contentstack Launch_ doc for details.

### Can I use multiple CDNs with Launch?

It is generally not recommended to layer multiple CDNs, as this could lead to cache conflicts and unpredictable behavior.

### How can I check if my content is being cached?

You can monitor caching behavior using response headers such as x-cache or cf-cache-status. A value of HIT indicates that the content was served from the cache, whereas MISS indicates that it was fetched from the origin.

### Is caching secure? Can sensitive data accidentally get cached?

Sensitive or private data should never be cached. Always ensure sensitive data responses have caching disabled (no-store or no-cache) headers set explicitly.

### Where can I find more information on Next.js-specific caching strategies?

Visit our dedicated [Next.js on Launch Documentation](/docs/developers/launch/nextjs-on-launch) for more details.

### How does caching work for 404 and error pages?

By default, **404** and **error pages** are **not cached** by Launch’s CDN, even if Cache-Control headers are present. This is a platform-level behavior to ensure error pages are always revalidated. Identify known bad routes and handle them gracefully at the edge using [Launch Edge Functions](/docs/developers/launch/edge-functions/).

### Does Launch support a data cache like Next.js App Router?

No. Launch does not support the native data cache feature of the Next.js App Router (e.g., fetchCache, revalidatePath, revalidateTag) due to its serverless and [read-only file system architecture](/docs/developers/launch/nextjs-on-launch#file-system).

### Does Launch recommend any alternatives to Next.js Data Cache

*   **Use SSR with Cache-Control headers**: Cache API responses at the CDN level using Cache-Control headers to increase the cache-hit ratio and enable [on-demand cache revalidation with Automate](/docs/developers/automation-hub-connectors/launch-trigger).Cache-Control: public, s-maxage=86400, stale-while-revalidate=60
*   **Cache API requests in a framework-agnostic way**: Check out the [GitHub example](https://github.com/contentstack-launch-examples/management-api-cache-wrapper) that caches Contentstack Management API responses to reduce rate-limiting issues.

### Does caching apply to external URLs fetched via Edge Rewrites, Redirects, or Edge Functions?

Launch uses Cloudflare as its CDN. Caching external URLs can apply, but only if the external URL is served through Cloudflare and returns cacheable Cache-Control headers. If the external origin is hosted on a different CDN or server and lacks cacheable headers, the response will not be cached.

### Can I use in-memory caching at the origin with Launch?

No. Each request is handled by a stateless function instance that may not retain memory between invocations. This implies:

*   Any data stored in memory—such as variables, objects, or in-process caches—is not guaranteed to persist beyond a single request.
*   You should opt out of in-memory caching supported by some libraries, such as the [Contentstack SDK](/docs/developers/sdks/content-delivery-sdk/javascript-browser/reference#quickstart-in-5-mins-cache-policies), which can optionally maintain a local cache to help with rate limiting and performance.

## Event Tracking (Lytics) FAQs

### How do I know if Event Tracking (Lytics) is enabled?

Check your website's HTML for the presence of the Event Tracking <script> tag. If the tag is present, Event Tracking is active.  
For example: <script async="" src="https://c.lytics.io/api/tag/\*/latest.min.js"></script>

### Do I need to redeploy after enabling Event Tracking?

Yes. If your application uses [ETag-based](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/ETag) browser-side caching, you must redeploy your site. This ensures that the Event Tracking script is correctly delivered to users.

### How do I know if Event Tracking is disabled?

If the Real-Time Event <script> tag is missing from the HTML, Event Tracking is disabled.

### I updated the Real-Time Tracking tag (Lytics) settings,when do changes take effect?

Changes typically take effect within **5 minutes** of updating the settings.

### I enabled Event Tracking, but I don't see the dashboard data. Why?

A mandatory redeploy is required to activate the Event Tracking (Lytics) feature on your website due to browser caching ([ETag](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/ETag#caching_of_unchanged_resources) behavior).

### I disabled Event Tracking (Lytics), but data is getting collected. Why?

A mandatory redeploy is required to deactivate the Event Tracking (Lytics) feature on your website due to browser caching ([ETag](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/ETag#caching_of_unchanged_resources) behavior).

### If I enable Event Tracking, does it start gathering data for all the users?

No. Data collection begins only after users provide explicit consent. To collect user-specific data, you must [configure a custom tag or build a custom consent modal](/docs/developers/launch/event-tracking-in-contentstack-launch#handling-user-consent-optin). When the user accepts, Real-Time User Event Tracking starts for that session.

### Why don’t Edge-related functionalities work with the Nuxt framework?

This is due to how <NuxtLink> handles client-side navigation. To resolve this, use standard <a> tags instead.

Learn more in the [Nuxt.js on Launch](/docs/developers/launch/nuxt-on-launch#setting-up-edge-redirects-and-rewrites-in-nuxt-on-launch) guide.

## Cache Priming FAQs

### What content should I prioritize for Cache Priming?

Focus on high-traffic and frequently accessed pages, especially those updated regularly. These include landing pages, key product pages, dynamic content, and essential resources that must load quickly.

### Will Cache Priming affect my existing caching setup?

No, Cache Priming seamlessly integrates with your current caching configuration. It enhances performance by preloading content during deployment without overriding existing cache rules or policies.

### Can I use Cache Priming across multiple environments (staging, production, etc.)?

Yes, Cache Priming supports multi-environment deployments, ensuring optimized caching across staging, production, and other environments without manual intervention.

### How often is primed content refreshed?

Cache Priming works alongside cache revalidation mechanisms, updating content based on predefined policies or upon new deployments.

### Does Cache Priming work with dynamic content?

Yes, Cache Priming optimizes both static and dynamic content. It preloads frequently accessed dynamic pages that follow predictable update patterns while ensuring static pages load instantly.

### How do I enable and configure Cache Priming?

Configure Cache Priming by specifying key URLs in launch.json and enabling the cache priming toggle from the UI. For detailed instructions, refer to the [Cache Priming](/docs/developers/launch/cache-priming#steps-for-execution) document.

### What happens if a primed URL is no longer needed?

You can use [Automate](/docs/developers/automation-hub-guides/about-automation-hub) to purge the cache for the URL and remove the URL from the Cache Priming list. The cache will gradually invalidate outdated content based on your CDN’s expiration policies.

### How does Cache Priming handle personalized, geo-specific, or restricted content?

Cache Priming is designed for globally accessible content and respects security policies, geo-restrictions, and IP limitations:

*   **Geo-Specific Content**: Priming is only effective where regional content is accessible. If a page is restricted by geography, users outside those regions may not benefit.
*   **Security & IP Restrictions**: Cache Priming does not override authentication or IP-based restrictions. Websites with strict access controls must explicitly allow Contentstack IPs for priming to be effective.

### How does Cache Priming impact API-driven websites?

Cache Priming can **preload API responses**, making frequently requested data instantly available. This reduces response times and backend load.

### What happens during a large-scale content update?

For major content updates, use Cache Priming alongside **cache revalidation strategies** to serve fresh content without requiring a full cache purge.

### How do I revalidate cache-primed paths?

To learn how to revalidate already cache-primed paths, refer to the [Revalidate CDN Cache](/docs/developers/launch/revalidate-cdn-cache/) Launch document.