QueryAdmin

Overview

QueryAdmin is to OcaltQL what phpMyAdmin is to a database: a place to see and change everything, without writing anything. Databases and their tables and rows, files across your storage, subdomains, domains, email addresses, FTP logins, scheduled work, your private network, and a console for running OcaltQL directly.

Everything QueryAdmin does, it does through the same commands a script would use. There is no private back door and nothing it can reach that your own scripts cannot.

What it is

A persistent control plane for the account. The left of the product is a structured sidebar of domain-specific tools. The right — one click away at all times — is the query console, for when the panel is the long way around.

Because QueryAdmin operates on the identical namespace and credentials model as the rest of Ocalt, anything expressible in OcaltQL can be inspected, configured, or orchestrated from this single surface. No credit card is required to explore it.

What it does

• Browse and edit tables, insert and delete rows, export a database as SQL, CSV, JSON or Excel — then import it back.
• Move through your files, edit them in place, compress and extract archives, and hand out share links.
• Create subdomains and point domains at them. Provision email addresses on any domain you hold.
• Mint FTP logins scoped to a single folder and revoke them when they are done.
• Watch what is scheduled and what is running. Inspect machines, maps, CAD assets and quotas.
• Run OcaltQL in the built-in console without leaving the panel.

How it works

Every panel is built from the verbs OcaltQL already has. Nothing is simulated and nothing is cached behind your back — what QueryAdmin shows you is what a script would see at that moment.

That is why a change made in the console appears in the table view, and a row edited in the table is what the next SELECT returns. There is one namespace, not a UI copy of it.

Getting started

1. Open admin.ocalt.com with your Ocalt account.
2. Create a database from the sidebar, add a table, insert a row. Export it as JSON so you can see the shape.
3. Open the console and SELECT ROWS FROM DB "…" TABLE "…". Confirm it matches.
4. Upload a file, share it, revoke the share. Then do the same with FILE SHARE in the console.

NEW DB "sales"
AFTER NEW TABLE "orders" IN DB "sales" COLUMNS ADD "ref" TYPE STRING AND ADD "status" TYPE STRING
AFTER INSERT INTO DB "sales" TABLE "orders" ROW "ref" AS "A-1001" AND "status" AS "open"
AFTER SELECT ROWS FROM DB "sales" TABLE "orders" WHERE "status" IS IDENTICAL TO "open" SET ?rows
AFTER COUNT ?rows SET ?n
AFTER EMIT ?n & " orders still open"

Surfaces in the sidebar

Permissions

When you act as a business, QueryAdmin shows that namespace, not your personal one. Member grants are the same grants the runtime enforces: files, databases, subdomains, machines, mail, scripts. A bookkeeper can reach databases and mail without touching a machine; an engineer can reach machines without seeing the ledger.

The plan, the billing and the API key never leave the owner. QueryAdmin will not offer those controls to a member who cannot hold them.

Limits and plans

The console is available on every tier, including Free. What you can actually create — mounted storage, query volume, machine slots — follows the account plan. QueryAdmin will show you the quota rather than fail silently.

Every action in the panel is a query against the daily allowance, the same as a script. Heavy clicking on large tables spends the same resource a loop would.

Related products

FAQ

Is QueryAdmin required?

No. Anything it does, a script can do. It exists so you can see the shape of what you have built before changing it, and so you can click when you would rather not type.

Can I break production from the panel?

Yes, in the same way you can from a script. There is no staging copy. Dropping a table drops the table. Use member grants and a separate namespace when the blast radius matters.