Changelog

What changed in each version of Qorekit. Versions follow semantic versioning; until 1.0, a new minor version may change how things work, and the release notes say so.

0.1.0-beta.1

Released on 14 November 2026.

The first public beta. Everything below is new. Try it in the demo or install it; please do not trust it with data you cannot afford to lose yet.

Building in the browser

• Modules, entities and fields, created and changed in the browser. Every entity is a real database table and every field a column, on MySQL, MariaDB or PostgreSQL.
• 19 field types: short, long and rich text, email, web address (also as a video or audio player, or an embedded page), phone, whole and decimal numbers, money, automatic numbers, date, date and time, yes or no, single and multiple choice, related records, users, files and images.
• Fields can be renamed, get a new key, new settings, become required or unique, and even change their type. Qorekit first shows what the change would do to the values already stored, and can clear those it cannot convert.
• A trash for fields: a field in the trash keeps its column and values until it is deleted for good.
• A heading for each entity: the field that names its records in lists, related record fields and the record panel.
• Choice lists, shared by any number of fields, with colours, a default item and items that can be retired without touching old records.
• The list of each entity is designed in the browser: its columns, their order and the default sort, kept as a draft until published.

Working with records

• Lists a page at a time, quick with a hundred thousand records on ordinary shared hosting.
• Records open in a panel beside the list, or on a page of their own.
• Two people editing the same record cannot overwrite each other's changes.
• A trash for records, and deleting them for good for those who may.
• Sensitive values (such as identity or account numbers) are shown masked; revealing one is written to the audit log.
• Uploaded files and images are served only to people who may see their record; program files are never accepted.

People and permissions

• Users, with fields of your own added to them.
• Roles that decide, for each entity, who may see, add, change and delete records: all of them, only their own, or none. A person with several roles gets the widest access of them.
• Administration permissions open building, choice lists, user management, list design and the trash to people who are not administrators. User managers can give only the roles their own roles allow.
• Everyone can change their password; deactivating a user signs them out everywhere. Signing in slows down after repeated wrong passwords.

Installing and running

• An installation wizard that checks the server, sets up the database (or a table prefix in a shared one) and the first administrator. The same from the command line.
• Made for shared hosting: Apache or LiteSpeed with .htaccess, nginx pointed at public/, no Redis, no websockets, no processes that keep running.
• Scheduled work from cron, or, without cron, after page requests. Administration › System shows how it runs and what needs attention.
• Updates from within Qorekit: packages are signed and checked before anything is replaced, the database is brought up to date by itself, and the previous version is kept for a week to go back to.
• Packages for hosting panels' app installers (Softaculous and Installatron).
• A demo mode for public demos that start afresh every few hours.

The interface

• English and Turkish, chosen by each person; the server answers in the same language.
• Light and dark themes, usable with the keyboard alone and on a phone.
• Installation settings for the default language, time zone, date and number formats, the record panel's width and the sites that may be embedded.

Not in this beta yet

These are planned for the coming versions:

• Searching and filtering in lists (the API can already search).
• Importing and exporting records, forms, dashboards and reports.
• Email, notifications and automations.
• API tokens for other programs; for now the API uses the interface's session.
• Plugins, and the features of Qorekit Pro.