O
OpenMathLab
Engineering Computing Environment
Connecting…
Engineering Workspace
Numerical computing, simulation, visualization and engineering systems.
Session starting
FREE ACCESS • NO LOGIN • PRIVATE WORKSPACES

Build, simulate and understand complex systems.

OpenMathLab brings numerical computing, modeling, simulation and advanced engineering workflows into one browser workspace.

✓ No login, no subscription. Each browser gets a private workspace; export projects to your computer.
SYSTEM STATUS

OpenMathLab Core

LIVE
Numerical engineReady
Simulation engineReady
Advanced systemsReady
Project storageFile-first
Functions—
Cataloged Blocks—
Toolboxes—
Advanced Systems—
WORKBENCHES

Everything in one workspace

◌Toolbox EcosystemDiscover scientific, engineering and modeling capabilities.
↔Portable ProjectsImport and export complete file-first project packages.
INTELLIGENCE CONFIGURATION

Connect your AI assistant

Choose a cloud API or a local model running on the OpenMathLab server computer. You control when a message or code is shared.

CONNECTION

Provider configuration

Not tested

Keys stay in server memory only, and are cleared on restart or by the Remove key button.

Select your provider to get started.
ASSISTANT

Try a conversation

Your conversation appears here. Messages are not saved to SQLite or project files.

Review suggested code changes

A response containing a fenced MATLAB or Octave code block can be previewed. AI cannot change or execute your project without your explicit approval.

No code change proposed.

AI calls can incur provider charges. Include code only when you intend to share it with the selected provider.

Local AI and multiple users

Ollama, LM Studio and vLLM addresses refer to the machine running OpenMathLab. If OpenMathLab is hosted remotely, localhost on your personal PC is not accessible to the server. Remote-user local models need a separate trusted local connector. Each visitor has separate private AI preferences in no-login mode.

PERSONAL HARDWARE · COMPUTE

Compute & GPUs

Your GPU, your choice. GPU operations run in your browser or on your own separate GPU worker — never on the machine hosting OpenMathLab.

EXECUTION TARGET

Hardware connection

Not checked

The GPU token is never sent to OpenMathLab's Python server, SQLite database, or project ZIP. Keep it private. For remote GPU workers use HTTPS and explicit allowed origins.

Choose a compute target to start.
GPU device information will appear here after detection.
HARDWARE TEST

Run an operation

Real GPU / no fallback
GPU worker jobs are processed on your own GPU machine, not the OpenMathLab host.
Select a GPU mode, detect hardware, then run a sample.
GPU execution boundaries

WebGPU supports compatible browsers and hardware. The separate GPU worker requires a GPU-enabled PyTorch installation on your machine and your configured CORS origin. Browser WebGPU currently supports matrix multiplication and vector addition; the separate worker supports eight bounded operations. General MATLAB scripts, arbitrary Simulink models and full GPU toolboxes still run through the existing CPU runtime and are not silently moved to a GPU. The browser-only status journal does not independently verify GPU worker claims, and running GPU kernels cannot be force-cancelled. Public Internet deployment still requires additional security hardening.

FREE ACCESS · OPTIONAL COLLABORATION

Private sessions & project sharing

No accounts, registration, or passwords. Each browser has a private visitor identity. Share revisioned projects using one-time invitations; ZIPs always remain portable.

PRIVATE SESSION

Your browser identity

Checking…
Free anonymous private workspace. No login required.

Collaboration project

Start a collaboration project, then generate a one-time invitation code for a teammate. The teammate pastes the project ID and invite code to join. This shares revisioned text changes, not the full project ZIP or binary datasets.

No project loaded
Live collaboration: not connected

Published text is journaled in SQLite. Use Download snapshot for a portable ZIP; binary files must still be exported from the main project manager.

INVITATIONS

Share securely

Explicit permissions
Project members and revision details will appear here.

This is revision-based collaboration with conflicts detected, not simultaneous CRDT co-editing. Keep downloading ZIPs to preserve complete projects.

ADMINISTRATION · READ ONLY

Operations overview

Account and workload counts without revealing anyone's scripts, API keys, files, or GPU credentials.

Deployment health

Administrators only
Select Refresh metrics to inspect this installation.

This dashboard does not enable public sandboxing, automatic remote GPU execution, or distributed scheduling. Public access requires additional hardening.

PERSONALIZATION

Workspace preferences

Preferences persist on this OpenMathLab installation in SQLite; your project data remains file-based.

Auto-save does not save to a server project database. Download your project ZIP to preserve work permanently.

DATA OWNERSHIP

Privacy & data

A clear view of what lives where.

Project files

Projects stay in your browser and downloaded ZIPs; optional small text-only recovery drafts are stored in this browser when autosave is enabled. Binary files are not in drafts. No SQLite project storage.

SQLite preferences

Stores appearance settings and AI provider URL/model metadata by anonymous browser profile. No AI keys.

API credentials

Held temporarily in Python server memory and sent only to the configured AI provider. Never exported in a ZIP.

AI conversations

Chat text is held in the open page; requests are sent to your configured model endpoint. Remote providers may retain data according to their policies.

OPENMATHLAB

Help & capabilities

Open engineering computing in a single Python-served environment.

Architecture

Python, FastAPI, HTML, CSS, JavaScript, Apache Arrow/Parquet (optional), and SQLite preferences. No Node/npm required.

Tips

Switch workspaces with the top navigation. In Workspace, select main.m, Command Window, or Result. Settings are separated from engineering project files.

Security

OpenMathLab has free no-login private guest workspaces. Public shared hosting requires hardened isolated workers, restricted network access and independent security verification. Guest session isolation alone is not a sandbox.

COMMAND WINDOWREADY
>> OpenMathLab ready.
>> Run a script or enter commands from the workspace.
>>
RESULTSRun code or a simulation to populate results.
StateReady
Variables0
Figures0
OUTPUT
No results yet.
FIGURESZoom with mouse wheel, drag to pan, Fit to reset, and Save PNG.
No figures yet.
◈
motor_control.modelContinuous simulation model
0 blocks • 0 connections
Double-click a library block to add it · Drag to position · Click ports to connect
chart.json
STATEFLOW OUTPUTREADY
Ready.
DATA ENGINEERING

Explore your datasets

Inspect columns and records, convert formats, and package data with your project.

Choose a CSV, Parquet, Arrow or Feather file to get started.
▥

Your data, clearly organized

Browse CSV without optional packages. For Parquet and Arrow, install Apache PyArrow.

Advanced Systems
OPENMATHLAB+

Engineering systems beyond the classic desktop workflow.

Digital twins, experiment design, uncertainty, surrogate models, provenance and agent-assisted engineering workflows.

—advanced systems available
ADVANCED SYSTEM OUTPUTREADY
Ready.
EXPERIMENT WORKSPACE

Engineering Notebook

Write. Execute. Explain. Export.

Code and notes remain in your browser until exported or added to the project.
PRIVATE GUEST EXECUTION

Compute Job Center

Review isolated CPU jobs and client-reported personal GPU jobs. GPU requests never pass through the hosting compute server.

New isolated CPU job

Docker only

Uses the script from Workspace → Code. The worker has no network, host mounts or GPU access. It is stateless and cannot change your live Workspace.

Enable OPENMATHLAB_WORKER_MODE=docker and build the worker image first.

My CPU and personal GPU job history

0 jobs

Personal GPU statuses are reported by your browser, not independently verified by this server. Continue checking your own GPU worker for authoritative status; this journal never saves tokens or numerical inputs.