A Real PaaS for Modern PHP
Deploy Laravel and Symfony applications with git push. Scale with gigalixir ps:scale.
Escape the limitations of shared hosting and the complexity of managing your own VPS. Get a professional, containerized runtime.
For too long, PHP deployment has meant FTP uploads or messy rsync scripts.
Gigalixir brings the professional "git push" workflow to the PHP ecosystem.Treat your PHP application like the software product it is.
You push your code, and we build an immutable release artifact. This eliminates the "it works on my machine" issues caused by inconsistent server environments or manual file modifications.
Modern PHP frameworks require specific setups: background queues, scheduled tasks, and CLI tooling.
We support them natively.
The buildpack includes the common PHP extensions required by modern frameworks (mbstring, pdo_pgsql, gd, xml, etc.) by default.
If you need a specific version or a niche extension, you can configure it via composer.json or a custom buildpack configuration.
Run administrative tasks against your production environment using gigalixir ps:run.
You can execute php artisan migrate, php bin/console cache:clear, or any other CLI command securely. This runs in a one-off container connected to your live database.
Run Laravel Horizon or simple queue workers by defining them in your Procfile.
Unlike shared hosting, where you have to hack together cron jobs to keep workers running,
Gigalixir runs your worker processes continuously. You can scale them independently of your web traffic.
PHP apps often rely on a database to do the heavy lifting.
We provide the infrastructure to ensure that foundation is solid.
The Questions We Get The Most at Gigalixir Support
We provide managed PostgreSQL, which is a powerful alternative to MySQL and is fully supported by all major PHP ORMs.
If your application strictly requires MySQL (e.g., legacy codebases using raw SQL), you can provision a MySQL database from an external provider (like Aiven or AWS RDS) and connect to it from Gigalixir by setting the DATABASE_URL.
You do not edit php.ini directly on the server. Instead, you can create a .user.ini file in your document root or modify the buildpack configuration options.
This allows you to override settings like memory_limit, upload_max_filesize, and post_max_size to suit your application's needs.
Technically yes, but with a major caveat: Gigalixir uses an ephemeral filesystem.
This means that any media files uploaded to wp-content/uploads will be deleted when the application restarts.
To run WordPress successfully, you must install a plugin that offloads media storage to Amazon S3 or Google Cloud Storage immediately upon upload.
Modern frameworks often serve files from a public/ subdirectory rather than the project root.
You can create a Procfile and specify the document root in your web command, or use a .buildpacks configuration to set the DOCUMENT_ROOT environment variable (e.g., web: vendor/bin/heroku-php-nginx -C nginx.conf public/).
Just run git push gigalixir main. We pull the new code, update dependencies via Composer, and restart the PHP-FPM process with zero downtime.
Your users will seamlessly transition to the new version without error pages.
Reach out directly to the Engineers who built Gigalixir to discuss your specific architecture, integration challenges, or compliance constraints here 👇
Stop fighting generic cloud infrastructure.
Whether you’re working with Elixir, Python, or Node.js, get the specialized support and performance your application deserves.