What SixPreflight is

SixPreflight looks at a server the way a careful engineer would, before your shop opens on it.

Upload one folder, open it in a browser, set a password, and press a button. A few seconds later you get one plain sentence — ready to open, or not ready, and exactly what to fix first.

It is free, and it works whether you drop it into your 6amMart codebase or point it at a bare server that has nothing installed on it yet.

What it is

A single folder of PHP. Nothing to install first — no Composer, no build step, no npm, no framework. It needs PHP 8.2 or newer and the pdo_mysql, json, mbstring and session extensions, which any server that can run 6amMart already has.

Open the folder in a browser, choose a password on the first screen, and press Check now. About a hundred checks later — more on a deeper pass — you get one sentence, a letter grade, and an ordered list of what to fix, each with the exact command or setting that fixes it.

It only ever reads. It never changes a setting for you, and it is safe to run on a live shop with real customers on it.

What it costs you to skip it

A shop can look completely normal in a browser while its payment gateway has no working credentials, its push notifications go nowhere, its .env file is downloadable by anyone who guesses the URL, its scheduled jobs have never run once, and its database is set up to use a fraction of the memory you are paying for.

None of that shows up in the browser. It shows up when a real customer places a real order and something quietly fails — a payment that never settles, a vendor who never gets paid, a rider's marker that never moves. By then it costs you a refund, a support ticket, or a customer who does not come back.

SixPreflight is the check you run before any of that happens, and it costs you nothing but the few seconds it takes to read the answer.

The three ways it runs

SixPreflight works out what it is looking at, and changes what it tells you accordingly.

Inside your 6amMart codebase

Every check runs, including the ones written from the 6amMart codebase specifically: the scheduler that pays your stores and riders, and whether it has actually run; modules switched on in the admin panel but missing from the server; the exact PHP extensions 6amMart's own packages need; the websocket behind live delivery tracking, end to end; and your Firebase, Google Maps, payment, SMS and email credentials — contacted for real, not just checked for being non-empty.

On a plain server

No application needed. Point it at a fresh server with nothing installed and it still checks the hardware, PHP, the database engine, the web server, file permissions, and what the internet can reach. This is the mode to use while you are still choosing a server or setting one up — see the server and configuration guide for what to build before you install anything.

Embedded in SixPanel

If you run 6amMart through SixPanel, you already have this. It is mounted inside your shop as the panel's own Shop check-up page, with the settings SixPanel already manages pointed at the panel screen that owns them instead of at instructions you would have to apply by hand.

That works on both SixPanel runtimes — the recommended one, which installs nginx, PHP-FPM, MariaDB and Redis from the chosen release's own packages under systemd, and SixPanel Docker, which runs the same services in containers with the versions pinned by the images. See Running inside SixPanel.

Does it actually work

It was run on real servers, and the results are published rather than described: 97 out of 100, grade A on SixPanel and 96, grade A on SixPanel Docker, with no red rows on either.

Treat that as a starting point rather than a proof — it is us scanning our own servers. The reason it is checkable is that the tool is free and read-only, so you can run the same scan on the same kind of box and compare rows, not adjectives.

One caveat that applies to any score, ours included: a single red row caps the number at 88 regardless of how the rest went, so the number is a prompt to read the rows rather than a substitute for reading them. Reading the report explains why.

What it never does

• Never changes a setting on your server — every finding is something you apply yourself
• Never writes to an application table
• Never sends an email or SMS to a real person
• Makes only GET requests to your own site during the exposure tests — it never posts

Where to go next

• Install SixPreflight — where the folder goes, and your first scan
• What it checks — the full list, step by step
• The server and configuration guide — if you are still choosing or building a server