Your Apps
Apps directory:
Qbix Server
Running
Qbix ServerLong-lived bearer tokens for API access, CI/CD, and AI assistants. Each user manages their own keys.
🔑 New API Key Created
Copy this token now. It will not be shown again.
Verify that the server binary hasn't been tampered with. For advanced users and auditing.
Paste a PEM private key to add your signature to this binary. Multiple signers can sign independently for M-of-N verification.
Automatically set up new domains when someone visits your server with a new domain name. They point their DNS at your server, and the first visit triggers certificate provisioning and site setup.
Q classes are preloaded. Try Q::app(), Q_Config::getAll(), Q_Request::url(). Ctrl+Enter to run.
Messages shown here were written by third parties on external platforms. They are displayed as plain text and are never interpreted.
Deploy your app to remote Qbix servers, or federate events across nodes.
This server's mesh identity:
Scanning for nearby peers...
Detecting…
No builds yet.
No build history.
Detecting frameworks...
Takes effect gradually as workers finish their current requests. Each worker handles one request at a time. More workers = more concurrent requests, but also more memory.
Recurring tasks that run on a schedule. Each runs in its own isolated process. Tasks created here are persisted in your panel config. Config-file tasks can be toggled but must be edited in the config.
Apply a preset configuration bundle. Each adjusts multiple settings to optimize for a specific use case.
Generate a link — the invited person will set their own username and password.
Set a username and password for the user (you will need to share the password with them).
Select which apps and domains this manager can administer.
Set file access tiers per app and optionally per branch.
Leave empty to remove the email address.
Each branch is an isolated copy of your app with its own subdomain and database, for testing changes without affecting the live site.
Each branch gets its own cloned database with separate credentials, so branches can't read or modify each other's data (or the live site's).
The server auto-detects databases from your app's config files (.env, wp-config.php, Qbix local.json, etc.). Use these fields only if you want to override the auto-detected source — for example, to clone from a staging database that doesn't contain sensitive production data.
Upload a SQL file to create a template database for this app. New branches will clone from this template instead of the live database, keeping production data safe.
You can also upload a files archive (.zip or .tar.gz) containing template assets like user avatars or uploads that should come with each branch.
No pending merge requests.