About FolioFlux
FolioFlux is built to feel native to self-custody operations.
The product is intentionally narrower than a generic finance dashboard. It starts with wallet identity, moves users through import, and keeps portfolio, analytics, and tax workflows tied to the same operational record.
Founder profile
Andrii Furmanets
Independent full-stack developer focused on blockchain product UX.
Portfolio, analytics, and reporting workflows over hype.
Identity begins with the address, not with a generic account form.
Support, privacy, and terms stay visible before onboarding.
Product proof
The public promise maps to real workspaces, not a static pitch.
About pages earn trust faster when the claims point back to inspectable product surfaces. These workflows are the same destinations the wallet-first entry path opens after onboarding.
Portfolio workspace
Holdings, allocation, and value review stay tied to imported wallet activity.
Analytics workspace
Performance and allocation views use the same operational record.
Transactions workspace
Imported and manual activity remains inspectable before tax or reporting work.
Why build it this way
Crypto users should not be forced through generic finance onboarding.
Too many portfolio tools still ask crypto users to create a generic account, land on empty screens, and infer the trust model for themselves. FolioFlux takes the opposite path: connect the wallet, import activity, then move into the specific workspace you intended to reach.
Wallet identity first
FolioFlux starts with wallet-based sign-in because self-custody users should not have to work around an email-first product model.
Trust through public explanation
About, Terms, and Privacy pages exist to explain what the product does, what it does not do, and how wallet-based access works.
Narrow scope over hype
The product focuses on onboarding, imports, analytics, and tax workflows instead of pretending to automate every part of crypto investing.
Trust explanation
Public explanation is part of the product boundary.
FolioFlux uses wallet-based sign-in. We never ask for your private keys, and every signature stays in your wallet app.
Public policy pages and founder contact paths are part of the trust model too. If a product asks for trust, it should explain itself in public before it asks users to sign anything.
What exists today
The public site should point to workflows the product can already prove.
These are the operating surfaces that already exist in the app, and they shape how the product is described in public.
Wallet-based sign-in
Authentication starts with the wallet, and every signature stays in the wallet app.
Activity imports
Blockchain import is the main path, with CSV import available when exchange history needs to come in too.
Portfolio and transactions
Imported activity flows into holdings, transaction history, and the core portfolio workspace.
Analytics workflows
Performance, allocation, and related analytics are tied to the same imported account data.
Tax-report workflows
Cost basis and export flows live in-product so reporting work stays connected to imported history.
Start with the route this page explains
Use the wallet-first path instead of entering through a blank dashboard.
The cleanest entry into FolioFlux is still the same: connect your wallet, import activity, and land inside the workspace you actually intended to open.