* Front-end code is compiled from Python to JS with Skulpt (http://skulpt.org)
* The back-end code runs in a custom Python sandbox. Calls to server functions go over a secure web socket (this lets us do fun things like returning database rows directly from server functions, rather than faffing with REST APIs all day)
* The built-in database (Data Tables) is based on Postgres, using its JSONB and GIN indexing to create a table you can search efficiently on any column. This also means that things like transactions are properly robust.
(Right now, it does run in the browser, but we'll be moving it to the back-end soon to improve performance. For now it's good enough.)
From the Skulpt website: "Skulpt is an entirely in-browser implementation of Python."
It sounds like you implemented python in JS, so there is no compilation to JS. The application code is always python and is evaluated on the client, no?
If you move it to the back end, would that not be something like Trascrypt?
Skulpt has a separate compiler stage that compiles Python to JS, and a runtime library. There's no need to eval() that code in the same JS VM that compiled it, so it's totally feasible to ship the JS to the client and run it there.