TECHNOLOGY FOUNDATION
Polyglot by Design
Mythos Systems does not begin with a favorite language and force every product into it. Each system is decomposed into responsibilities, native performance, security, web experience, AI integration, automation, data management, and observability, and the technology stack is chosen to match.
Primary Technology Families
Rust
Secure, high-performance foundation for native and infrastructure-facing components where correctness, concurrency, and resource control matter most.
Python
Model, automation, integration, and research layer where ecosystem depth and iteration speed create the greatest engineering advantage.
TypeScript & SvelteKit
Rich user interfaces with structured application behavior, public sites, dashboards, and operational control surfaces.
Tauri
Modern interfaces with native application boundaries and lower runtime overhead than traditional desktop shells.
Go
Service simplicity, portability, networking, and operational deployment where native interface integration is not the priority.
Data Systems
SQLite is appropriate for local applications, embedded authoritative state, private user data, and offline-capable systems.
PostgreSQL is appropriate for multi-user systems, shared server applications, hosted services, and richer concurrency.
Mythos Systems uses embedded or server databases according to the ownership and concurrency model of the product.
Native, Web, and Hybrid
Native
Terminal and IDE systems, hardware integration, local models, secure vaults, and offline operation.
Web
Public content, broad accessibility, hosted collaboration, dashboards, and documentation.
Browser-Local
Privacy-conscious inference, optional local intelligence, client-side retrieval, and controlled public knowledge assistants.
Hybrid
Native application with hosted identity, cloud model routing, local model support, synchronization, and collaboration.
WebLLM and WebGPU
WebLLM enables selected language models to run in a supported browser using WebGPU. Mythos Systems uses this when public or private content can be processed locally, server inference cost should be minimized, and the website remains usable without the model.