- What does the morethingsdigital/vercel-statamic package actually do?
- It is an integration package that supplies the configuration and helper code needed to run a Laravel-based Statamic CMS on Vercel's serverless platform. Rather than replacing Statamic, it adapts the surrounding Laravel environment so routing, caching and environment setup behave correctly in a serverless, ephemeral runtime. You still build your site with Statamic as usual and use this package to bridge the gap to Vercel.
- How do I install vercel-statamic in my Statamic project?
- Install it through Composer with composer require morethingsdigital/vercel-statamic inside your existing Laravel and Statamic application. After installation, follow the repository README for any config publishing, environment variables or entrypoint changes the package expects. Because Vercel runs PHP through a serverless runtime, your project also needs the usual Vercel PHP setup rather than a traditional web server root. Check the README for the exact sequence before deploying.
- Which Laravel and Statamic versions does this package support?
- The package is built for Laravel applications running Statamic, but exact version constraints live in its composer.json and README rather than in this summary. Before upgrading Laravel or Statamic, review the require and conflict sections of the package's composer.json to confirm compatibility. Pinning a tested combination in your own composer.json avoids surprises during a Vercel build.
- How does routing work for a Statamic site on Vercel?
- On Vercel your Laravel application is invoked through a single serverless function, so all requests must be funnelled through the Laravel front controller instead of being served by per-directory rewrite rules. The package provides the configuration and helpers that make Statamic's route handling and page resolution work in that setup. You should still ensure your Vercel routing configuration sends non-asset requests to the PHP entrypoint.
- How should caching be configured for Statamic in a serverless environment?
- Serverless functions have ephemeral, often read-only local storage, so filesystem-based caches such as Statamic's static caching and Laravel's file cache will not behave the way they do on a VPS. The package is intended to help with caching setup for this environment, but you should plan on an external store for anything that must persist between invocations. Review the README's caching notes and test cache warm-up behaviour on a preview deployment before going live.
- Can Statamic write content and assets when the filesystem is read-only on Vercel?
- Vercel's runtime filesystem is generally not writable in a durable way, so authoring content directly in production on Vercel is not a reliable workflow. Statamic's flat-file content is best committed to the repository or stored in a remote filesystem driver, with the Control Panel used locally or in a separate persistent environment. Confirm the supported content strategy in the package README before choosing an editing workflow.
- Which environment variables do I need to set for a Statamic site on Vercel?
- Expect to configure the standard Laravel values such as APP_KEY, APP_ENV, APP_DEBUG and APP_URL, plus any Statamic licence or addon credentials your site uses, as Vercel project environment variables. The package description explicitly mentions environment setup, so check the README for any package-specific keys it adds. Remember that changing an environment variable requires a new deployment to take effect.
- Does this package work with Statamic Pro, multi-site installs and addons?
- The package targets statically or flat-file driven Statamic sites, and multi-site or Pro features should work as long as their data is available to the build and runtime. Addons that rely on long-running processes, queues, persistent local writes or scheduled tasks need extra attention because Vercel is request-scoped. Test each addon on a preview deployment rather than assuming parity with a traditional server.
- How do I test a Vercel Statamic deployment before it goes live?
- Run the site locally with your normal Laravel and Statamic tooling first to confirm the application itself is healthy, then use Vercel preview deployments to validate routing, caching and environment variables. Preview deployments are the best place to catch read-only filesystem errors or missing environment keys. Also verify that your build step includes any content or asset compilation Statamic needs.
- What are the alternatives to vercel-statamic, and is it actively maintained?
- Alternatives include deploying Statamic to a traditional Laravel host, a container platform, or a static-site workflow where Statamic's static caching generates HTML at build time. Choosing Vercel plus this package mainly makes sense when you want Vercel's edge network and preview workflow for a headline marketing site. Check the repository's commit history, releases and open issues to judge current maintenance activity before adopting it.