OcaltQL

What is OcaltQL

A query language built to run on the Ocalt runtime. It is not limited to databases — it is a full execution language covering web, filesystem, media, compute, services, and more. Every OcaltQL script is a sequence of verbs, subjects, and prepositions that describe exactly what must happen and in what order.

How does it run?

Every OcaltQL script is submitted to the runtime via the /api endpoint. The runtime parses the script, executes it, and returns the result. There is no compilation step. There is no environment to configure as it is configured through the same script endpoint. Write the script, send it, get the result.

The Philosophy

OcaltQL was designed to be written the way you would describe a task out loud. There's no weird syntax and no boilerplate. A fullstop at the end of a line is optional. Uppercase or lowercase — it does not matter. The language stays out of your way. The underlying code & runtime may evolve to be more efficient but the syntax stays the same, so the next generation OcaltQL will use the same syntax but the runtime will constantly be updated. This ensures that products written in OcaltQL never need to be recoded — they only evolve & get better without altering the code.

EMIT "Hello World"

EMIT "Hello World"
AFTER CALCULATE 1 + 1 SET ?result
AFTER EMIT ?result

What OcaltQL can do

• Web — generate HTML, handle forms, bridge JavaScript, build UI
• Filesystem & Media — manage files & FTP access, process images, edit video and audio, 3D & CAD
• Database — create and query databases and tables
• Services — browser automation, email, maps, push notifications, charts, documents
• Compute — cryptography, WebAssembly, SSH, remote computing, real-time streams
• Application — accounts, chat, OOP, custom verbs, hosting, subdomains
• Network & Server — peer to peer, tunneling, transcoding, cluster orchestration, web & self hosting

Where to go next

The next page covers the OcaltQL API and client — how to connect to the runtime and send your first script.