Skip to content
Urukagina
← All posts

Why our demo runs entirely in your browser

· Urukagina team

  • demo
  • architecture

Most product demos in the ERP world come with a catch: a sandbox you have to request, a login that expires, or a video instead of the real thing. We wanted something you can open from a link, click around in, and break without consequences. The demo on this site does that, and it does it without a single server.

What is actually running

When you open the demo, your browser downloads a bundle that contains three things:

  1. An application server. The business logic of each demo application is transpiled to JavaScript ahead of time and runs inside a service worker.
  2. An OData gateway. The user interface talks to the backend over OData, the same protocol it would use against a real system. The service worker intercepts those requests and answers them locally.
  3. A database. A SQLite build compiled to WebAssembly holds the tables and the seed data. It lives in your browser’s cache storage.

All of this comes from open-steamgate, an MIT-licensed project that describes itself as “the layer under an ERP, not an ERP”. We package our sample applications for it and publish the result as plain static files.

What that means for you

  • No account, no waiting. The link works for anyone.
  • Your own copy. Every visitor gets an isolated database. Change anything, approve anything, delete anything. Clearing the browser cache resets it.
  • It keeps working offline. After the first visit, the bundle and the database are cached.

What it does not mean

The demo shows the shape and flow of our tools on synthetic data. It is not connected to any real system, and the sample packages are deliberately self-contained: they bring their own tables, their own seed rows and their own services. Behaviour on a production ERP system depends on that system’s configuration, and the demo cannot stand in for a proof of concept there.

A note on size

The first load is heavier than a normal web page because the whole runtime arrives at once. We keep the smaller SQLite build as the default for that reason. If you are on a metered connection, wait for a Wi-Fi network before opening the demo.

Trying it

Open the Demo entry in the navigation. You land on a launchpad with one tile per application. Start with Workflow Designer: load a change-request type, look at the graph, drag a node, and export the result.