// the find
Fincept-Corporation/FinceptTerminal
FinceptTerminal is a modern finance application offering advanced market analytics, investment research, and economic data tools, designed for interactive exploration and data-driven decision-making in a user-friendly environment.
A native C++20/Qt6 desktop finance terminal with embedded Python 3.11 for analytics, data connectors, and basic trading/AI-agent tooling, shipped under AGPL-3.0 as the free counterpart to a paid 'Enterprise' product the same company sells. It's aimed at students, hobbyists, and academics who want a Bloomberg-terminal-style app without a subscription; anyone building a commercial or hosted product on it runs into both the license and the vendor's own upsell funnel.
The single-binary native architecture is a real technical choice, not just a selling point — C++20/Qt6 shell with embedded Python for the analytics layer avoids an Electron runtime entirely, and the pinned toolchain (CMake/Ninja/Qt/Python versions) plus CI (arch-ratchet checks, nightly sanitizer runs, lint gates) suggests someone is actually enforcing build discipline on the native side. The breadth of data connectors (100+, spanning FRED, IMF, World Bank, exchange feeds) and analytics modules (DCF, LBO, options pricing, an 18-module QuantLib wrapper) means a lot is usable out of the box without writing glue code yourself.
The README is mostly a pricing page: two separate paid-tier pitches (Enterprise and Quantcept) before you get to a description of what the open repo does, and the project openly states it now ships one release a month because the team's daily effort goes into the closed Enterprise build — this repo is the loss-leader, not the product. AGPL-3.0 is a hard blocker for a lot of use cases: host a modified build as a service and you're obligated to publish your changes, which rules out most commercial reuse outright. The 'bring your own LLM key' model for the 37 AI agents has no cost ceiling, and with this many agents and connectors wired up, that bill adds up fast with no guardrails mentioned. The codebase is enormous and sprawling (hundreds of individual Python scripts under dozens of analytics submodules) with no clear signal of per-module maturity — breadth is easy to see, depth and correctness of any given piece (say, the LBO or options pricing code) you'd have to verify yourself.