A proprietary technology stack we wrote ourselves between 2010 and 2024 — and keep extending. Now it's the substrate AI workers use to build Elastbiz Code and the four-app suite. Four pillars: a language, a database, an HTTP server, a widget toolkit.
The Elastic Platform isn't a collection of off-the-shelf parts glued together. EPL, the Elastic Database, the HTTP server, and the GUI widget layer were designed as one system — schema-from-classes flows directly from the language into the database; HTTP modules speak the same object model as the storage layer; widgets and web SPAs render through the same server.
That tight coupling is what lets a small team — and now AI workers on top of it — ship complex systems quickly. The same substrate that ran our prior decade of client work now runs Elastbiz Code in production.
C-like OOP scripting language with reference-counted garbage collection, native C++ plugin system, and multi-threading primitives. The substrate everything else runs on.
Hierarchical object store. Objects from EPL classes are written directly; schema derives from class attributes. Built-in SQL-like DSL embedded in EPL source.
attrib(db,...) annotationsMulti-threaded server framework with native TLS, WebSocket, virtual hosting, template engine, and a clean module pattern. The server you're reading this on.
THTTP_Module + shipCross-platform native UI components — Windows, Linux, macOS. Used for our internal tooling and any pixel-perfect parts of the web SPAs that need native rendering.
Tight integration between language, database, and HTTP layer. Build complex systems with less glue code.
Used in production since 2010 across gaming, video, enterprise, VR, and now AI-driven dev tools.
Native code execution, optimized memory management, designed for systems work — not interpreted-language overhead.
The full developer documentation walks through every API surface — syntax, types, classes, the DSL, the module pattern, layout system, threading.