FALBI connects historical replay, account-level risk and live execution in a modular codebase for MetaTrader FX/CFD workflows through MetaApi.
Privately owned · Pre-revenue · Sold as software and agreed transferable IP
Persistent state, journals and broker reconciliation support the execution lifecycle.
An outright acquisition of a privately owned Python software asset for MetaTrader FX/CFD workflows through MetaApi. The project is pre-revenue.
Historical replay and live execution paths, the integrated TA Trader strategy layer, account-specific routing and risk, persistent state, execution journals and broker reconciliation.
A team working with this stack can review the existing modules and decide what it would reuse or integrate into its own workflow.
This is a software asset acquisition. The offer does not include a customer base, a revenue stream, seller trading accounts or a guaranteed trading return.
For a team already building Python and MetaTrader workflows, FALBI offers existing modules to evaluate and integrate. The acquisition gives control of the agreed source and development direction.
ReplayEngine and ReplayBroker provide the historical path. Use them to inspect strategy and execution behaviour with persisted state and journals.
Routing, sizing and risk operate per account. Supported hedging and netting paths handle different order and position models.
The live execution layer includes broker reconciliation, recovery logic and SQLite persistence to support traceable operation.
The integrated TA Trader strategy layer is included. Adapting another strategy is an engineering integration task. Broker, account and MetaApi prerequisites must be checked for the buyer’s deployment.
The available asset is client-side trading infrastructure. Native FIX, exchange connectivity, a broker-server plugin and a hosted multi-tenant service are outside the documented product scope.
Read the architecture and integration scope here. A PDF copy is available below for sharing and offline review.
Historical and live market-data handling feed the included TA Trader strategy layer. The live path includes warmup and synchronization. Replacing the strategy requires mapping new decisions into the documented execution contract.
Routing and sizing operate per account, with configured risk, margin, spread and policy constraints. STANDARD and PROP are account configurations; they do not imply approval by a prop firm or a challenge-pass guarantee.
ExecutionCore and LiveLogicalBroker manage the order and position lifecycle through the MetaApi adapter. The supported hedging path includes staged take profits; the netting path includes partial-close handling.
ReplayEngine and ReplayBroker provide historical evaluation and inspection. Results concern the supplied dataset and environment. A replay result does not establish live-broker acceptance or future investment performance.
SQLite persistence, execution journals, broker reconciliation and reconnect/recovery logic support state tracking. Review should examine ownership of execution requests and broker observations across connection changes.
The buyer validates compatible broker/account access, symbol and risk configuration, service permissions and its deployment environment. MetaApi and other third-party services retain their own terms and costs.
The documented connectivity is MetaApi-integrated MetaTrader FX/CFD. Native FIX, IBKR or exchange adapters, futures/options rollover, broker-server plugins, liquidity hubs and a hosted multi-tenant SaaS service are outside the documented scope. New connectivity and strategy substitutions need separately scoped engineering.
The proposed acceptance record ties one release hash and delivery manifest to the actual demonstration: completed warmup, three sequential controlled broker DEMO round trips, final broker observations, no run-owned orders or positions left open, preserved unrelated trades and confirmed cleanup with no unresolved items.
Real video and sanitized screenshots will accompany the qualified release. A controlled source review follows agreed confidentiality. Complete source delivery follows the written transaction and confirmed funding process.
FALBI is a pre-revenue software asset. The transaction covers source and agreed transferable IP; customers, business revenue and a verified investment track record are outside the offer.
Transfer of the agreed proprietary production source and the owner’s transferable rights under a signed asset purchase agreement.
Review the scope first, qualify your intended use, then agree the asset list, acceptance criteria and funded transfer process.
Concrete terms for discussion. A signed agreement is required to bind either party. The asset list, price and acceptance process are agreed before funding.
The overview, technical scope and proposed terms are readable on this page. Download the PDFs when a file is more convenient.
The final review record will tie the demonstration to one accepted release. Trading profitability is not an acceptance criterion for this engineering asset.
A release hash, run identifier and delivery manifest connect the code being sold to the recorded demonstration.
Warmup, three sequential controlled DEMO round trips, execution observations and journal checks form the planned verification record.
Acceptance includes authoritative final reads, no run-owned positions or orders left open, preserved unrelated trades and no unresolved cleanup items.
The review pack will show the real run, its final status and relevant sanitized evidence. Account identifiers, credentials and private broker data are removed.
This section describes the acceptance evidence to be supplied with the qualified release.
State your intended use, your existing stack and whether you want an outright acquisition. That makes the first discussion specific and useful.
Check the buyer’s Python / MetaTrader scope and the commercial interest.
Review architecture, accepted demonstration evidence and a controlled source sample.
Define rights, archive contents, acceptance and the payment release process.
Deliver the verified archive and documentation with the agreed handover support.
Vladyslav · Independent FALBI owner · vvlad0066@gmail.com