Live Demos
Eight live demos, one for each AltSql module built so far. Each runs the module’s own prototype code, compiled to WebAssembly, in your browser. The devices, their sensors and links, and their memory chips are simulated. Nothing needs installing, and nothing you do leaves the page.
Simulated devices, real code. Run without interference, each demo shows the figures its Alpha report gives for it. AltSql Vector’s differ a little in a browser, as its report explains.
AltSql Core: Three Devices, One Engine
A machine sensor, a truck’s cold-chain logger and a soil sensor run the same engine. Each keeps its own records, decides for itself and sends only what matters to its gateway, where the same records arrive byte for byte. Pull the plug on any of them at any moment.
AltSql Ask: Ask 500 Machines One Question
Each machine keeps a day of readings in its own AltSql database. You ask in SQL. The gateway turns the question into a small program, every machine answers from its own records, and only the answers travel back.
AltSql Vector: Teach a Device What Normal Sounds Like
A vibration sensor sits on a motor. Every 1.6 seconds the device turns what it hears into a fingerprint, looks for the closest one it was taught, and names the state, or flags a pattern it does not know. You can teach it on the spot.
AltSql Wave: Find the Burst That Shows the Fault
A vibration sensor on a pump’s motor keeps a 1.6-second burst four times a day, compressed without losing a bit, and sends only the burst’s features to the gateway. After three weeks a bearing starts to fail. Search the features with SQL, then fetch the raw signal behind any row.
AltSql Mesh: Twelve Devices, One Table, No Signal
A sheep farm with no mobile coverage and no gateway. Three utes, four quad bikes and five people on foot carry a device each. They read the water troughs, open and close gates, add jobs and clear them, and count sheep, all into one shared table. Whenever two come within radio range they sync, over a link that loses messages. Stop the writing and watch every device end up with the same table.
AltSql Realtime: A 10 ms Deadline on a Chip That Takes 45 ms to Erase
A controller runs a loop 100 times a second. Every cycle it writes one value, its state or, every tenth cycle, one of its settings, and logs a row, and those writes must be done within 10 ms of the cycle’s start. Its flash chip needs 45 ms to erase a sector, and up to 400 ms. AltSql Core erases inside the write that needs the room. AltSql Realtime never erases inside a write, and works out from its configuration the most any write can cost. It erases only when the loop calls idle: here, between cycles, while the chip erases in the background.
AltSql Instant: A Sensor With No Battery
A small solar cell charges a capacitor. When it is full, the sensor wakes, opens its store and saves readings, one after another, until the capacitor is empty and the power goes, wherever the sensor is at that moment: between readings, or in the middle of a write. Then it charges again, and wakes again, many times a minute. Two sensors, the same light, the same capacitor: one keeps its readings with AltSql Instant on MRAM, the other with AltSql Core on NOR flash.
AltSql DB: A Whole Fleet in One File
Twelve devices running AltSql Core sync into one AltSql DB file on their gateway, each device’s bytes stored as it wrote them. Ask with SQL and see the plan, read a device’s newest reading by the direct path beside SQL, and cut the gateway’s power in the middle of a commit.
If a Demo Does Not Start
The demos work in any current Chrome, Edge, Firefox or Safari, on a computer or a phone, with JavaScript switched on. They need WebAssembly, which all of them support. Each demo’s code comes with its page and runs inside it. If a demo says its engine could not start, try another browser, or allow scripts on the page if an extension blocks them.
If a check ever fails, the demo says so in red, and the project would be glad to hear about it through the contact page.
The modules and what each is for are on the modules page.