For investors and institutional evaluators
Everything we've built.
Nothing we haven't.
Finmind is a financial platform for Uzbekistan with a free core and pay-per-feature modules: portfolio, brokerage, market data, tax, wealth planning and personal finance in one system. This page is its register. Every figure below is read from the running platform, through a cache of a few minutes, or stamped with the day we measured it.
Deciding whether to fund
You are in the right place. The register below is the whole company, limits included.
Deciding whether to buy
Banks, insurers, funds and regulators have their own surface. Finmind for institutions.


Contents
Rendered 2026-10-21 04:08 UTC. Figures marked live come from the platform's API through a cache of a few minutes.
The company
What Finmind is
A financial-intelligence platform for Uzbekistan: capital markets, FX, commodities and macro data consolidated from official sources, with portfolio, accounting, the country's real personal income-tax engine, credit, insurance, pension and advisory built on top. Market data, learning, the AI assistant, brokerage connection, portfolio and the simulator are free for every user; the rest is in two paid plans, Premium and Expert, bought for 30 days or a year and never renewed automatically.
- Features live today
- 79
- from the catalogue API, cached for a few minutes
- Product categories
- 10
- from the catalogue API, cached for a few minutes
- Premium plan price
- 79 000,00 UZS / month
- from the plans API, read at render time
- Upstream systems live
- 11 of 26
- the platform's integrations registry → 26 entries (11 live / 8 partial / 4 designed / 3 blocked), counted 2026-08-29 after the KATM credit bureau was declared alongside the first-party bank catalogues; the development database trails until its next seed run
- Backend tests
- 1 753+
- pytest collection on the measurement date → "1753 tests collected"; one module still being wired up is EXCLUDED from the count rather than counted optimistically
- Automation engines, one order seam
- 6
- one dedicated backend module per engine, counted in the repository; every one routes through the single validated order seam
Live figures read from the platform's API through a cache of a few minutes; measured figures observed 23.08.2026 against the running system. Sources printed beneath each.
Real or null
A price on Finmind comes from a named source or it is null, rendered as “n/a” with a machine-readable reason. Zero is a claim; we only make it when a source did.
Live or measured, labelled either way
Counts and prices marked live are read from the platform's own API, through a cache of a few minutes; everything else was observed once, on 23.08.2026, with the measurement that produced it printed further down. There is no third category.
Money is exact, end to end
NUMERIC(38,2) in the database (146 columns of it), decimal strings on the wire, BigInt minor-unit arithmetic in the browser. Checkable in one query: the schema contains 0 double-precision or real columns, anywhere, of any kind.
Cited, or it does not save
Tax computations carry their Tax Code article basis, and a statutory parameter cannot be saved at all without naming the decree that set it: the refusal is a database CHECK constraint, not a code convention or a review habit.
Owner-scoped, server-gated
Portfolio, orders, messages, declarations are owner-scoped at the query level, so one user's data is structurally invisible to another; feature entitlements are enforced as API permissions on the backend, not as hidden buttons.
Refuse rather than corrupt
The declaration PDF will not render at all without a font that can draw Uzbek and Cyrillic glyphs. A silently corrupted tax document is worse than a failed download.
The market
Why Uzbekistan, and why this shape
Uzbekistan's financial infrastructure publishes more than most people use: the exchange its asking prices, the central bank its rates, the disclosure portal its filings, the tax code its every article. What does not exist is the layer that joins them for a person or an institution: no e-filing API, no broker fill callback, no open-banking framework, and instruments, share classes and statutory parameters that are local in ways imported software gets wrong. That gap is the company; the limits chapter below names each of those constraints and what we built against it.
We publish no market-size estimate: a TAM slide is a claim about other people's money, and this register confines itself to claims about our own work.
The landscape
Where Finmind sits among the others
Ten other services serve the Uzbek retail investor, and only two of them are brokerage apps: GoInvest and Jett open brokerage accounts and route orders to UZSE through licensed brokers, which Finmind does not do. fondbozori.uz is the exchange's own trading system, used through a member broker, and the one Finmind connects to. Stockscope, Moniq, DaykonInvest and uzstock.uz are data sites, Xisob Terminal is a market-data terminal and dfin.uz a financial-literacy site, as Finmind's public pages are; Cbonds is an international data provider that covers Uzbek bonds and shares among its countries. The table states only what each service's own pages documented on the day we read them, with the page cited under every cell; a feature a service has and does not document is marked not published, not absent. Two GoInvest cells rest on what Finmind saw in the app itself, and say so.
Analytics layer over your brokerage account
Finmind
Reads the customer's existing fondbozori.uz brokerage account and adds market data, fundamentals, portfolio, tax and advisory tools on top. Opens no brokerage account and is not a broker.
Brokerage app of a licensed broker
GoInvest
The trading app operated by GoInvest LLC and published by Kapital-Depozit LLC, a UZSE member: remote brokerage account opening and trading on UZSE from iOS and Android.
Brokerage app of a licensed broker
Jett
A trading service run by Multibroker LLC; a new brokerage account is opened with the licensed broker Alkes Research, and the brokerage itself is provided by its partner brokers. iOS, Android and web.
The exchange's trading system, used through brokers
fondbozori.uz
The exchange's own web and mobile trading terminal (WTS and MTS), run by the state Information-Resource Centre of the Stock Market: every member broker's clients place orders and see their positions in it. Not a broker; access comes through a member broker. This is the system Finmind connects to.
Data and analytics site
Stockscope
A UZSE market overview and screener with a watchlist and a portfolio page, run by Wandering Ventures LLC. No trading.
Data and analytics site
Moniq
A catalogue of UZSE stocks, corporate bonds and bank deposits with a portfolio that imports broker reports, a payout calendar and Telegram notifications. No trading; a broker directory instead.
Data and analytics site
DaykonInvest
A UZSE share catalogue with multiples, yearly statements, a screener, TWR portfolios and alerts, run by an individual developer as a web app and a Telegram bot, in Russian. Not a broker; it directs readers to licensed brokers.
Market-data terminal without trading
Xisob Terminal
A free web terminal with a live tape of UZSE shares and bonds, openinfo.uz disclosures, a dividend calendar, news, alerts and a documented JSON API, built by an individual. No trading; its guide names brokers instead.
Financial-literacy site with free tools
dfin.uz
A financial-literacy publication with free tools, live since February 2026 under the name Direct Finance: articles, calculators, a trading simulator, a manual portfolio tracker and one UZSE share page so far. No trading; its guide sends readers to the broker apps.
Data and analytics site
uzstock.uz
An analysis site for UZSE issuers, live since September 2026 under the name UZ Stock Analyzer: filings parsed from openinfo.uz with multiples per company, quotes, a bond analytics page, AI-generated reports and a manual portfolio in a PRO tier. No trading; the operator is not named.
International financial data provider
Cbonds
A global fixed-income data provider operated by Global Bond Data FZE: bond, share and issuer data for Uzbekistan among its countries, a screener, a portfolio, an Excel add-in, apps and an API for companies, behind registration. Not a broker; no Uzbek interface.
Analytics layer over your brokerage account
Finmind
Company analysis
Market data
Trading and accounts
Tax and assistant
Languages, apps and API
Brokerage app of a licensed broker
GoInvest
Company analysis
Market data
Bonds and portfolio
Trading and accounts
Tax and assistant
Brokerage app of a licensed broker
Jett
Company analysis
Market data
Bonds and portfolio
Trading and accounts
Tax and assistant
The exchange's trading system, used through brokers
fondbozori.uz
Market data
Bonds and portfolio
Trading and accounts
- Places orders on UZSE
- Yes, the exchange's terminal, used through a member broker18
- Opens a brokerage account
- No, opened with a member broker; the exchange's page links here to start trading20
- Connects an existing brokerage account
- No, it is the terminal the brokerage account lives in18
- IPO applications
- Not published, the exchange publishes the IPO and SPO schedule20
Tax and assistant
Languages, apps and API
- Uzbek-language interface
- Yes, Latin script; Russian and English as well18
- App in the App Store and Google Play
- Not published, a mobile web terminal19
- Works inside Telegram
- Not published18
- Public API documentation
- Not published, no documentation published18
- Published price list
- Not published, the member broker's tariff applies18
Data and analytics site
Stockscope
Company analysis
Trading and accounts
Tax and assistant
Data and analytics site
Moniq
Company analysis
Market data
Trading and accounts
Tax and assistant
Data and analytics site
DaykonInvest
Company analysis
Market data
Bonds and portfolio
Trading and accounts
Tax and assistant
Market-data terminal without trading
Xisob Terminal
Company analysis
Market data
Bonds and portfolio
Trading and accounts
Tax and assistant
Languages, apps and API
- Uzbek-language interface
- Yes, Latin and Cyrillic; Russian and English as well31
- App in the App Store and Google Play
- Not published, web31
- Works inside Telegram
- Not published, reads Telegram channels as a news source31
- Public API documentation
- Yes, JSON and WebSocket endpoints32
- Published price list
- Not published, says it is free35
Financial-literacy site with free tools
dfin.uz
Company analysis
Market data
Bonds and portfolio
Trading and accounts
Tax and assistant
Languages, apps and API
- Uzbek-language interface
- Yes, Latin script; Russian and English as well36
- App in the App Store and Google Play
- No, its apps page says no apps yet41
- Works inside Telegram
- Not published, a channel43
- Public API documentation
- Not published36
- Published price list
- Not published, says there is no paid subscription42
Data and analytics site
uzstock.uz
Company analysis
Market data
Bonds and portfolio
Trading and accounts
Tax and assistant
Languages, apps and API
- Uzbek-language interface
- Yes, Latin script; Russian and English as well44
- App in the App Store and Google Play
- Not published, web44
- Works inside Telegram
- Not published44
- Public API documentation
- Not published, open JSON endpoints without documentation44
- Published price list
- Not published, a free plan and a PRO tier; no amounts44
International financial data provider
Cbonds
Company analysis
Market data
Bonds and portfolio
Trading and accounts
Tax and assistant
Languages, apps and API
- Uzbek-language interface
- No, not among its listed languages; English, and Russian on cbonds.ru48
- App in the App Store and Google Play
- Yes57
- Works inside Telegram
- Not published, news channels58
- Public API documentation
- Yes, an API catalogue; access is sold to companies only56
- Published price list
- Not published, says pricing is tailored per client; a trial is offered59
Sources
- 1.finmind.uz/ (opens in a new tab) read on 26.09.2026
- 2.finmind.uz/stocks (opens in a new tab) read on 26.09.2026
- 3.finmind.uz/uzse-bonds (opens in a new tab) read on 26.09.2026
- 4.finmind.uz/business (opens in a new tab) read on 26.09.2026
- 5.finmind.uz/api/v1/docs/ (opens in a new tab) read on 26.09.2026
- 6.finmind.uz/uz/business (opens in a new tab) read on 26.09.2026
- 7.goinvest.uz/ (opens in a new tab) read on 26.09.2026
- 8.goinvest.uz/uz (opens in a new tab) read on 26.09.2026
- 9.play.google.com/store/apps/details?id=org.uicgroup.goinvest (opens in a new tab) read on 26.09.2026
- 10.apps.apple.com/uz/app/goinvest-investment-app/id6748455336 (opens in a new tab) read on 26.09.2026
- 11.uic.group/ru/portfolio/goinvest-mobile-app (opens in a new tab) read on 26.09.2026
- 12.uz.kursiv.media/2026-05-07/ipo-uznif-jett/ (opens in a new tab) read on 26.09.2026
- 13.jett.uz/ru/ (opens in a new tab) read on 26.09.2026
- 14.jett.uz/uz/ (opens in a new tab) read on 26.09.2026
- 15.play.google.com/store/apps/details?id=uz.multibroker.jett.mobile (opens in a new tab) read on 26.09.2026
- 16.jett.uz/ru/plans/ (opens in a new tab) read on 26.09.2026
- 17.www.gazeta.uz/ru/2026/05/08/jett/ (opens in a new tab) read on 26.09.2026
- 18.fondbozori.uz/usx/ (opens in a new tab) read on 26.09.2026
- 19.fondbozori.uz/usx/m/index.html?lang=EN (opens in a new tab) read on 26.09.2026
- 20.uzse.uz/?locale=en (opens in a new tab) read on 26.09.2026
- 21.stockscope.uz/en (opens in a new tab) read on 26.09.2026
- 22.stockscope.uz/en/screener (opens in a new tab) read on 26.09.2026
- 23.stockscope.uz/en/about (opens in a new tab) read on 26.09.2026
- 24.moniq.uz/en (opens in a new tab) read on 26.09.2026
- 25.moniq.uz/ru/investments/bonds (opens in a new tab) read on 26.09.2026
- 26.moniq.uz/ru/directory/brokers (opens in a new tab) read on 26.09.2026
- 27.daykon.uz/ (opens in a new tab) read on 26.09.2026
- 28.daykon.uz/stock/UZTL (opens in a new tab) read on 26.09.2026
- 29.daykon.uz/stocks (opens in a new tab) read on 26.09.2026
- 30.t.me/DaykonUz_bot (opens in a new tab) read on 26.09.2026
- 31.xisobterminal.uz/ (opens in a new tab) read on 26.09.2026
- 32.xisobterminal.uz/docs (opens in a new tab) read on 26.09.2026
- 33.xisobterminal.uz/aksiya/UZTL (opens in a new tab) read on 26.09.2026
- 34.xisobterminal.uz/blog/uzse-brokerlar-taqqoslash-2026 (opens in a new tab) read on 26.09.2026
- 35.xisobterminal.uz/blog/xisob-terminal-qanday-ishlatiladi (opens in a new tab) read on 26.09.2026
- 36.www.dfin.uz/en/about (opens in a new tab) read on 26.09.2026
- 37.www.dfin.uz/en/stocks (opens in a new tab) read on 26.09.2026
- 38.www.dfin.uz/en/stocks/uznif (opens in a new tab) read on 26.09.2026
- 39.www.dfin.uz/en/guide (opens in a new tab) read on 26.09.2026
- 40.www.dfin.uz/ru/rukovodstva/kak-kupit-aktsii-v-uzbekistane-poshagovaya-instruktsiya-2026 (opens in a new tab) read on 26.09.2026
- 41.www.dfin.uz/en/app (opens in a new tab) read on 26.09.2026
- 42.www.dfin.uz/terms-of-use (opens in a new tab) read on 26.09.2026
- 43.t.me/dfinuz (opens in a new tab) read on 26.09.2026
- 44.uzstock.uz/ (opens in a new tab) read on 26.09.2026
- 45.uzstock.uz/api/market/stocks (opens in a new tab) read on 26.09.2026
- 46.uzstock.uz/api/catalog/status (opens in a new tab) read on 26.09.2026
- 47.uzstock.uz/api/bonds (opens in a new tab) read on 26.09.2026
- 48.cbonds.com/about/ (opens in a new tab) read on 26.09.2026
- 49.cbonds.com/country/Uzbekistan-bond/ (opens in a new tab) read on 26.09.2026
- 50.cbonds.com/stocks/UZ7011340005/ (opens in a new tab) read on 26.09.2026
- 51.cbonds.com/bonds/1668509/ (opens in a new tab) read on 26.09.2026
- 52.cbonds.com/bonds/ (opens in a new tab) read on 26.09.2026
- 53.cbonds.com/portfolio/ (opens in a new tab) read on 26.09.2026
- 54.cbonds.com/watchlist/ (opens in a new tab) read on 26.09.2026
- 55.cbonds.com/ai-bonds/ (opens in a new tab) read on 26.09.2026
- 56.cbonds.com/api/ (opens in a new tab) read on 26.09.2026
- 57.cbonds.com/promo_mobile/ (opens in a new tab) read on 26.09.2026
- 58.t.me/cbondsglobal (opens in a new tab) read on 26.09.2026
- 59.cbonds.com/subscription/ (opens in a new tab) read on 26.09.2026
Last reviewed 26.09.2026. A cell states only what the named page published on the day we read it; a feature a service has and does not document is marked not published, not absent. Nothing here is a judgement of quality, and no figure is estimated.
A reader who has no brokerage account yet opens one with a licensed broker first: how to open a brokerage account in Uzbekistan and connect it to Finmind lists the exchange's member brokers without endorsing any.
The proof
One order nobody typed
On 06.08.2026 a take-profit rule, row 21 in our own stop-loss table, was armed and then left alone. Five days later, on 11.08.2026 at 13:26:00 Tashkent time, the monitor saw the target trade with real executed size and fired it. Nine seconds after that the order was at the exchange and the broker had returned its own order id 1829 (11.08.2026).
The rule placed a real sell order, 6 171 148 shares of UZNF at 5,55 UZS, which is 34 249 871,40 UZS at that limit, with nobody watching. The two halves are not a coincidence of timing: rule 21 stores the id of the order it placed, #53, as a foreign key to brokerage order #53. Both rows are quoted below, exactly as measured.
We stop the sentence there on purpose. There is no fill callback from this broker; an execution shows only in its own live order list, which the reader we built on 23.08.2026 copies verbatim and never backfills (limit 01 below), so the order above is still not called a fill and 0 orders on this platform carry an observed execution today. “Accepted and resting at the exchange” remains the strongest thing we can honestly say about any order sent through this broker, this one included.
- Orders that reached the broker, of 44 recorded
- 33
- Accepted, each with the broker's own order id
- 12
- Rejected: 21 by the broker, 9 by our own pre-flight
- 30
The whole ledger, refusal by refusal
A partial ledger is worse than none. 44 order rows exist all-time: 33 left this platform and reached the broker; 9 never did, because our own pre-flight refused them first (a closed market, not enough order-available cash, an instrument we could not label, or a limit price already outside the published band); and 2 were cancelled before submission. We count those 9 as ours, not as broker traffic, because they are.
Of the broker's 21 refusals we keep the broker's own message word-for-word on 18 of them and append a plain-language hint that is plainly ours; the remaining 3 arrived with no usable text at all and fall back to our own generic sentence rather than to a reason the broker never gave. We rewrite nothing and delete nothing: a platform that hides its refusals cannot be audited.
5 of all those rejections were our own defect, a decimal-padding bug in the order payload, root-caused and fixed on 27.07.2026 and none since. July produced 21 rejections in all; the other 16 that month, and every rejection after it, are ordinary market refusals, 9 of them on 04.08.2026, where the limit price sat outside the exchange's band for that day. (measured 23.08.2026 against brokerage order #53; counted in the order ledger: rows with a submission timestamp, plus rows carrying a broker refusal.)
read directly from the protective-rule ledger, row 21: kind target, status executed, UZNF
read directly from the order ledger, row 53, on the measurement date
quantity × limit price from order #53, recomputed to the tiyin
What is built
Every feature, read from the catalogue
Generated from the production feature catalogue at request time, the same catalogue the in-app pricing page and the billing system read. It is not a slide: nothing can appear here that a user cannot use for free or buy.
Personal Finance
15 featuresA double-entry ledger under the whole household: holdings and imported broker statements book into it, budgets and spending analytics read out of it, and the local shapes, the family budget and the gap (rotating savings circle), are first-class objects, not skins on a generic app.
Wealth & Retirement
9 featuresThe long-horizon half. Returns deflated by the real published CPI rather than an assumed rate; volatility, VaR and drawdown in Decimal; look-through exposure that sees the issuers inside your funds; both statutory pension projections resolved from cited decrees; zakat against a nisab built from the real gold spot. A figure the data cannot support comes back null with its reason, never as a comforting number.
Markets & Data
18 featuresThe warehouse and everything that reads it: prices, the sovereign yield curve, issuer disclosures, corporate actions, macro series, the index and the screener. Every row traces to a named upstream or is not there at all.
Commodities & Real Assets
4 featuresGold at the central bank's own published bar prices, UZEX commodity trading, and real-estate reference data.
Global & Crypto
3 featuresOutside the country: US equities and crypto quotes, plus the connection layer for foreign exchanges and brokers.
Trading & Automation
8 featuresEverything that can move real money, all of it through one validated order seam: broker sync, live tickets, protective brackets, the AI lab, copy trading and algo trading. Autopilot ships inside Algo Trading: one entitlement, not a second SKU.
Research & Analysis
5 featuresValuations, predictions and company analysis. Where a ratio cannot be computed it is emitted as null with the reason recorded, per instrument and per ratio, rather than as a plausible multiple.
Rates & Comparisons
7 featuresThe comparisons households actually shop on (deposits, loans, cards, insurance and commercial FX) across the licensed local providers, from their own published terms. Under the same heading, where those banks physically are: 6,600+ ATMs, branches and currency-exchange offices from the Central Bank's own register, every one geocoded, so a rate comparison ends at an address you can walk to rather than a number on a page.
Advisory & Assurance
6 featuresAdvisory surfaces and the assistant, which proposes and then waits: nothing it suggests acts until the user explicitly approves it. Alongside them, auditing and compliance workspaces, for the users who have to prove something to somebody.
Learn
4 featuresTutorials, progress streaks, and a beginner simulator that fills against real last prices while being wired to no broker at all.
Prices as returned by the catalogue API through a cache of a few minutes: set by a platform administrator, current rather than permanent. Full descriptions are on the landing page.
Under the hood
What the code actually does
Each claim below is written against the code as it runs today; no roadmap items appear on this page. Open a card for the point-by-point receipts.
Brokerage integration at the protocol level
Finmind speaks the UZSE broker terminal protocol (fondbozori.uz) natively, not as a screen-scrape, and live order placement works: 12 of our orders have been accepted by the broker and carry its own order id.
Brokerage integration at the protocol level
- The login cryptography is locked to test vectors byte-for-byte (SHA-1 → base64 → nonce → MD5 → base64), asserted by both the Python client's tests and the Go client's.
- The sync client is data-inquiry only, enforced by a test that greps the module for order-path tokens, not merely by intention; cash and holdings sync read-only with freshness tracking.
- An execution is recorded only by asking the broker: a reconciliation sweep reads its own live order list and copies the executed quantity it reports, never infers one. A partial stays open, a zero is not an observation, and nothing is backfilled, so 0 orders here carry an observed execution today, which the limits below state in full.
- Broker statements can also be imported from files, so a portfolio never depends on a live connection.
Market data that is sourced, cached and honest
Every price traces to a named source: the exchange, the central bank, the state disclosure portal. Or it is null.
Market data that is sourced, cached and honest
- The market-wide order book comes from the exchange's own published asking-prices file: one fetch covers the whole market, cached for seconds and shared across all users, with a last-good snapshot for upstream hiccups. The trade panel adds the broker terminal's price levels for the security on screen.
- A non-positive price is dropped, not displayed: an empty side of the book is honest, a fabricated zero is not.
- Issuer profiles, disclosures and corporate actions from openinfo.uz; official rates and gold-bar prices from cbu.uz; consumer prices from narxtahlil.uz; global markets and crypto from Yahoo Finance and CoinGecko.
- Valuation ratios that cannot be computed are emitted as null with the reason recorded, per instrument, per ratio.
An assistant that asks permission
The AI assistant answers questions about the user's own portfolio, and when asked to act it proposes an action that does nothing until the user explicitly approves it.
An assistant that asks permission
- An approved action executes through the same validated order path as a manual order: same gates, same audit trail, same dry-run rules. Rejecting a proposal cancels it; no path from chat to execution skips approval.
- From Telegram the assistant answers, and a single trade it proposes there can be confirmed in the chat only while the user has switched Telegram trading on (off by default): the confirmation is a single-use button that expires in minutes, the switch is re-read at that moment, and the order then runs through the same gates as one placed in the app. Brackets, schedules, plans and bulk sells cannot be approved from Telegram at all.
- Statistical projections ship with the warning attached to every response: an estimate of past price behaviour, not advice and not a promise.
A religious decision we refuse to guess at
Shari'a screening to AAOIFI Standard 21 and Meezan Bank's criteria: one decisive business screen plus 7 financial ratios, across all 106 listed tickers on the exchange. 106 of 106 carry a curated sector ruling, so the business screen is never skipped for want of one.
A religious decision we refuse to guess at
- 13 tickers permissible, 84 impermissible, 9 undetermined with a machine-readable reason (4 interim-only filings + 4 unusable filings + 1 unclassified business). The market is dominated by conventional banks and insurers, and no ratio rescues a business that is impermissible in itself.
- An issuer's sector is looked up by symbol in a hand-curated map of 90 symbols: mostly exchange tickers, plus labels for issuers with only bonds listed and a few registry or older aliases, so an issuer known by two symbols is counted twice. Each ruling is made against the issuer's officially stated activity, not inferred from its name.
- “Debt” means real interest-bearing borrowing, read from the NSBU Form-1 line items. Not total liabilities, which would sweep in trade payables and wrongly fail a debt-free company.
- No Uzbek issuer discloses its non-compliant income, so the 5% purity screen is ALWAYS reported unavailable: every pass is “halal subject to income purity” at medium confidence, never a confident halal. A screen we cannot compute is reported as unavailable with its reason, never silently skipped to reach a verdict.
The wealth side, held to the same rule
The honesty discipline is not confined to the order path. The clearest proof is the insurance needs-analysis engine: it joins income, debts, dependants, liquid assets and the user's own savings goals, and when an input is missing it returns “cannot assess” with the missing list, never a need of zero.
The wealth side, held to the same rule
- Every multiplier in that engine is labelled a named industry convention and explicitly not Uzbek law, is surfaced in the response and can be overridden per call. Amounts in another currency convert at the latest central-bank rate or are excluded and reported, never summed at face value.
- Real returns deflate nominal so'm with the actual published CPI series, chained month by month. A date the series does not cover degrades to null with the exact period used disclosed; it never invents an index.
- Portfolio risk is annualized volatility, historical AND parametric VaR, maximum drawdown, beta against a UZSE benchmark and HHI concentration, computed in Decimal, not float, and nothing persisted.
- Portfolio X-ray looks through fund holdings to the underlying issuers by each fund's active constituent weights, and rolls both share classes of one issuer together by ISIN rather than by ticker suffix.
- Both statutory pension projections resolve every input from the cited-parameter table or the primary text of the pension law; an unconfigured parameter yields null with a stated reason. Zakat's nisab is built from the real gold spot and the real USD rate, or it is null.
Security posture, including the boring parts
The controls an institutional reader probes for, stated plainly.
Security posture, including the boring parts
- Brokerage credentials are Fernet-encrypted with a key that exists only in the environment: no default key, no per-process fallback. If the key is missing, every encrypt and decrypt raises. We refuse rather than persist plaintext.
- Optional Telegram two-factor login can only be enabled after a live code was actually delivered and verified; codes are hashed, expiring, attempt-capped and single-use. Two-factor is core security and is deliberately not a paid feature.
- Anything secret-like is masked by default and revealed per item behind an eye icon; list views render only the masked shape.
Built for Uzbekistan, not localized to it
The hard, local problems are the moat: the tax code, the exchange's actual publishing habits, the instruments people here actually hold.
Built for Uzbekistan, not localized to it
- Savings circles and family budgets, how households here actually save, as first-class features rather than skins.
- Deposit, loan, card and insurance comparison across local banks and insurers, with the state insurance register handled honestly (see the limits below).
- UZS as exact tiyin arithmetic, local number notation on official documents, share classes modelled explicitly rather than guessed from a ticker suffix.
- Uzbek apostrophe forms are normalised before any name match, so “O‘zbekiston” and “O'zbekiston” are one issuer and not two.
Automation
6 ways to trade, one door
Every engine below places its orders through the same validated seam as a hand-typed ticket: same checks, same audit trail, same dry-run rules. One line each; the algorithms open beneath.
Manual ticket
A human types an order; it is validated, priced against a live reference and either dry-run or sent.
Protective brackets
Standing stop-loss and take-profit rules our own monitor evaluates. The broker's order form has no stop field, so these are synthetic (see the limits).
Its 2 algorithms, one line each
- Stop-loss
- If the market trades at or below the stop with real executed size, place a plain limit sell for the live-sellable quantity.
- Take-profit
- The mirror image on the upside: the rule that produced the sale described above.
Signal algorithms
Four textbook signals plus a scheduler, each evaluated on a beat and each writing its reasoning to an audit row.
Its 5 algorithms, one line each
- MA crossover
- Buy when the fast moving average crosses above the slow one; sell on the opposite cross.
- Momentum
- Act when the N-day return passes a threshold the owner set.
- Mean reversion
- Act on the z-score of price against its own rolling mean.
- DCA
- A scheduled fixed-amount buy on an interval, regardless of signal.
- TWAP scheduler
- Slice one parent quantity into timed child orders instead of hitting a thin book at once.
AI Trading Lab
A model-driven strategy that may suggest, paper-trade or trade live, and a live order passes 10 checks, in order, before it exists.
Its one algorithm, one line each
- The gate
- Global switch, live mode, armed and not killed, broker live switch, symbol allowlist, Shari'a screen, position cap, daily loss limit, daily trade count, then full order validation.
Copy trading
Mirror another trader's orders sized as a percentage of your own portfolio, never raw share counts.
Its 2 algorithms, one line each
- Sizing
- The leader's trade is converted to a share of their portfolio, then re-applied to yours and capped per position.
- Identity
- Leaders appear under an alias, never an email; consent to be copyable is off by default and has to be switched on in settings.
Autopilot
Three standing plans the owner specified, each a draft until armed and each fill-gated rather than optimistic.
Its 3 algorithms, one line each
- Recurring buy
- Spend a fixed SUM on an interval, but only after the previous order actually reached a filled state; an unknown fill waits rather than stacking buys.
- Standing entry
- Wait for a stock you do not hold to trade inside your price range, then buy from a fixed budget, never above your maximum.
- Average down
- When price falls a step below your average cost, buy a tranche that is re-verified to lower the blended average before it goes out; equal-to-average never fires.
Usage, stated exactly: 9 protective rules have run to a conclusion in the development database, 3 triggered on real executed size and placed their order (one of them is the order above), 6 were cancelled by their owner first. 0 are armed today, and 0 autopilot plans have ever been created here. We would rather decompose the count than let a total imply live cover that is not there (measured 23.08.2026; one count over the protective-rule ledger, by status → cancelled 6, executed 3).
Autopilot is one of the 6 engines but not a separate row in the catalogue above: it ships inside Algo Trading and is gated by that one entitlement. One purchase, not a second SKU.
Money safety
What stands between an algorithm and your money
Automation that can spend real money is a liability question before it is a feature. These are the controls, not a philosophy.
- Two switches, or it is a paper trade
- An order reaches the broker only when the platform-wide live switch AND that user's own live-trading opt-in are both on; either one off and the order persists as a dry run, the broker never contacted. Both default to off.
- Draft until armed
- Every automated rule (bracket, algorithm, AI strategy, copy follow, autopilot plan) is created inert, evaluated only after its owner explicitly arms it. Pausing is one click.
- Kill switches above the strategies
- A global setting stops the AI engine, another the autopilot sweep, another the Telegram bridge, independently of anything a user has armed; a single strategy can be killed on its own.
- Caps re-derived, never counted
- The autopilot's per-run, per-plan, per-user and total-budget caps, and the AI lab's position-size cap, daily loss limit and trade count, are recomputed from the run audit on every evaluation, never kept as a counter that can drift. A figure that cannot be established blocks the run; it never defaults to zero.
- At most once per slot
- Concurrent workers claim an evaluation through a unique constraint (autopilot) or an atomic status change (stop-loss), so two beats firing together can never double-buy or double-sell.
- Pre-trade validation, every path
- One validator guards manual and automated orders alike: a listed security with a real ISIN, an existing reference price, positive quantity, a sell never exceeding the sellable quantity, a limit inside the exchange's published band.
- Confirmation before anything acts
- The assistant proposes; the user approves. An unapproved proposal does nothing, and there is no path from a chat message, in the app or on Telegram, to an order.
- Anything that can act is audited
- Strategy evaluations, mirrored trades, assistant actions, autopilot runs and broker rejections are written down with their reasons, reviewable after the fact; a rejection pauses the plan that caused it instead of retrying money into a failing pipe.
Tax and compliance
A real tax engine, down to the form
Finmind computes Uzbekistan's annual personal income-tax declaration (form 172) from the user's own ledger: the page-1 identity block, all 10 page-2 income schedules and the 12 computation rows of page 3.
The document itself
- Exports to PDF, XLSX, DOCX and JSON, in the notation the authority itself uses: 4 734 047,14 and 01.04.2026, not US formatting.
- Computed rows carry their Tax Code article basis, verified against the Code's own text, including the exchange-traded securities exemption most generic tools miss (worked through below); a citation found wrong is corrected in the code and the correction recorded, never quietly re-pointed.
- A value the engine does not know renders as “—”, never as a zero, and the warning explaining why travels inside the exported document.
Statutory parameters
Minimum wage, BHM, the pension base and the INPS rate are effective-dated named parameters: 12 rows spanning 01.01.2019 to 01.09.2026, each citing the decree that set it (PP-4086, PF-196, PF-108, PF-91, PF-115). One row exists because an operator placeholder was ten times too low; the decree amount superseded it and the row records that. An uncited parameter is refused by the schema itself, through a database CHECK constraint.
measured 23.08.2026 · one count over the statutory-parameter table; the decrees it cites → PP-4086, PF-196, PF-108, PF-91, PF-115
What that one citation is worth, worked through
A generic engine treats a securities gain as ordinary income at the general rate. The Code does not: a gain on emission securities realised on the stock exchange is exempt outright. On a hypothetical 1 000 000,00 UZS of gain on UZSE-traded shares:
120 000,00
what a 12% engine charges
Tax Code Art. 381 §1; the engine's basis note on that row reads "Art. 375 item 9 with Arts. 327-329; Art. 381 §1 (12%)"
0,00
what the Code actually charges
Tax Code Art. 378 item 7, 2nd indent; from 17.04.2025 Art. 327 §17 (O'RQ-1057); recorded as the relief basis on schedule row 8
120 000,00
the difference, per million of gain
arithmetic performed in this page, in exact minor units, on the two rates cited beside it. Not a measurement and not anyone's actual saving.
What remains is not a tax and we do not net it above, because it has a different base: a fee of 0.01% that the SELLER pays on the TRANSACTION value of an exchange trade in emission securities; the issuer is excluded, and the Code never calls it a trading tax (Tax Code Art. 327 §16; the engine's note records 0.01% on exchange trades, 0.3% organised off-exchange). A worked example is not advice, and the declaration states its basis on every row.
Provenance
26 doors, and which ones are open
Every upstream the platform touches lives in one registry with an evidence rule: an integration is marked live only when a named code path talks to it AND we have observed the data it wrote, with a row count and a date. The whole board, including the doors we cannot open.
Live(11)
a named code path talks to it and we have observed the data it wrote
Central Bank of Uzbekistan (cbu.uz)
Official UZS FX rates, policy rate, gold-bar prices, bank registry and the sovereign yield curve.
CoinGecko crypto prices (api.coingecko.com)
Crypto asset prices and market caps for the global-markets crypto strip.
Gold spot feeds (gold-api.com, Yahoo GC=F)
International gold spot price (XAU/USD) for the gold page and real-return math.
Narx-Tahlil price monitor (narxtahlil.uz)
Official consumer product price statistics for the cost-of-living view.
OpenInfo corporate disclosure portal (openinfo.uz)
Issuer disclosures, daily exchange OHLCV bars (stocks, ETFs, bonds), issuer fundamentals and the day-aggregate screener behind live quotes.
State Statistics Committee SIAT (stat.uz)
Official macro indicators (CPI, GDP and friends) for the macro dashboard.
Central Securities Depository (uzcsd.uz)
Corporate actions (dividends, meetings) from the depository's public register.
Uzbek Commodity Exchange (uzex.uz)
Commodity trade register and weekly exchange quotes for the commodities view.
Uzbek Republican Currency Exchange (uzrvb.uz)
Weighted FX rates and volumes, the interbank/repo money-market curve and government-bond auctions.
Tashkent Stock Exchange (uzse.uz)
Real-time trade tape, authoritative share registry (shares outstanding/par) and bond listings.
Yahoo Finance quotes (query1.finance.yahoo.com)
Global market quotes (US indices, big tickers) for the world-markets strip.
Partial(9)
it works, but only for part of what the upstream could give us
Fondbozori WTS brokerage terminal (fondbozori.uz)
Read-only brokerage account sync (cash, securities, statements) and live order routing to UZSE.
What it is waiting on: Brokerage account data, statements and orders need each user's terminal login; the quote, price history and member list answer without one, and there is no documented API. Brokerage account sync and order entry work. The venue pushes no fill confirmation; the only evidence of an execution is its own order list, which we now reconcile against; nothing has been observed through it yet.
Tax committee taxpayer cabinet (my.soliq.uz)
Pull the taxpayer's own income and withholding data to pre-fill the form-172 declaration we already generate offline.
What it is waiting on: The public reference catalogues are read, and the filing assistant and an importer for the cabinet's own salary export are built. The taxpayer's data and the filing itself need a per-taxpayer E-IMZO session or a Soliq-servis agreement.
Telegram Bot API (api.telegram.org)
Price alerts and notifications, two-factor codes, and the chat bridge.
What it is waiting on: Bot token in hand; notifications and the chat bridge run. The bridge deliberately cannot place an order.
Uzbek commercial banks (rate aggregators)
Deposit, loan and card rates across Uzbek banks for the comparison tables.
What it is waiting on: Rates only, via public aggregators. A direct bank connection would need a per-bank agreement; we hold none.
Uzbek bank deposit catalogue (official sites)
Deposit products read from each bank's own pages, with the terms that decide whether one is good: minimum, capitalisation, replenishment and the early-withdrawal penalty.
What it is waiting on: Read from each bank's own site, so coverage is whatever they publish: five of the 35 CBU-registered banks expose parseable deposit terms today. There is no bank API and no open-banking framework in Uzbekistan to ask for more.
Uzbek bank loan catalogue (official sites)
Loan products with the bank's own nominal and effective rates, term and amount ranges, collateral and subsidy conditions, never a rate we computed ourselves.
What it is waiting on: Five banks publish parseable loan terms out of 35 registered. We store the bank's own effective rate and never compute one to fill the gap, so a bank that publishes only a nominal rate stays partial.
Uzbek bank card catalogue (official sites)
Cards banks sell: categories, payment networks, fees and the perks exactly as each bank states them.
What it is waiting on: Three banks publish a parseable card tariff table. None of those pages prints its own updated-on date, so rows are stamped with the fetch time and say so rather than implying the bank confirmed them today.
National open-data portal (data.egov.uz)
Public state registers of licensed financial institutions: the MFO/bank-office directory, microcredit organisations, pawnshops, payment organisations and operators, e-money systems, bank auditors and the geocoded ATM register.
What it is waiting on: Read-only and GET-only, and the two registers we most want, licensed insurers and securities issuers, provably are not published there. The insurer list is served from a different upstream and labelled as such rather than borrowing this one's credibility.
NAPP e-OSGO / ERSP insurance register (e-osgo.uz, ersp.e-osgo.uz)
Two halves. Working: the public ERSP participant roster, the only machine-readable list of Uzbek insurers reachable without a contract. Blocked: per-policy OSGO verification against the state register, which would replace trusting user-typed policy data.
What it is waiting on: The participant roster is reachable and parsed. Per-policy verification is not: it needs an accredited-consumer agreement with the regulator plus an E-IMZO credential, and the public policy register is captcha-gated, which is why the insurance checker records rather than verifies.
Designed(3)
researched and specified; nothing is talking to it yet
Ministry of Employment services (mehnat.uz)
Employment records for income verification and tax pre-fill.
What it is waiting on: The public employer registry is reachable, and the tax page uses it to check an employer's STIR; no lookup has been observed in production yet. The personal labour book needs OneID and an agreement with the ministry.
Unified government services portal (my.gov.uz)
Government e-services relevant to personal finance, surfaced in-platform.
What it is waiting on: The public service catalogue is readable; the data behind each service needs a contracted OneID client, which we do not hold.
State pension system (Extrabudgetary Pension Fund)
Pull real accumulative-pension balances instead of manual entry.
What it is waiting on: No route exists for a third party: the pension ledger is shown only to its holder behind a OneID login. The holder can paste or upload their own statement, which the platform imports.
Blocked(3)
an external gate we cannot open by writing code
KATM credit bureau (infokredit.uz)
Credit score, the bureau's own scoring class and contract history, read from the report the subject downloads themselves.
What it is waiting on: Credit bureau. No consent-free API exists: a report is released only to the subject, or to a contracted member with consent, under Law O'RQ-301. Until membership, the product reads the report the subject downloads from my.gov.uz, in their own browser.
OneID national SSO (id.egov.uz)
National single sign-on returning verified PINFL, INN/STIR and passport data: no manual identity entry.
What it is waiting on: National SSO. Requires a registered client under a paid contract with the state operator, free only for state bodies.
Paynet Xolis (QR payments)
Accept feature payments by QR and confirm them automatically.
What it is waiting on: Xolis itself publishes no developer API or callback at all. The operator protocols that ARE published are already implemented here, and none is switched on, because the merchant credential only exists after a signed agreement this project does not hold. Each adapter reports itself unconfigured and its callback answers 503 rather than confirming a payment.
Signed in, this board is read live from the platform's own registry endpoint. Signed out, it is the snapshot of 23.08.2026: a front-end test asserts that snapshot still matches the backend registry file, so it cannot quietly drift out of date.
Due diligence, pre-answered
Limits we state plainly
You would find these in diligence anyway. We would rather you hear them from us, because how a platform handles what it does not know is the product.
- 01
The broker never tells us an order filled, so we ask, and we never assume
There is no fill callback here and no push of any kind; the one place this venue admits an execution is its own live order list, and reading that list is the ONLY way a fill is ever written on this platform. The rules are deliberately unflattering: a partial stays “submitted” (the rest is still working and cancellable), a zero is never written as an observation, an order the broker stops listing is left alone (absence is not evidence of a fill), a shrinking figure is an anomaly rather than an update, and there is no backfill at all; 0 orders here carry an observed execution today. Anything that depends on a fill, the recurring-buy plan for instance, reports “fill unknown” and waits.
- 02
Our stop-losses live on our servers, not the exchange's
The broker's verified order form has no stop-trigger field (the gateway raises if you try), so a stop is a rule our own monitor evaluates before placing a plain limit sell; the exchange never held it, and if our monitor is down the stop does not fire. We would rather you knew that from us than discovered it on a bad day.
- 03
The 10-level order book comes one security at a time
Our first depth requests named the security by its bare ISIN, the broker's terminal answered with an empty shell, and we read that as a venue withholding its book. The terminal's own screen code names a security as market, board and ISIN in one string; asked that way, the same public endpoint returns up to 10 price levels a side with the number of orders at each, no login needed. A pass over every listed security on 15 Sep 2026, run just after the close and so outside trading hours, found resting orders on nearly half of them. What remains is a limit of shape, not of access: the ladder comes one security per request through our broker connection, so the trade panel shows it for the security on screen, while the market-wide order book page shows the exchange's own public file, which stops at the best bid and ask.
- 04
We take payment by hand, on purpose (for now)
The code for automatic collection exists: 3 operator protocols are implemented against their published specifications (Paynet UWS, CLICK's shop API, the Payme merchant JSON-RPC) and 0 are switched on, because the credential is the part no operator hands out without a signed merchant agreement. Each adapter reports itself unconfigured and names the settings it lacks, their callback endpoint answers 503 rather than pretending to confirm a payment, and Xolis, the QR product people here actually use, publishes no developer API at all. So payment runs by hand, exactly as the business-model chapter describes. It does not scale and we know it: the code is written, the agreements are not.
- 05
Copy trading is opt-in, and the leaderboard is nearly empty because of it
Nobody is copyable by default. A profile is listed only after the user records an explicit consent (copytrade migration 0003, 30 Aug 2026, flipped the default to off and revoked every prior enrolment), always under an alias, never an email. Of the profiles on the platform only the ones that opted in appear, which is why the leaderboard is short. We would rather volunteer that here than have a privacy reviewer find it.
- 06
The insurance register has a captcha, so we record, not verify
The state register of compulsory insurance policies, ersp.e-osgo.uz, requires a captcha and offers no API, so we record what the policyholder saw and link to the authoritative register rather than claim a verification we cannot perform. Behind that limit sits an import keyed on the register's OWN identity, the series and number it prints (e.g. EUID 0386126): the same block pasted twice updates one policy instead of minting a second, the premium is never silently rewritten, and every field the paste does change is reported back with its old and new value.
- 07
There is no e-filing API, so the taxpayer files
The taxpayer cabinet offers no public API for submitting the declaration. Finmind computes and renders the exact document, in the authority's own notation, and the taxpayer files it. We will not pretend to a submission channel that does not exist.
- 08
Some statutory numbers are unknowable right now, so we say “pending”
Several caps in the tax code are multiples of decree-set amounts that are not always published in advance. When a decree is missing, the affected rows render as pending with an explanation. A declaration that quietly guessed would be worse than one that waits.
- 09
The deterministic parser is proven; the language model is not
Money instructions go through a deterministic intent parser that runs FIRST and handles everything it recognises: holdings, net worth, prices, orders, standing plans. The language model sees only what the parser did not understand, and anything it proposes is rebuilt by the same proposal builders, behind the same approval and order validation, so no order-safety property depends on the model. What we have not proven is the model half itself: the API key in the container has never been probed live, and if the provider rejects it the assistant falls back to the parser silently. We would rather tell you that than let you assume an LLM you have not seen work.
- 10
We have no traction metrics to show you, so this page shows none
No user counts, no AUM, no revenue claims, no testimonials, no logos. What we can demonstrate is the running system itself, driven live, with its own gaps named as we reach them. We would rather earn the other numbers than assert them.
Business model
Three plans, priced per market
Free covers market data and learning for every Finmind account. Premium opens every analytic and tool; Expert adds automation, AI trading and advisory. Each is bought for 30 days or a year and does not renew automatically, and every entitlement is enforced as a server-side permission. Organisations evaluate the basic features for their type, then agree a contract.
Premium plan, current price
79 000,00 UZS / month
790 000,00 UZS / year
Read from the plans API when this page is rendered. An introductory, market-entry price: set by a platform administrator, changeable at any time. Not a unit-economics claim, and no revenue figure appears on this page because there is none to report.
How we actually take the money
Priced on the server: the amount comes from the plan row, never the browser. A reference QR carrying our own payment reference and amount, explicitly not a provider-signed payload (the API says so on every payment). Paid out of band; a sysadmin confirms the money arrived, and that approval alone creates the time-boxed entitlement. Append-only afterwards: there is no delete endpoint, and a payment row can only be superseded, never removed.
Why the third step is manual is limit 04 above: the 3 operator adapters are written and 0 are switched on, because the credential only exists after a signed merchant agreement. The day one is signed, approval becomes automatic.
Evidence
How you can check us
None of these is a traction metric. They are the size and shape of the thing itself, and every one is reproducible in an afternoon with us in the room.
| Figure | What it is | How it was measured |
|---|---|---|
| 1 753+ | backend tests collected by pytest, and rising | pytest collection on the measurement date → "1753 tests collected"; one module still being wired up is EXCLUDED from the count rather than counted optimistically |
| 108+ | backend test files, and rising | a filesystem walk of the backend tree, counting test files |
| 38+ | front-end assertion suites run with node --test, and rising | a filesystem walk of the frontend tree, counting node --test suites |
| 146 | NUMERIC(38,2) columns: the money scale, the most common numeric shape in the schema | one query over the database's own column catalogue: NUMERIC columns at precision 38, scale 2, schema-wide |
| 0 | double precision or real columns in the entire schema: the “money is never a float” rule, stated as a fact about the database rather than as a coding habit | one query over the database's own column catalogue: columns typed double precision or real, schema-wide |
| 0 | orders on this platform carry an execution observed from the broker: the reconciler writes only what the broker's own order list returns today and never backfills, so no order here has ever been called filled | the observed-fill fields arrive with a schema migration dated 23.08.2026 that the development database has not applied yet, so no row can hold one; the only writer is the fill reconciler, whose NO BACKFILL rule leaves an order the broker no longer lists genuinely unknown |
| 13 | listed tickers came back permissible, and every one of them is “halal subject to income purity” at medium confidence, because the purity screen cannot be run here | the full screening run, re-executed in a backend shell on the measurement date → 13 permissible, 84 impermissible, 9 undetermined |
| 84 | came back impermissible: the exchange is dominated by conventional banks and insurers, whose core business no ratio can rescue | the same screening run: the impermissible share of its coverage |
| 9 | are reported undetermined with a machine-readable reason: 4 whose only filings cover an unfinished year, 4 whose filings yield no computable ratio, 1 whose issuer record stops at a risky sector with no sub-industry. None is guessed either way | the same screening run: its machine-readable reasons → interim statements 4, unusable statements 4, unclassified business 1 |
| 18 358 | daily price bars | one count over the price-bar warehouse |
| 5 920 | official currency rates | one count over the official-rate table |
| 2 429 | sovereign yield-curve points | one count over the yield-curve table |
| 552 | issuer disclosures | one count over the disclosure table |
| 546 | corporate actions | one count over the corporate-actions table |
| 154 | imported issuer financial reports | one count over the imported financial reports |
| 141 | macro indicator series | one count over the macro series table |
| 110 | instruments: 106 stock rows and 4 bond rows | one count over the instrument table, grouped by type |
| 67 | bond listings | one count over the bond listings |
| 35 | licensed banks from the central bank's register | one count over the central-bank registry mirror |
| 51 | insurance products from 10 insurers | one count over the insurance product table |
| — | users, assets under management, revenue: there are none to report, so the cell is blank rather than absent | nothing to run: the platform is pre-revenue and pre-launch |
All measured 23.08.2026 against the running system. These counts move (the warehouse grows every day the schedulers run), which is exactly why each one is stamped with a date and its measurement instead of being presented as timeless. A figure printed with a + is a floor: re-measure it and expect to get more, never less. Backend tests: at least, measured 23.08.2026 · pytest collection on the measurement date → "1753 tests collected"; one module still being wired up is EXCLUDED from the count rather than counted optimistically.
The raise
There is a live fundraise. This page states no terms.
Contact details read from the platform's own public settings. Change them in the admin surface and they change here within a few minutes.
Stage, amount, valuation and use of funds are conversations, not web copy: we would rather answer your questions directly than publish a number this register cannot bind to a source.
Ask for a walkthrough and we will drive the running system with you watching: the catalogue, the declaration export, the order ticket, and the rejected orders, which are the part that tells you whether the rest is real.
Blog
Latest from Finmind
Guides to Finmind and plain explanations of investing and personal finance in Uzbekistan, from the Finmind editorial team.
29 Sept 2026
Asset allocation: how to split your money across assets
What asset allocation is, how goals, time horizon and risk capacity shape your mix of cash, fixed income and shares, and what it means on the Uzbek market.
29 Sept 2026
Portfolio rebalancing: when and how to do it
What rebalancing is, calendar and threshold methods, how to rebalance with new money and dividends, and the costs and tax points for UZSE investors.
29 Sept 2026
Position sizing: how much to put in one stock
How to decide how much of your portfolio goes into a single share, with simple sizing rules, worked examples and the liquidity limits of UZSE stocks.
Contact
Questions or a problem to report. Your message reaches the team directly; the answer appears in your Finmind account (Settings, then Support) and in Telegram when your chat is connected.
Prefer email? finmind_support@protonmail.com