Quasar brings together trading, artificial intelligence and private communication
Quasar grows as an independent software ecosystem with its own products, its own infrastructure and one set of engineering principles.
The philosophy
Modern applications are often assembled from dozens of external services, cloud platforms and closed APIs. That speeds up the launch, but hands control over the product to other companies.
Quasar is built differently: critical technology belongs to the ecosystem itself. We use proven system libraries and standards, but the architecture, the product logic, the infrastructure and the direction of development stay under our control.
Three directions
Quasar Trading Terminal — a released product: a trading terminal with a trade journal and risk management, running on Windows, macOS and Linux.
Quasar AI — the longest-running direction: our own intelligent core, knowledge, memory, analysis tools and a software agent.
Quasar Messenger — work that has just begun: private communication with no central storage of personal correspondence, the first client on Linux.
These are not three unrelated applications: in time the core will be able to work inside the terminal, the messenger will carry private communication, and one infrastructure will join accounts, devices and services. Each product nevertheless stays on its own feet — the failure of one must not stop the rest.
One engineering foundation
The main products are written in C++ and Qt 6. A single foundation gives predictable performance, controlled use of resources and desktop interfaces that do not depend on a browser.
The site, the mail, the documentation, the downloads, the forum and the blog are our own modules too, running on our own infrastructure.
Public progress, closed technology
We publish news, development stages, product concepts and user documentation. The source code of the key components stays closed. Being closed does not stand in for security: the protection rests on a considered architecture, modern cryptography, separation of powers and keeping the data available to the server to a minimum.
What comes next
The order of work is simple: the foundation first, scale afterwards. Architecture and protocol, a working version for Linux, testing, builds for the other systems, a separate mobile adaptation, integration with the ecosystem.
About Quasar — the philosophy, the three directions and a map of how they are connected.