Deploy a Laravel app with MariaDB, free

Put a Laravel app online on its own HTTPS address, with a real MariaDB database beside it and an editor in the browser, on the free plan. Start from our starter with one click, or bring your own Laravel app: Uppcoder runs composer install, sets APP_KEY, runs your migrations and starts the scheduler.

What you get on the free plan

The free plan (Spark) runs one app with one database. No card needed, and no time limit: if we ever change or end it, you hear from us by email at least 60 days before.

  • One app with one database: 2 GB of memory and 2 GB of disk
  • An editor in the browser and a terminal in the same container as the app
  • Its own HTTPS address from the first minute
  • SSH from your own editor, if you prefer it
  • Backed up every night to a separate server, the free plan included

Sign up and take the free plan

Sign up at portal.uppcoder.com, then go to Billing, Available Plans, Spark, Start free. The free plan asks you to confirm your email address first: press Send me the link, then click the link in that email.

One click: the starter's Deploy button

Open github.com/Uppcoder/laravel-mariadb-starter and press Deploy to Uppcoder. The deploy page opens with the starter already set up: Laravel as the main app, connected to its own MariaDB 11 database. Give the app a name, press Deploy, check the summary and press Confirm and deploy. Uppcoder clones the repository, runs composer install, sets APP_KEY, runs php artisan migrate and starts the app. The first start takes about a minute after Deployment Complete; until then the address answers 502.

  • Uppcoder/laravel-mariadb-starter on GitHub: a small Laravel 13 notes app on MariaDB, a migration, /status, the HTTPS proxy trusted, a Deploy to Uppcoder button.
The deploy page started from the Laravel + MariaDB starter: Laravel connected to MariaDB 11
The deploy page started from the Laravel + MariaDB starter: Laravel connected to MariaDB 11
The summary before deploying: Laravel, public address, connected to MariaDB; MariaDB 11, private; fits your plan
The summary before deploying: Laravel, public address, connected to MariaDB; MariaDB 11, private; fits your plan
Deployment Complete, with the app's own address
Deployment Complete, with the app's own address

Try it

Open the app's address: it is a small notes page, and each note you add is a row in the notes table that the migration created. /status checks the database and shows the driver, the MariaDB version and the number of notes. The app starts private, behind your Uppcoder login, until you make it public.

/status on the app's address: app ok, database ok, MariaDB 11.8
/status on the app's address: app ok, database ok, MariaDB 11.8
The notes page with the first note added
The notes page with the first note added

The database is already wired in

The app gets the database as DB_CONNECTION=mariadb, DB_HOST, DB_PORT, DB_DATABASE, DB_USERNAME and DB_PASSWORD in its environment. Laravel reads these before .env, so no password sits in your code or in your repository. The app runs on PHP 8.4 with Composer, as php artisan serve, and php artisan schedule:work runs your scheduled tasks (routes/console.php) beside it. Both are ordinary programs in ~/.config/supervisor.d/laravel.conf, yours to change, with their logs in ~/log. To add a package, run composer require <package> in the web terminal; for a new migration, php artisan make:migration, then php artisan migrate. To work from your own machine instead, open Connect with SSH on the stack page and connect from your editor's remote mode (VS Code Remote - SSH, Cursor, JetBrains Gateway, Zed).

Bring your own Laravel app

Build a stack from the Laravel + MariaDB template (Stacks, Create), then paste your repository's https address on the Laravel card, with an access token if it is private. The repository needs artisan at its root. Uppcoder runs composer install, copies .env.example to .env if there is no .env, sets APP_KEY if none is set, and runs php artisan migrate on the stack's database. Your code is not changed. Uppcoder's proxy ends HTTPS in front of the app, so add trustProxies(at: '*') in bootstrap/app.php (the starter has it), or url() and asset() give http:// links on an https page. One path is taken: /health is answered by the platform itself (its health check), so give your own status route another name.

Share it

When you want other people to use it, switch Private to Public at the top of the stack page. It changes at once, with no restart, and anyone with the link can open it. The editor, the terminal and the files always stay behind your login.

Questions about Laravel on Uppcoder

Is it really free, and for how long?

Yes. The free plan (Spark) runs one app with one database, needs no card and has no time limit. If we ever change or end it, you hear from us by email at least 60 days before.

How does my Laravel app reach MariaDB?

Through DB_CONNECTION=mariadb, DB_HOST, DB_PORT, DB_DATABASE, DB_USERNAME and DB_PASSWORD in the environment. Laravel reads them before .env, so the default config/database.php works unchanged.

Which PHP version does it run?

PHP 8.4, with Composer, pdo_mysql, pdo_pgsql, mbstring, bcmath, gd, redis and zip.

Do scheduled tasks run?

Yes. php artisan schedule:work runs beside the app and checks routes/console.php every minute.

Why do my links say http:// on an https page?

Uppcoder's proxy ends HTTPS in front of the app. Add trustProxies(at: '*') in bootstrap/app.php, as the starter does, and Laravel builds https links.

My app answers /health with just "OK". Why?

The platform answers /health itself: it is the container's health check. Give your own status route another name, such as /status, as the starter does.

Can I work from my own editor instead of the browser?

Yes. Open Connect with SSH on the stack page, create a key with one click, then use the ssh command or add the lines to ~/.ssh/config for VS Code Remote - SSH, Cursor, JetBrains Gateway or Zed.

Laravel, its database and an editor, live from one click, on the free plan.