One software ecosystem for trading, artificial intelligence and private communication.
Quasar is built as an independent technological system: our own code, our own infrastructure, our own products and one set of engineering principles.
We are not assembling a random set of ready-made services. Every Quasar product is designed as part of one ecosystem and develops under our control — from the server architecture and the computing core to the desktop interface.
Modern applications are often built out of dozens of external services, cloud platforms and closed APIs. That speeds up the launch, but hands control over the product to other companies.
The Quasar philosophy is different: critical technology must belong to the ecosystem itself. We may use proven system libraries and standards, but the architecture, the product logic, the infrastructure and the direction of development stay under our control.
Our own technologyThe key components of Quasar are developed inside the project. That lets us understand how the whole system works, govern its quality and not depend on a third-party platform changing overnight.
One engineering foundationThe main Quasar products are written in C++ and Qt 6. That is a shared technological base for high performance, controlled resource usage and solid desktop interfaces.
Privacy by architecturePrivacy must be provided by the way the system is built, not by promises alone. A server must not receive data and keys it does not need to do its job.
A product must be usefulResearch matters, but the work must end in real applications. Quasar Trading has already walked that path from an idea to a working product. Quasar Messenger and Quasar AI will grow the same way.
Products
One ecosystem — three directions
Quasar Trading Terminal
Released · 1.0.2
The first finished user product of the ecosystem. The trading terminal brings work with the market, a trade journal and risk management together in one application.
Building it shaped the main Quasar approach: Linux first as the principal development environment, then a native build and verification of the product on the other operating systems.
The most complex and longest-running research direction of Quasar, under development for more than six months.
Quasar AI is not somebody else’s model plugged in under a new name. The project includes our own intelligent core, a knowledge system, memory, analysis tools and an agent able to work with projects and software tools.
A new private-communication project inside the ecosystem. Its goal is a messenger in which personal correspondence is not kept in a central server database.
When both people are online, the data goes straight between their devices. If the recipient is unavailable, encrypted fragments are temporarily spread among the participants of the network and later reassembled on the recipient’s device.
The first client is being built for Linux only. Once the core and the network protocol are stable, the port to other desktop and mobile platforms begins.
These are not three unrelated applications. In time Quasar AI will be able to work inside the terminal and the other products, Messenger will carry private communication, and one infrastructure will join identity, devices and the ecosystem’s services.
Each product must nevertheless stay on its own feet: the failure of one component must not stop the rest.
Development
The foundation first, scale afterwards
We do not try to release a product for every existing platform at once. The main development happens on Linux, where the architecture, the core and the first working version are built and verified.
Once the base is stable, the product is built and adapted inside the target operating system itself. Mobile applications are a separate stage, with the limits of iOS and Android taken into account.
Architecture and protocol
A working version for Linux
Testing and stabilisation
Builds for the other desktop systems
A separate mobile adaptation
Integration with the ecosystem
Independence
Public progress — closed technology
Quasar publishes news, development stages, product concepts and user documentation. The source code of the key components stays closed.
Closed code must not stand in for security. The products are protected by a considered architecture, modern cryptography, separation of powers and keeping the data available to the server infrastructure to a minimum.
The architecture of Quasar Messenger is being designed so that the servers do not hold the keys that decrypt personal correspondence. No administrative mechanism for obtaining the plain text of messages is to exist in the infrastructure.
Infrastructure
Our own infrastructure
The ecosystem runs on its own server architecture. The main node serves the public services and routes the additional load to the servers of the farm.
As the project grows, the infrastructure can be extended with new nodes without changing the overall model of the ecosystem.
Community
Quasar is more than applications
The site brings together the project’s news, documentation, downloads, blog and forum.
We show the real progress of development: what already works, what is being worked on and what exists only in plans so far. Project statuses must be clear and must not suggest that unfinished features are already available to users.
Build our own. Understand every level. Keep control.
Quasar grows step by step: from a working trading terminal to our own intelligent system and a private communication network. Every new product strengthens the ecosystem while keeping its independence, its performance and one set of engineering principles.