Statamic deployment options

# Get ready

• Have a local development environment with PHP and a web server ready.
• Have Statamic installed and running locally.

# Deployment considerations

Statamic combines file-based content storage with Laravel framework capabilities, making both file-sync and Git-based deployment viable depending on your project needs. Like Grav and Kirby, it stores content as text files on the file system, but being built on Laravel it also uses Composer.

If you intend to use Statamic with a database, book the database component and set up database import/export.

# Deployment options

# 1 - SFTP upload

Upload all contents of your local Statamic folder - including the hidden .htaccess file and the vendor folder — into the htdocs directory of your environment. A good starting point if you are new to web development, but consider moving to rsync for anything recurring.

# 2 - rsync

A scriptable command-line flow that works in both directions: push template and config changes up, pull content down. Easy to automate with AI agents. See the general rsync article. A good fit for solo projects and quick demos.

# 3 - Git + rsync

The most advanced option, suited for team projects. Manage code with Git for revision history and deployment automation (composer install, cache clearing, migrations); sync content separately with rsync. See Git + rsync deployment for Statamic.