Python source · Acquisition / Licensing

Build on existing Python trading infrastructure.

FALBI combines a multi-timeframe TA strategy engine, historical replay and account-specific MetaTrader FX/CFD execution through MetaApi. Acquire the software asset, license existing source for internal use, or agree commercial rights for your own product. A scoped technical pilot is available before a larger licence purchase.

Full acquisition €15,000 · Internal licence €3,000 · Replay Core module €750
Commercial product licence from €4,500 · Technical pilot €350

Need a Python fix or a business automation? Explore scoped project work →

Saved historical replay: 350 days and 455 simulated executions. Inspect the full journal, results and verification status without connecting a runner.

Privately owned · Pre-revenue · Fixed module purchase terms or a negotiated source agreement

One architecture · Two operating paths
Historical replay or live market dataHistory mode / live mode
Strategy decisions + account controlsTA Trader strategy · routing · sizing · risk
Replay broker or MetaApi executionPer-account order and position handling

Persistent state, journals and broker reconciliation support the execution lifecycle.

PythonSource code + documentation
MetaTrader / MetaApiFX / CFD integration scope
Replay + live pathsResearch and execution workflows
Per-account controlsRouting, sizing and risk
FALBI at a glance

The codebase.
The strategy.
The execution foundation.

A privately owned Python software asset for MetaTrader FX/CFD workflows through MetaApi. Choose acquisition, internal or module licensing, or commercial product rights. A paid pilot can check a defined use case. The project is pre-revenue.

What the system contains

TA Trader creates structured plans with entry, stop loss and TP1/TP2/TP3 targets. The surrounding framework provides historical replay, account-specific routing and risk, live execution, persistent state, 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.

What the buyer receives

  • Agreed source files under the selected purchase or licence
  • Framework-wide or module-specific delivery, as agreed
  • Installation, configuration and operating documentation
  • An agreed source and documentation package
  • A bounded written handover, fixed in the agreement

The offers cover software and defined rights. They do not include a customer base, a revenue stream, seller trading accounts or a guaranteed trading return.

What you can acquire

A reusable execution foundation.
A clear engineering scope.

For a team already building Python and MetaTrader workflows, FALBI offers existing modules to evaluate and integrate. Each agreement defines which source files and rights the buyer receives.

01 / REPLAY

Inspect decisions before live use

ReplayEngine and ReplayBroker provide the historical path. Use them to inspect strategy and execution behaviour with persisted state and journals.

02 / ACCOUNT CONTROLS

Keep execution account-specific

Routing, sizing and risk operate per account. Supported hedging and netting paths handle different order and position models.

03 / EXECUTION LIFECYCLE

Track state across broker events

The live execution layer includes broker reconciliation, recovery logic and SQLite persistence to support traceable operation.

Supported scope

Built around MetaTrader FX/CFD integration.

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.

  • RuntimePython; documented dependency profiles and release verification tools
  • ModesHistorical / live; STANDARD / PROP account configurations
  • AccountsAccount-specific routing, sizing and risk; hedging and netting handling
  • StateSQLite persistence, execution journals, reconciliation and recovery
  • StrategyIncluded TA Trader layer; replacements require integration work
Technical overview

From market data
to account execution.

Read the architecture and integration scope here. A PDF copy is available below for sharing and offline review.

TA Trader: context to trade plan

Closed-candle market structure and multi-timeframe context feed trend/correction, breakout/retest and structure-reversal playbooks. Persistent setup state connects analysis to execution planning, normally on a 5-minute base timeframe.

Plans define entry geometry, stop loss and TP1/TP2/TP3 targets. Account checks still decide whether and how a plan can be executed.

One strategy, historical and live paths

The same strategy implementation participates in HISTORY and LIVE operation. Historical replay advances a replay clock and simulated broker; LIVE consumes closed broker candles through MetaApi.

Data-only operation supports observation. Historical replay provides read-only statistics during and after processing.

Independent account controls

AccountRouter applies a shared decision independently to eligible account aliases. Each account has its own state, sizing, risk, Warden and margin checks; one account can accept a different size or reject the decision.

STANDARD and PROP are policy selections. PROP models configurable evaluation/funded stages, pause deadlines and account binding.

Broker execution and ownership

ExecutionCore and LiveLogicalBroker handle the order and position lifecycle through the MetaApi adapter, including ownership mapping and execution keys.

Supported paths include hedging with child-position legs and staged take profits, and netting with partial-close handling. The retained real DEMO qualified one hedging account.

Persistent state and reconciliation

Transactional SQLite state, execution journals and broker reconciliation support recovery and account isolation. The controlled runtime uses WAL and FULL synchronization.

Shared-write horizontal deployment requires a separate persistence and concurrency design.

Defined integration seams

OO components, typed broker/event contracts, a broker factory and event boundaries separate strategy, account policy and transport. Implemented adapters cover mock and MetaApi operation.

MetaApi can connect compatible MetaTrader accounts at different brokers. Exact symbols and specifications must be configured; an independent API needs a new adapter.

Check the integration boundary

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.

Source and operating guides

The source package includes installation, configuration and operating documentation. A controlled technical review can help your team assess the modules against its intended use. The exact delivery contents and transferable rights are agreed before funding.

Prices & delivery scope

Choose the source
and rights you need.

One-time seller asking prices in EUR. The full acquisition transfers agreed proprietary rights; the two licence options are non-exclusive. Exact files, prerequisites, acceptance and fees are agreed before payment.

Non-exclusive

Internal source licence

€3,000

One organisation · one-time licence fee

The agreed framework source for your organisation’s internal research and trading workflows, with permission to make internal modifications.

  • Agreed framework source and existing documentation
  • Internal use by the named licensee; ownership stays with the seller
  • No source resale, redistribution, OEM, hosted customer service or AI-training rights
  • Up to 2 hours of written handover over 7 calendar days after acceptance
Request internal licence
Fixed module package

Replay Core source

€750

One-time · one internal-use licensee

ReplayEngine, ReplayBroker and their required source dependencies, packaged separately with a working CSV integration example.

  • Exact file list and integration notes before purchase
  • Synthetic sample data and completed example output
  • Offline Python 3.12 example, with no broker login
  • Up to 1 hour of written handover within 7 days after purchase
Inspect this fixed package →

Replay Core is a defined module edition with its own file list, example and purchase terms. Other existing modules remain individually scoped and may depend on additional parts of FALBI. New adapters, a customer dashboard, custom strategy development and ongoing operation are separately quoted. For commercial product rights, see the separate offer below. OEM, raw-source redistribution and sublicensing require separately agreed rights.

Commercial use & a smaller first engagement

Build your product.
Or test one defined use case.

Two additional offers with a written scope. Agree the intended use and available inputs before payment. Commercial licensing supplies existing source and agreed rights; the pilot supplies a bounded technical result.

Your commercial product

Commercial derivative licence

from €4,500

One named organisation and product · non-exclusive

Use the agreed FALBI source as a foundation for a substantially differentiated product under your own branding, with the commercial scope fixed in a signed licence.

  • Agreed framework source and existing documentation
  • Rights for the named hosted customer service or packaged product, including object-code distribution as agreed
  • Up to 3 hours of written handover over 14 calendar days after acceptance
  • Seller retains master ownership; no standalone framework resale, raw-source redistribution, sublicensing, OEM or AI-training rights
Define commercial product rights
One defined technical case

Technical fit pilot

€350

Fixed fee · up to 3 hours of scoped technical work

Commission one FALBI replay, configuration or integration-fit check using existing Python, MetaApi or SQLite paths. The question, inputs, deliverables and delivery date are agreed first.

  • One bounded case using agreed synthetic or authorised sample data; live trading is outside the pilot scope
  • Written findings, reproduction or configuration evidence where feasible, and specific next steps
  • Outcome may identify blockers; fixes, new adapters and production deployment are separately quoted
  • The €350 fee is credited once toward a commercial derivative licence for the same organisation and use case within 30 calendar days of pilot delivery
Agree a pilot scope

The commercial price is a starting asking price for the agreed product and rights. A licence does not supply a finished customer-facing platform. Pilot work starts only after written scope, delivery date and funding are confirmed; the fee covers the agreed work and report, with no guarantee of a successful integration or trading result. The licence credit reduces the later balance and is not an additional cash payment or a cash refund. External data, broker, MetaApi and hosting charges are excluded.

Indicative purchase & licence terms

Define the delivery.
Fund the agreed scope.

The terms below describe negotiated full-framework and custom-source deals. The fixed €750 Replay Core edition uses its own published module purchase terms. For a negotiated deal, confirm the exact source, rights, price, acceptance and payment route before funding.

Published asking prices
Full source/IP acquisition: €15,000. Internal source licence: €3,000. Scoped module licence: from €750. Commercial derivative licence: from €4,500. Technical fit pilot: €350. These are seller asking prices. Module and commercial quotes depend on the agreed files, dependencies and rights. Any different price requires the seller’s written acceptance.
Purchase or licence
The full acquisition assigns only the agreed proprietary rights owned and transferable by the seller. The internal and module licences are non-exclusive for one named organisation’s internal use and modification. A commercial derivative licence permits the specifically agreed customer-facing product or service for one named organisation and product. The seller retains master ownership under all licence options. A pilot supplies the agreed technical work and report, with no commercial source licence included. No company shares, customer base, revenue stream or personal broker accounts are included.
Licence boundaries
Internal and module licences exclude hosted customer services. A separately signed commercial derivative licence may permit a substantially differentiated hosted service or packaged product, including object-code distribution, within its named scope. All published licence offers exclude standalone framework resale, raw-source redistribution, sublicensing, OEM and AI/model training or dataset use. Any broader rights require an explicit separate grant. No licence is granted by viewing a demo, receiving review access or downloading public documents.
Seller and delivery
Vladyslav, independent FALBI owner. Full legal identity and payment verification are exchanged privately. The agreement lists the exact release, source files, existing documentation, dependency schedule and rights. Secrets, personal accounts and private runtime data are excluded.
Funding
For negotiated source acquisitions and licences (excluding the fixed Replay Core edition), the buyer funds 100% of the agreed price through a mutually agreed escrow or payment arrangement before the complete inspection archive is delivered. Cleared funding must be confirmed by the provider. Instalments, earn-outs and deferred proceeds are outside the published proposal.
Pilot scope and credit
The €350 pilot covers up to three hours of agreed technical work and a written report. Scope, sample inputs, deliverables, delivery date, acceptance and remedies are confirmed before payment. An inconclusive result or a documented blocker can be a valid finding; a fix or successful integration is not promised. The fee is credited once against a commercial derivative licence purchased by the same organisation for the same use case within 30 calendar days after pilot delivery. The credit reduces the agreed licence balance by €350; it is not cash or a second payment. External service charges and applicable taxes are separate.
Inspection and release
For negotiated source purchases and licences (excluding the fixed Replay Core edition), the proposed inspection window is three calendar days from confirmed delivery of the complete agreed archive, subject to the provider’s supported process. Acceptance checks the written scope and agreed demonstration evidence. Funds are released under the agreed acceptance and provider rules; a provider hold is separate from funds available to the seller.
Material failure
A failure against written acceptance criteria is notified within the agreed inspection window. Remedies, return/refund steps and extensions are fixed in the agreement and provider process before funding.
Rights start
For negotiated deals, the proposed transfer or licence activation condition is cleared payment to the seller, as fixed in the signed agreement. Replay Core purchase activation follows its separate module terms. Earlier inspection access grants only the expressly agreed review rights.
Fees and taxes
Prices are in EUR. Proposed fee allocation: buyer pays the transaction/escrow funding fee; seller pays applicable disbursement and seller-origin marketplace/finder fees. Applicable taxes and bank/intermediary/FX costs are established before funding. A published price does not state the seller’s net receipt.
Bounded handover
Full acquisition: up to six hours over 14 calendar days after acceptance. Internal licence: up to two hours over seven days. Module licence: up to one hour over seven days. Commercial derivative licence: up to three hours over 14 days. These windows start after acceptance. The pilot has its own agreed scope and delivery date. Written handover correspondence covers the delivered source, documentation and configuration. New development and ongoing operation require a separate scope.
Prior and third-party rights
Third-party terms and any prior grants are disclosed before signing. A source/IP buyer receives only the rights actually available; earlier valid licences may survive a later acquisition. New grants must be compatible with existing agreements.
Final agreement
Legal identities, exact assets, permitted use, jurisdiction, acceptance, remedies and liability terms are fixed in writing. The software is pre-revenue. Technical acceptance does not promise trading profitability, prop-challenge success or universal broker compatibility.
Keep a copy

Documents for offline review.

The PDFs describe the negotiated acquisition, internal licence and custom-module offers. The fixed Replay Core edition has its own file list and purchase terms on its product page. The additional commercial derivative and pilot offers are described above and require their own agreed written scope.

Start with a fit check

Four steps to a defined transfer.

For a negotiated framework deal, state your intended use, existing stack, purchase option and deadline. For the fixed Replay Core package, use its shorter purchase process.

01 / FIT

Confirm the use case

Choose the acquisition, licence or pilot scope and check the Python / MetaTrader prerequisites.

02 / REVIEW

Inspect the asset

Review architecture, accepted demonstration evidence and a controlled source sample.

03 / TERMS

Fund the agreed deal

Define rights, archive contents, acceptance and the payment release process.

04 / HANDOVER

Receive the defined release

Deliver the verified archive and documentation with the agreed handover support.

Speak directly with the owner.

Vladyslav · Independent FALBI owner · vvlad0066@gmail.com

Discuss a purchase