since August 2017
Design started in August 2017, the test version shipped in January 2018, and official operations began on January 3, 2019.
iEXExchanger design and development began in August 2017. In November 2017 the team was already working with the early OwlChange exchange project, the first test version shipped in January 2018, and official iEXExchanger operations started on January 3, 2019. The product then grew through real exchange projects and public releases: on February 6, 2019 the first exchanger based on iEXExchanger, JPMarket.cc, was launched; later came the exchanger.iexbase.com beta site, forum topic, news section, and regular versions. Today it is a modern platform with Angular 21 SSR for the customer side, Vue 3 for the admin panel, Tailwind 4, Laravel backend, queues, realtime events, APIs, and ecosystem products.

Design started in August 2017, the test version shipped in January 2018, and official operations began on January 3, 2019.
Since July 6, 2023, the product operates through a company in Dubai Silicon Oasis, UAE.
Modern frontend, Laravel backend, documentation, updates, and separate ecosystem services.
Not simply to sell an “exchange script”, but to give owners a working system: launch, daily operations, security, team control, payment scenarios, scaling, training, and clear post-purchase support.
In the exchange business, a product cannot be judged only by a polished website. Years of development, public discussions, real updates, legal registration, documentation, support, and the ability to adapt to the market all matter.
This history is based on public mentions, archive traces, official news, Telegram posts, and the current product state.
The story is not just version numbers. Releases and internal chronology show how the product moved from a 2017 prototype and the 2018 test version to public releases, a legally formed company, modern architecture, and separate services around exchange businesses.
Development came from real exchangers, operator work, payments, rates, and customer support.
Each stage closed real weak points: documentation, security, integrations, interfaces, and stability.
Over time, separate products, launch services, support, and automation grew around the core platform.
The exchange-product logic was formed: early OwlChange experience, the January 2018 test version, and the move from AngularJS to Angular 2.
The base exchange platform formed: orders, directions, rates, reserves, payments, operators, users, affiliates, notifications, and security.
The system became more than an exchange form: clearer materials, bot scenarios, cloud tariffs, support rules, and infrastructure automation appeared.
A key technology shift happened: from PHP 7.4 support to stopping PHP 7.x support and moving to PHP 8.0.
The focus moved toward customer operations, integrations, support regulations, installation, migration, and maintenance services.
Releases strengthened rates, reserves, BestChange, payment scenarios, and security while the company formalized in the UAE.
The product moved from exchanger.iexbase.com to iexexchanger.com, updated the official website, and kept shipping interface, security, merchant, and BestChange improvements.
New products and services appeared around the exchange business: Telegram Mini App, Marketplace, BestChange support, company registration, SumSub, and service lines.
The platform moved to a new architecture with SmartNotifier, AI, KYC, rates, reserves, customer sections, a new interface, and updated analytics.
News and Telegram show that the product is no longer just a single script archive. Separate services and launch-support directions grew around the exchange platform.
A separate exchange flow inside Telegram: order, history, customer interface, and connection to the main platform.
Self-hosted online chat for exchangers: website widget, operator workspace, history, files, Telegram bridge, email, FAQ, and analytics on the customer server.
Server-side crypto wallet for deposits, payouts, internal transfers, and unique order addresses with keys stored on the owner server.
BestChange rate automation: competitor positions, margin, spreads, reserves, limits, TXT file, and change history.
Module store, ready-made solutions, and additional products around the platform.
Launch support, migration/reinstallation, company registration in UAE/UK/Hong Kong/EU, BestChange preparation, and consulting.
iEXExchanger keeps moving: the architecture changed, interfaces were rewritten, modules were separated, and weak points of older generations were gradually replaced with newer solutions.
Modules grow from real exchanger scenarios: order handling, payment checks, rates, reserves, operator mistakes, security, customer support, and listing preparation.
Older frontend approaches were replaced with Angular 21 SSR, Vue 3, and Tailwind 4 so the product can evolve faster on both customer and admin sides.
The product has public releases, forum discussions, company news, documentation, legal documents, and visible development traces since 2019.
The company continues to develop the platform, release updates, expand the ecosystem, and support customers who need more than a one-time set of files: they need a clear technological foundation for an exchange business.