The stack behind our games, engines, and analytics.
Technology is Ghost Citadel’s credibility layer. It explains the languages, data engines, graphics systems, and performance methods used across the studio.
It is not the product page, and it is not the consulting page. It is the technical map beneath both.
Different tools for different pressure points.
Python is not used for the same reason as C. Julia is not used for the same reason as Rust. Polars and DuckDB are not decorative dependencies. Each part of the stack has a role, a boundary, and a failure mode we design around.
TECHNOLOGY MAP
Python, C, Julia, Rust, R.
Where each language belongs: orchestration, native kernels, numerical work, systems safety, and statistical analysis.
→ 02 · Data StackPolars, DuckDB, Arrow.
Columnar analytics, local query execution, event-log handling, Parquet outputs, and open data movement.
→ 03 · Graphics Stackraylib, shaders, 3D.
The runtime craft behind Linux-first games: cameras, input, rendering, effects, and asset discipline.
→ 04 · PerformanceNative, ARM, Linux, WASM.
Memory layout, hot loops, profiling, target hardware, and regression guardrails for real execution.
→Technology explains the craft. Other sections carry the business job.
This page should not sell diagnostics, consulting, or individual games. It should make the visitor understand why Ghost Citadel can build them.
Observatory
The process-mining product built from the data-engine and performance stack.
Scriptorium
The applied engineering offer when a customer needs custom work.
Games
The playable products built from the graphics and runtime stack.