How Qorekit is built.
For the people who look after the server or write the code: the stack, the data model, and what Qorekit expects of your hosting. The full detail is in the documentation.
- Application
- Laravel 13 on PHP 8.3 or newer
- Interface
- A Vue 3 single-page app, built at release time: the server never needs Node.js
- Database
- MySQL, MariaDB or PostgreSQL
- Web server
- Apache or LiteSpeed with .htaccess, or nginx
- Background work
- Queues and sessions in the database; cron, or after page requests when there is none
- Licence
- GNU GPL, version 3 or later, with the source beside every release
The database your host already gives you.
The whole test suite runs against each engine. Everything engine-specific lives in one place in the code, a dialect per engine; nowhere else writes raw SQL.
MySQL
5.7 or newer
Tested on 8.4
MariaDB
10.4 or newer
Tested on 11.4
PostgreSQL
13 or newer
Tested on 17
Sharing a database with another program? A table prefix keeps the tables apart. All requirements →
Real tables, real columns
What you build in the browser becomes ordinary database tables.
A table per entity
Each field is a column of a type that fits it: VARCHAR, DECIMAL, DATE. Reporting tools and plain SQL read it as it is.
In the docs →Schema changes that finish
Every change is planned, logged and applied so that one that fails part way can be finished or undone.
In the docs →Type changes keep the data
A new type builds a new column, converts the values into it and swaps it in. Qorekit shows first what happens to them.
In the docs →A doctor for the schema
qorekit:schema-doctor reports, and can repair, any gap between what was built and the tables.
In the docs →Conflicting edits caught
Each record carries a version, so two people saving the same record never overwrite each other unseen.
In the docs →One way in for every write
The interface, an import and a plugin all write through the same service: validation, permissions, audit columns and events.
In the docs →Made for shared hosting
No Redis, no websockets, no processes that keep running.
Nothing to keep running
Queues and sessions use the database. There is no worker to start and nothing to restart.
In the docs →Cron, or none
Scheduled work runs from cron, or after page requests when the host offers no cron.
In the docs →Installs three ways
The browser wizard, Softaculous and Installatron, or php artisan qorekit:install.
In the docs →A shared database is fine
A table prefix such as qk_ keeps Qorekit's tables apart from another program's.
In the docs →No build step on the server
The interface ships prebuilt. Upload the files and open the wizard.
A System page
Scheduled work, background jobs, server checks and what needs attention, in one place.
In the docs →Signed, checked, reversible
Updates come from inside the app, and nothing unsigned gets in.
Ed25519 signatures
Every package carries a SHA-256 checksum and a signature. A package that does not match the keys Qorekit ships with is refused.
In the docs →The database follows
After the new files are in place, the first request brings the database up to date.
In the docs →Going back
The previous version is kept for a week and can be put back from the same page.
In the docs →Maintenance mode
While an update runs, visitors see a short notice instead of a half-updated site.
In the docs →Your files left alone
Your data, .env, uploaded files and anything that is not part of Qorekit are never touched.
In the docs →Careful by default
Permissions are checked on the server, for every request.
Two-step verification
An authenticator app with recovery codes, turned on by each person.
In the docs →Where you are signed in
Every browser with its last use; sign one out, or all but this one. A new password signs out the rest.
In the docs →Roles and permissions
Who may see, add, change and delete, checked on every read and write, not only hidden in the interface.
In the docs →Masked values
Identity and account numbers stay masked until someone reveals them, and every reveal goes to the audit log.
In the docs →Strict browser headers
A Content Security Policy with a fresh nonce on every page, and protection from framing and content sniffing.
Code hooks off by default
PHP written inside Qorekit runs only once the server's owner turns it on.
In the docs →A public API for plugins
Plugins build on the same interfaces the core uses. They may still change before version 1.0.
PHP SDK
Field types, formula functions and listeners to record changes, through Qorekit\Sdk.
In the docs →Interface components
The Q* components of @qorekit/ui, so a plugin's screens look like the rest of Qorekit.
In the docs →A documented JSON API
The interface talks to /api/v1 with a session cookie. API tokens for other programs come with Pro.
In the docs →Language packs
Plain translation files, no code. Every name you give is translatable too.
In the docs →On your server, in your hands
Qorekit is software you run, not a service you rent.
Runs on your server
Records, files and users stay in your database and your storage folder.
Quiet on the network
Apart from email you set up and code hooks you write, the core connects out only to check for and download updates.
In the docs →Ordinary backups
Plain tables back up with your hosting panel's tools or mysqldump and pg_dump.
In the docs →Free software
The core is GPL. The source of each release sits beside it on the Download page.
Go there →Try it on your own hosting.
The installer checks the server first and says what is missing.