Kiln
Get started
← All posts Product update

Kiln now handles Statamic, Filament and SQLite sites

Statamic content kept out of Git is found and copied, caches are skipped, Git automation is flagged, and sites without a MySQL database are no longer treated as if they had one.

Daniel Jones 24 October 2026 · 2 min read
On this page

Kiln started life moving Craft CMS sites for our own agency. It now understands Statamic, Filament and SQLite sites properly too.

Statamic

  • Content outside Git is copied. If a site keeps content/, users/ or storage/forms out of Git, Kiln finds those folders and offers to copy them, alongside uploads in public/.
  • Caches are skipped. The static page cache and the Stache rebuild themselves, so Kiln doesn't copy them.
  • Git automation is flagged. If STATAMIC_GIT_ENABLED is on, the review warns that the new server's SSH key needs write access to the repository.
  • The deploy script stays in the right order. Statamic's [BOT] check stays at the top, and static cache warming moves after the new release goes live.

Sites without a MySQL database

Flat-file Statamic sites often have no database at all. Kiln now reads each site's .env and treats it as one of five kinds:

Database What Kiln does
MySQL or MariaDB on the server Creates it on the new server and copies it
External Leaves it as it is
None Nothing to create or copy
SQLite Doesn't copy it, and shows a note
PostgreSQL Doesn't copy it, and shows a note

Filament

Filament admin panels are Laravel apps, so they get everything Laravel sites do. Livewire's temporary uploads are no longer copied.

Every framework now has a full simulated migration in our test suite: Craft, Laravel on MySQL, Statamic, Laravel on SQLite and Filament. Try it in the live demo.

Let Kiln do the whole move Every site, database and setting copied, then one switch-over with zero downtime. £15 a server.
Try the live demo

Keep reading

Guide The Forge server migration checklist Guide Ubuntu 22.04 end of life: what Forge users need to do before April 2027