qualinvest

Qualinvest is a tool box for quantitative analysis and management of financial asset portfolios. Currently, it consists of three components:

• qualinvest_core: A library implementing the core functionality used by the binary tools. The library supports parsing automatic transaction documents (currently only from comdirect Bank), Bank account and user management, position and P&L calculations. Data is stored persistently in PostgreSQL database. The library relies heavily on finql, another rust library providing methods for financial analysis.

• qualinvest_cli: A command line interface to qualinvest_core. It supports commands for database renewal, insertion of objects into the database, uploading and parsing documents, and updating of market data quotes. It is mainly useful as an administration tool and for automating processes, e.g. updating market data once a day or every few hours.

• qualinvest_server: A http based GUI interface with multiple user support. Each user has only access to the specified set of accounts and the transactions in that accounts. Currently, view and management of transactions is supported as well as viewing position and P&L.

Please note that the toolbox is still in an early development stage and will be extended by more useful functionality in the near future. Though, if you miss a feature, please send me a note to help me prioritize the future developments.

Install instructions

The tools can be build basically by means of the cargo utilities, but with some extra preparation.

Since we use the compile-time-check feature by means of the sqlx-macros, a PostgreSQL database for testing needs to be setup prior to compilation, with the module pgcrypto enabled and all tables setup (but empty). Once the tools are build, all tables can be create for a new, empty database automatically by the command:

qualinvest_core --init-database --config config.toml

where the config file contains the credentials for the new, empty database.

Security Configuration for Production

⚠️ IMPORTANT: Before deploying to production, you MUST configure the following security settings:

1. Enable HTTPS

The application uses secure session cookies that require HTTPS. For production deployments:

• Deploy behind a reverse proxy (nginx, caddy, etc.) with TLS/SSL configured
• Ensure all traffic is encrypted with HTTPS
• The session cookies are configured with secure, http_only, and same_site flags for maximum security

2. Database Security

• Use strong, unique passwords for your PostgreSQL database
• Restrict database access to localhost or specific IP addresses
• Enable SSL mode for database connections in production
• Regularly update the pgcrypto extension and PostgreSQL version

Other stuff

We use pictograms from Entypo pictograms by Daniel Bruce — www.entypo.com, licensed under http://creativecommons.org/licenses/by-sa/4.0/.