Filament Hosting to Deploy Laravel Filament Admin Panels on Your Own Servers

What is the best hosting for Filament?

The best hosting for Filament is a small VPS or a managed Laravel platform that can run a persistent queue worker, a scheduler cron and PHP 8.2 or newer with OPcache. For one internal panel, a 2 GB server with Laravel Forge or Ploi on top is the cheapest sensible setup at roughly $22 to $24 a month all in. For a team or agency running several client panels, a panel with seats, atomic releases and a deploy log, such as DeployManage, is worth its higher fee.

Filament does not need anything exotic. The 5.x docs list PHP 8.2+, Laravel 11.28+ and Tailwind CSS 4.1+ for custom themes. The parts that break on cheap hosting are the background ones: imports and exports, database notifications and scheduled jobs. Pick a host by whether those run reliably, not by the headline price.

Can I host Filament on shared hosting?

You can load a Filament panel on shared hosting that offers PHP 8.2 and SSH, but imports, exports and queued notifications will be unreliable, because most shared plans do not let you keep a queue worker running. Some hosts allow a cron job that runs queue:work with --stop-when-empty every minute, which works for small exports and fails for a 50,000 row import.

Shared hosts also tend to cap memory and execution time, which is exactly what a large export or a heavy table with many relationships runs into. If the panel is used every day by staff, the move to a VPS usually pays for itself the first time an import does not have to be rerun by hand. Our guide to moving from shared hosting to a VPS covers the cutover.

Laravel Cloud or Forge for a Filament app?

Choose Laravel Forge, or another panel on a VPS, if you want a fixed monthly bill, root access and the option to run several small panels on one server. Choose Laravel Cloud if you want no server at all and the app is idle most of the day, so its compute can scale to zero. Filament runs the same on both.

The cost difference shows up with background work. Laravel Cloud Starter is $5 a month plus usage and includes one managed queue per environment, while an always awake Flex 1 GB app costs $12 a month in compute (the monthly cap) before the database. A Forge Hobby plan is $12 plus a $12 DigitalOcean droplet, with as many workers as the server can hold. The full math is on our Laravel Cloud pricing page and the Laravel Cloud vs Forge comparison.

How much does Filament hosting cost?

Hosting one Filament app on your own server costs about $22 to $24 a month with Ploi or Forge on a 2 GB DigitalOcean droplet, and $71 a month with DeployManage Starter. Filament itself is free and MIT licensed, so the bill is only server plus panel.

DigitalOcean Basic droplets are $12 for 2 GB and $24 for 4 GB. For a single panel the cheaper panels win clearly. Our fee buys team seats, an exportable deploy log and one dashboard across every cloud account; if you need none of that, use Forge or Ploi.

Why can't users log in to my Filament panel in production?

Because Filament blocks panel access outside the local environment until your User model implements the FilamentUser interface and its canAccessPanel() method returns true for that user. Locally everything works, so the first sign is a 403 right after the first deploy.

Fix it in code, not on the server: implement FilamentUser, return true for the right users (for example a verified email on your company domain or an is_admin flag), commit and push. Do not set APP_ENV=local in production to get around it, because that also turns on debug behavior you do not want a client to see.

What to put in a Filament deploy script

The Filament docs recommend caching components and icons on every deploy. A deploy script that covers Filament and Laravel together looks like this, run inside the new release:

composer install --no-dev --no-interaction --prefer-dist --optimize-autoloader
npm ci && npm run build
php artisan filament:optimize
php artisan optimize
php artisan migrate --force
php artisan queue:restart

Two notes. Node is not installed by default on a DeployManage server, so either add it once with a provisioning recipe or build assets in CI and commit them. And imports need two Laravel tables that new projects do not have: create them with php artisan make:queue-batches-table and php artisan make:notifications-table, then publish Filament's own action migrations. Queue workers are covered in our Supervisor queue worker guide.