WEBVTT

00:00:03.700 --> 00:00:04.500
Thank you

00:00:04.500 --> 00:00:05.940
for joining

00:00:05.940 --> 00:00:06.280
us

00:00:06.280 --> 00:00:07.000
here at our

00:00:07.000 --> 00:00:07.880
booth of MetaQuotes,

00:00:07.880 --> 00:00:08.300
at the

00:00:08.300 --> 00:00:10.540
iFX EXPO in 2026

00:00:10.540 --> 00:00:11.500
here in Limassol,

00:00:11.500 --> 00:00:12.000
Cyprus.

00:00:12.260 --> 00:00:13.460
It's our honor to

00:00:13.460 --> 00:00:14.060
have you and to

00:00:14.060 --> 00:00:15.060
see you and to speak here

00:00:15.060 --> 00:00:15.520
in person.

00:00:16.240 --> 00:00:17.060
Would you like to

00:00:17.060 --> 00:00:18.160
introduce yourself in

00:00:18.160 --> 00:00:19.480
a couple of lines: what

00:00:19.480 --> 00:00:20.080
you do, which

00:00:20.080 --> 00:00:20.820
company you work

00:00:20.820 --> 00:00:21.680
for? Yeah,

00:00:21.840 --> 00:00:22.580
sure. So

00:00:22.580 --> 00:00:24.040
I'm basically the

00:00:24.040 --> 00:00:25.440
Chief Operating Officer

00:00:25.440 --> 00:00:26.200
of GTCFX,

00:00:26.200 --> 00:00:27.040
and

00:00:27.040 --> 00:00:28.540
we're managing

00:00:28.540 --> 00:00:29.660
multiple

00:00:29.660 --> 00:00:30.180
entities

00:00:30.180 --> 00:00:31.200
throughout the

00:00:31.200 --> 00:00:32.620
world, working with

00:00:32.620 --> 00:00:33.720
various regulations.

00:00:33.720 --> 00:00:34.720
And

00:00:34.720 --> 00:00:35.320
basically

00:00:35.320 --> 00:00:36.160
our main

00:00:36.160 --> 00:00:37.300
driver and our

00:00:37.300 --> 00:00:38.240
main focus was

00:00:38.240 --> 00:00:39.140
on global

00:00:39.140 --> 00:00:40.340
trading. And with

00:00:40.340 --> 00:00:41.020
the help of

00:00:41.020 --> 00:00:42.580
MetaQuotes

00:00:42.580 --> 00:00:43.320
and all

00:00:43.320 --> 00:00:44.240
the

00:00:44.240 --> 00:00:45.140
products that they offer,

00:00:45.140 --> 00:00:46.340
which are MetaTrader 4

00:00:46.340 --> 00:00:47.060
and MetaTrader

00:00:47.060 --> 00:00:48.120
5, we've been

00:00:48.120 --> 00:00:49.000
able to actually

00:00:49.000 --> 00:00:50.040
intensify our

00:00:50.040 --> 00:00:51.480
growth, given

00:00:51.480 --> 00:00:52.700
the stability

00:00:52.700 --> 00:00:53.100
and

00:00:53.100 --> 00:00:54.080
the platform that

00:00:54.080 --> 00:00:54.580
they offer.

00:00:54.580 --> 00:00:56.160
And obviously, you

00:00:56.160 --> 00:00:57.200
know, the ecosystem that

00:00:57.200 --> 00:00:57.920
they've been building

00:00:57.920 --> 00:00:59.000
has always

00:00:59.000 --> 00:01:00.200
been

00:01:00.200 --> 00:01:01.360
top-notch, and

00:01:01.360 --> 00:01:02.100
to me, in

00:01:02.100 --> 00:01:03.160
my personal opinion,

00:01:03.160 --> 00:01:04.300
I believe

00:01:04.300 --> 00:01:05.360
it's becoming the

00:01:05.360 --> 00:01:06.040
new global

00:01:06.040 --> 00:01:07.140
standard for trading,

00:01:07.140 --> 00:01:08.220
especially in the

00:01:08.220 --> 00:01:09.120
CFD market and

00:01:09.120 --> 00:01:10.320
our industry.

00:01:10.320 --> 00:01:11.260
So, you have a history of

00:01:11.260 --> 00:01:12.280
working with MetaQuotes,

00:01:12.280 --> 00:01:13.340
I mean, with

00:01:13.340 --> 00:01:14.300
our trading platforms.

00:01:14.300 --> 00:01:15.320
How are they

00:01:15.320 --> 00:01:16.080
helping you with

00:01:16.080 --> 00:01:17.060
your operations and

00:01:17.060 --> 00:01:18.060
the growth of your company?

00:01:18.060 --> 00:01:18.960
So, we

00:01:18.960 --> 00:01:20.160
are obviously

00:01:20.160 --> 00:01:21.520
using the MetaTrader 4

00:01:21.520 --> 00:01:22.400
and the MetaTrader 5

00:01:22.400 --> 00:01:23.720
platforms, and

00:01:23.720 --> 00:01:24.120
with these

00:01:24.120 --> 00:01:25.100
platforms, we're

00:01:25.100 --> 00:01:27.020
actually utilizing

00:01:27.020 --> 00:01:28.420
certain connectivities

00:01:28.420 --> 00:01:29.360
which are available.

00:01:29.680 --> 00:01:30.140
They've been made

00:01:30.140 --> 00:01:31.160
available by MetaQuotes

00:01:31.160 --> 00:01:32.580
themselves, coming from

00:01:32.580 --> 00:01:33.240
the fact of

00:01:33.240 --> 00:01:33.940
the ease

00:01:33.940 --> 00:01:35.120
of use

00:01:35.120 --> 00:01:35.480
for the

00:01:35.480 --> 00:01:37.100
APIs, as well as

00:01:37.100 --> 00:01:38.300
the capabilities

00:01:38.300 --> 00:01:39.100
of having

00:01:39.100 --> 00:01:40.140
items like

00:01:40.140 --> 00:01:41.060
Ultency, the

00:01:41.060 --> 00:01:42.040
MT5 Gateway,

00:01:42.520 --> 00:01:43.520
other items such

00:01:43.520 --> 00:01:44.260
as routing

00:01:44.260 --> 00:01:45.160
facilitation

00:01:45.160 --> 00:01:46.320
for execution,

00:01:46.320 --> 00:01:47.320
and so

00:01:47.320 --> 00:01:48.200
on. So these

00:01:48.200 --> 00:01:49.020
are items that

00:01:49.020 --> 00:01:50.320
I can briefly

00:01:50.320 --> 00:01:51.420
touch on, as

00:01:51.420 --> 00:01:52.200
they actually

00:01:52.200 --> 00:01:53.020
allowed us

00:01:53.020 --> 00:01:53.840
to enhance

00:01:53.840 --> 00:01:55.240
our growth and

00:01:55.240 --> 00:01:56.000
gave us the

00:01:56.000 --> 00:01:57.340
greater capability

00:01:57.340 --> 00:01:58.360
to actually

00:01:58.360 --> 00:01:59.100
extend

00:01:59.100 --> 00:02:00.320
to various

00:02:00.320 --> 00:02:01.080
regions throughout

00:02:01.080 --> 00:02:02.040
the world with

00:02:02.040 --> 00:02:03.180
the availability

00:02:03.180 --> 00:02:03.860
of, you

00:02:03.860 --> 00:02:05.260
know, globally

00:02:05.260 --> 00:02:06.080
hosted access

00:02:06.080 --> 00:02:07.020
servers, for

00:02:07.020 --> 00:02:08.400
example, and so

00:02:08.400 --> 00:02:08.800
on, which

00:02:08.800 --> 00:02:10.360
are secured

00:02:10.360 --> 00:02:11.440
and promoted to

00:02:11.440 --> 00:02:12.460
us by MetaQuotes

00:02:12.460 --> 00:02:13.340
themselves, which

00:02:13.340 --> 00:02:14.360
gives us

00:02:14.360 --> 00:02:15.260
an ease of

00:02:15.260 --> 00:02:16.320
mind rather than

00:02:16.320 --> 00:02:17.460
having to always go

00:02:17.460 --> 00:02:18.640
to various

00:02:18.640 --> 00:02:19.100
vendors.

00:02:19.420 --> 00:02:20.120
The building of

00:02:20.120 --> 00:02:20.900
the ecosystem

00:02:20.900 --> 00:02:22.340
from the

00:02:22.340 --> 00:02:23.080
MetaTrader 5

00:02:23.080 --> 00:02:24.300
perspective was

00:02:24.300 --> 00:02:25.200
something that was

00:02:25.200 --> 00:02:26.300
very great for

00:02:26.300 --> 00:02:27.260
MetaQuotes because,

00:02:27.260 --> 00:02:28.440
as

00:02:28.440 --> 00:02:29.240
they expanded

00:02:29.240 --> 00:02:30.400
into becoming the

00:02:30.400 --> 00:02:31.280
global standard

00:02:31.280 --> 00:02:32.440
for trading

00:02:32.440 --> 00:02:33.080
CFDs,

00:02:33.080 --> 00:02:34.020
they've

00:02:34.020 --> 00:02:35.100
actually made available the

00:02:35.100 --> 00:02:36.260
multi-asset usage,

00:02:36.260 --> 00:02:37.020
so we can

00:02:37.020 --> 00:02:38.160
actually enter new

00:02:38.160 --> 00:02:39.420
markets at

00:02:39.420 --> 00:02:40.500
a higher,

00:02:40.500 --> 00:02:41.060
global

00:02:41.060 --> 00:02:41.800
scale per

00:02:41.800 --> 00:02:43.060
se. With the

00:02:43.060 --> 00:02:44.120
help of the technology

00:02:44.120 --> 00:02:45.400
that's always emerging,

00:02:45.400 --> 00:02:46.240
MetaQuotes has

00:02:46.240 --> 00:02:47.420
always been on

00:02:47.420 --> 00:02:48.020
the forefront

00:02:48.020 --> 00:02:49.140
of technology, as

00:02:49.140 --> 00:02:50.060
we know. And

00:02:50.060 --> 00:02:51.360
they've been enhancing all

00:02:51.360 --> 00:02:52.320
of their services and

00:02:52.320 --> 00:02:53.120
their capabilities.

00:02:53.120 --> 00:02:54.180
How easy was

00:02:54.180 --> 00:02:55.320
the deployment of

00:02:55.320 --> 00:02:56.260
additional access

00:02:56.260 --> 00:02:57.040
service, and

00:02:57.040 --> 00:02:58.220
which

00:02:58.220 --> 00:02:59.020
problems did it

00:02:59.020 --> 00:03:00.420
solve for you? Okay.

00:03:00.420 --> 00:03:01.020
So, it did

00:03:01.020 --> 00:03:02.020
help solve a lot

00:03:02.020 --> 00:03:03.120
of problems in certain

00:03:03.120 --> 00:03:04.140
regions where

00:03:04.140 --> 00:03:05.200
the deployments

00:03:05.200 --> 00:03:06.200
have existed, such

00:03:06.200 --> 00:03:07.460
as, you know, the introduction of

00:03:07.460 --> 00:03:08.260
Hong Kong region,

00:03:08.260 --> 00:03:09.280
as well as

00:03:09.280 --> 00:03:10.000
the regions in

00:03:10.000 --> 00:03:11.060
Europe and whatnot.

00:03:11.060 --> 00:03:12.020
Those

00:03:12.020 --> 00:03:13.360
assisted us in

00:03:13.360 --> 00:03:14.320
a way where it

00:03:14.320 --> 00:03:15.440
helped us not

00:03:15.440 --> 00:03:16.240
need to go

00:03:16.240 --> 00:03:17.100
look elsewhere.

00:03:17.100 --> 00:03:18.000
And we

00:03:18.000 --> 00:03:19.200
started utilizing these

00:03:19.200 --> 00:03:20.100
access servers to

00:03:20.100 --> 00:03:21.420
give us the lowest most

00:03:21.420 --> 00:03:22.320
possible latency.

00:03:22.320 --> 00:03:23.200
As we

00:03:23.200 --> 00:03:24.460
know, in this industry,

00:03:24.460 --> 00:03:25.580
latency is

00:03:25.580 --> 00:03:26.100
crucial,

00:03:26.100 --> 00:03:27.040
and

00:03:27.040 --> 00:03:28.480
knowing that MetaQuotes

00:03:28.480 --> 00:03:29.340
is making available

00:03:29.340 --> 00:03:30.220
such services,

00:03:30.220 --> 00:03:31.180
it puts

00:03:31.180 --> 00:03:32.100
us at ease,

00:03:32.100 --> 00:03:33.040
knowing that the

00:03:33.040 --> 00:03:34.080
ecosystem works.

00:03:34.080 --> 00:03:35.260
And that's what

00:03:35.260 --> 00:03:36.520
basically helped us

00:03:36.520 --> 00:03:38.000
reach the

00:03:38.000 --> 00:03:39.100
locations that we wanted

00:03:39.100 --> 00:03:40.300
to reach — at

00:03:40.300 --> 00:03:41.240
the lowest possible

00:03:41.240 --> 00:03:42.760
latency, given

00:03:42.760 --> 00:03:43.660
the technology that

00:03:43.660 --> 00:03:44.180
we have today.

00:03:44.180 --> 00:03:45.220
You managed to

00:03:45.220 --> 00:03:46.420
fix the latency between

00:03:46.420 --> 00:03:47.340
your

00:03:47.340 --> 00:03:48.360
servers and

00:03:48.360 --> 00:03:49.280
your clients with

00:03:49.280 --> 00:03:49.940
the access servers.

00:03:49.940 --> 00:03:51.060
Now, how do

00:03:51.060 --> 00:03:52.320
you find it now regarding

00:03:52.320 --> 00:03:53.660
the fixing also

00:03:53.660 --> 00:03:54.620
the latency in

00:03:54.620 --> 00:03:55.580
terms of execution

00:03:55.580 --> 00:03:56.320
with

00:03:56.320 --> 00:03:57.060
the use of

00:03:57.060 --> 00:03:58.360
our newly released

00:03:58.360 --> 00:03:59.140
product, the Ultency

00:03:59.140 --> 00:04:00.060
Matching Engine?

00:04:00.060 --> 00:04:01.360
So, the Ultency

00:04:01.360 --> 00:04:02.300
Matching Engine

00:04:02.300 --> 00:04:03.000
helped us a

00:04:03.000 --> 00:04:04.440
lot in the fact of execution.

00:04:04.440 --> 00:04:05.140
It made it

00:04:05.140 --> 00:04:06.000
more streamlined,

00:04:06.000 --> 00:04:07.160
very speedy

00:04:07.160 --> 00:04:08.440
execution. That's

00:04:08.440 --> 00:04:09.200
what a

00:04:09.200 --> 00:04:10.120
lot of our customers

00:04:10.120 --> 00:04:11.020
are actually

00:04:11.020 --> 00:04:12.080
always requesting.

00:04:12.080 --> 00:04:13.020
And the fact

00:04:13.020 --> 00:04:14.340
that with the usage of

00:04:14.340 --> 00:04:15.160
all of the

00:04:15.160 --> 00:04:16.180
other parts of,

00:04:16.180 --> 00:04:17.220
you know, MetaTrader 5,

00:04:17.220 --> 00:04:17.980
such as,

00:04:18.200 --> 00:04:19.240
you know, the deployment of

00:04:19.240 --> 00:04:20.220
access servers throughout

00:04:20.220 --> 00:04:20.780
the world,

00:04:21.000 --> 00:04:22.000
allowed us to

00:04:22.000 --> 00:04:23.180
always have our trade

00:04:23.180 --> 00:04:24.460
servers accessible in

00:04:24.460 --> 00:04:25.080
the most

00:04:25.080 --> 00:04:25.720
reasonable,

00:04:26.120 --> 00:04:27.020
feasible time,

00:04:27.200 --> 00:04:28.280
regardless to where they

00:04:28.280 --> 00:04:28.980
are in the world.

00:04:29.260 --> 00:04:30.280
And it basically

00:04:30.280 --> 00:04:31.000
gave us a

00:04:31.000 --> 00:04:31.960
sense of stability.

00:04:32.100 --> 00:04:33.240
And that sense of

00:04:33.240 --> 00:04:34.140
stability actually

00:04:34.140 --> 00:04:34.760
helped us

00:04:34.760 --> 00:04:36.060
grow. And now

00:04:36.060 --> 00:04:37.280
we're seeing the growth

00:04:37.280 --> 00:04:38.200
coming from

00:04:38.200 --> 00:04:38.660
the Far

00:04:38.660 --> 00:04:40.100
East, all the

00:04:40.100 --> 00:04:41.160
way from North

00:04:41.160 --> 00:04:42.300
Africa, Europe,

00:04:42.640 --> 00:04:43.260
Middle East,

00:04:43.260 --> 00:04:44.320
at the

00:04:44.320 --> 00:04:45.440
fastest possible

00:04:45.440 --> 00:04:46.160
speed that we

00:04:46.160 --> 00:04:47.500
can actually acquire.

00:04:47.880 --> 00:04:48.620
We've

00:04:48.620 --> 00:04:49.260
tested out

00:04:49.260 --> 00:04:50.080
other vendors,

00:04:50.080 --> 00:04:51.060
but we've

00:04:51.060 --> 00:04:51.880
actually found

00:04:51.880 --> 00:04:53.460
that MetaTrader 5's

00:04:53.460 --> 00:04:54.220
access servers

00:04:54.220 --> 00:04:55.300
seem to be

00:04:55.300 --> 00:04:56.220
one of the quickest

00:04:56.220 --> 00:04:57.380
and allowed us

00:04:57.380 --> 00:04:58.000
to expand

00:04:58.000 --> 00:04:59.440
and grow at

00:04:59.440 --> 00:05:00.440
a large scale.

00:05:00.920 --> 00:05:01.340
Okay,

00:05:01.340 --> 00:05:02.120
how did you

00:05:02.120 --> 00:05:03.020
find the setup of

00:05:03.020 --> 00:05:04.180
Ultency and the

00:05:04.180 --> 00:05:05.480
interface, having

00:05:05.480 --> 00:05:06.000
everything

00:05:06.000 --> 00:05:06.760
in one

00:05:06.760 --> 00:05:08.300
back office,

00:05:08.300 --> 00:05:08.580
in the

00:05:08.580 --> 00:05:10.360
MT5 Administrator, in

00:05:10.360 --> 00:05:11.280
the MT5 Manager,

00:05:11.280 --> 00:05:12.300
compared with,

00:05:12.300 --> 00:05:13.380
uh, let's

00:05:13.380 --> 00:05:14.040
say, other,

00:05:14.040 --> 00:05:15.540
other solutions? What

00:05:15.540 --> 00:05:16.520
was your first

00:05:16.520 --> 00:05:17.280
experience in

00:05:17.280 --> 00:05:18.060
this?

00:05:18.060 --> 00:05:19.600
So one of the first experiences that

00:05:19.600 --> 00:05:20.440
really caught my

00:05:20.440 --> 00:05:21.020
eye is the

00:05:21.020 --> 00:05:22.320
fact that you can control

00:05:22.320 --> 00:05:23.400
Ultency

00:05:23.400 --> 00:05:24.200
from

00:05:24.200 --> 00:05:25.420
one place, one,

00:05:25.420 --> 00:05:26.120
one console,

00:05:26.120 --> 00:05:27.080
right. The

00:05:27.080 --> 00:05:28.140
dream for each and

00:05:28.140 --> 00:05:29.160
every single broker,

00:05:29.160 --> 00:05:30.100
well,

00:05:30.100 --> 00:05:31.160
and any

00:05:31.160 --> 00:05:32.480
users or

00:05:32.480 --> 00:05:33.540
customers in

00:05:33.540 --> 00:05:34.180
this industry

00:05:34.180 --> 00:05:35.440
is to have

00:05:35.440 --> 00:05:35.960
it all in

00:05:35.960 --> 00:05:36.540
one place.

00:05:36.540 --> 00:05:38.240
And with

00:05:38.240 --> 00:05:39.120
that facility,

00:05:39.120 --> 00:05:40.320
it allowed us

00:05:40.320 --> 00:05:41.240
to have greater

00:05:41.240 --> 00:05:42.620
control, and

00:05:42.620 --> 00:05:43.240
it allowed us

00:05:43.240 --> 00:05:44.820
to basically change,

00:05:44.820 --> 00:05:45.420
modify,

00:05:45.420 --> 00:05:46.120
or

00:05:46.120 --> 00:05:47.280
release new items

00:05:47.280 --> 00:05:48.340
through that

00:05:48.340 --> 00:05:49.020
particular

00:05:49.020 --> 00:05:50.780
item, such

00:05:50.780 --> 00:05:51.400
as Ultency,

00:05:51.400 --> 00:05:52.500
for example. And

00:05:52.500 --> 00:05:53.500
Ultency basically

00:05:53.500 --> 00:05:54.320
defeats the

00:05:54.320 --> 00:05:55.220
purpose of having

00:05:55.220 --> 00:05:56.280
to go to

00:05:56.280 --> 00:05:57.300
another solution

00:05:57.300 --> 00:05:58.160
and

00:05:58.160 --> 00:05:59.140
acquiring that

00:05:59.140 --> 00:06:00.280
solution and setting

00:06:00.280 --> 00:06:01.460
up, you

00:06:01.460 --> 00:06:02.420
know, employees

00:06:02.420 --> 00:06:03.060
to learn

00:06:03.060 --> 00:06:04.140
that solution. We

00:06:04.140 --> 00:06:05.300
already had solutions

00:06:05.300 --> 00:06:06.280
which were

00:06:06.280 --> 00:06:07.020
available to us.

00:06:07.020 --> 00:06:08.220
But we found

00:06:08.220 --> 00:06:08.940
the ease

00:06:08.940 --> 00:06:09.580
of usage

00:06:09.580 --> 00:06:11.180
with Ultency, the

00:06:11.180 --> 00:06:13.020
quick deployment, the

00:06:13.020 --> 00:06:14.220
ability to manage it

00:06:14.220 --> 00:06:15.000
and control it through

00:06:15.000 --> 00:06:16.240
the Administrator, and

00:06:16.240 --> 00:06:17.360
as well as the Manager.

00:06:17.360 --> 00:06:18.540
And seeing all

00:06:18.540 --> 00:06:19.460
of your, you

00:06:19.460 --> 00:06:20.100
know, liquidity

00:06:20.100 --> 00:06:21.040
available to

00:06:21.040 --> 00:06:21.800
you in

00:06:21.800 --> 00:06:23.260
one screen was

00:06:23.260 --> 00:06:24.320
much greater than

00:06:24.320 --> 00:06:25.000
what we would have

00:06:25.000 --> 00:06:26.300
expected. Because,

00:06:26.300 --> 00:06:27.080
you know,

00:06:27.080 --> 00:06:28.300
it's better to

00:06:28.300 --> 00:06:29.140
have a

00:06:29.140 --> 00:06:30.360
one-stop shop rather

00:06:30.360 --> 00:06:30.900
than to

00:06:30.900 --> 00:06:31.660
shop around.

00:06:32.020 --> 00:06:33.020
Is it convenient for you

00:06:33.020 --> 00:06:34.060
that you have everything in one

00:06:34.060 --> 00:06:35.040
database and that

00:06:35.040 --> 00:06:35.960
you can see the

00:06:35.960 --> 00:06:37.600
full flow of

00:06:37.600 --> 00:06:38.360
the orders,

00:06:38.440 --> 00:06:39.080
how they are

00:06:39.080 --> 00:06:40.480
received, executed, and

00:06:40.480 --> 00:06:41.260
sent to the liquidity

00:06:41.260 --> 00:06:41.800
providers?

00:06:42.020 --> 00:06:43.060
I mean, did

00:06:43.060 --> 00:06:44.000
you see any convenience

00:06:44.000 --> 00:06:44.380
in that?

00:06:44.780 --> 00:06:46.420
Yes, of course. We actually saw

00:06:46.420 --> 00:06:47.460
a huge difference

00:06:47.460 --> 00:06:48.260
when we were

00:06:48.260 --> 00:06:48.980
doing, you know,

00:06:49.120 --> 00:06:50.160
we were practicing

00:06:50.160 --> 00:06:51.480
data warehousing, and

00:06:51.480 --> 00:06:52.000
with the help

00:06:52.000 --> 00:06:53.260
of MetaTrader 5

00:06:53.260 --> 00:06:54.060
and the data

00:06:54.060 --> 00:06:55.540
warehousing tools that

00:06:55.540 --> 00:06:56.140
were available

00:06:56.140 --> 00:06:57.200
to us, such

00:06:57.200 --> 00:06:58.340
as the connectivity to

00:06:58.340 --> 00:06:59.720
SQL databases and

00:06:59.720 --> 00:07:00.260
other forms

00:07:00.260 --> 00:07:01.280
of databases and

00:07:01.280 --> 00:07:02.060
the introduction of

00:07:02.060 --> 00:07:02.920
Kafka as well,

00:07:03.080 --> 00:07:04.300
helped us actually

00:07:04.300 --> 00:07:05.360
realize real-time

00:07:05.360 --> 00:07:06.100
data

00:07:06.100 --> 00:07:08.540
in really

00:07:08.540 --> 00:07:09.080
no time.

00:07:09.340 --> 00:07:10.580
It was

00:07:10.580 --> 00:07:11.260
very simple,

00:07:11.400 --> 00:07:12.060
very straightforward,

00:07:12.500 --> 00:07:13.100
very easy to

00:07:13.100 --> 00:07:14.020
set up, was

00:07:14.020 --> 00:07:14.800
not complex.

00:07:15.160 --> 00:07:16.700
With the enhancement of

00:07:16.700 --> 00:07:17.420
such features,

00:07:17.760 --> 00:07:18.120
it allowed

00:07:18.120 --> 00:07:18.880
us to

00:07:18.880 --> 00:07:20.160
even understand

00:07:20.160 --> 00:07:21.580
more to

00:07:21.580 --> 00:07:22.040
where our

00:07:22.040 --> 00:07:23.220
business is actually leading

00:07:23.220 --> 00:07:23.720
or going.

00:07:23.980 --> 00:07:25.460
In regards to latency,

00:07:25.460 --> 00:07:26.360
is there any

00:07:26.360 --> 00:07:27.560
specific feature

00:07:27.560 --> 00:07:28.140
that

00:07:28.140 --> 00:07:28.880
comes into your

00:07:28.880 --> 00:07:30.040
mind that you

00:07:30.040 --> 00:07:31.180
would like to see in

00:07:31.180 --> 00:07:32.180
the upcoming updates?

00:07:32.180 --> 00:07:33.480
I can't say

00:07:33.480 --> 00:07:34.160
that there is

00:07:34.160 --> 00:07:35.460
anything missing, per

00:07:35.460 --> 00:07:36.180
se, to run

00:07:36.180 --> 00:07:36.960
a brokerage.

00:07:36.960 --> 00:07:38.260
But what

00:07:38.260 --> 00:07:39.220
would be nice is

00:07:39.220 --> 00:07:40.020
to basically

00:07:40.020 --> 00:07:41.540
maybe enhance it

00:07:41.540 --> 00:07:42.260
with the help

00:07:42.260 --> 00:07:43.000
of, you know, the

00:07:43.000 --> 00:07:44.080
usage of something like

00:07:44.080 --> 00:07:45.040
the AI or

00:07:45.040 --> 00:07:46.280
the introduction of AI

00:07:46.280 --> 00:07:47.640
within the system.

00:07:47.640 --> 00:07:48.240
That would be a

00:07:48.240 --> 00:07:49.140
value-add, I

00:07:49.140 --> 00:07:50.200
believe. Okay, I'm glad

00:07:50.200 --> 00:07:51.000
that you brought it up

00:07:51.000 --> 00:07:52.300
because it's something that

00:07:52.300 --> 00:07:53.620
we are, we're

00:07:53.620 --> 00:07:54.380
considering and

00:07:54.380 --> 00:07:55.060
we are working on.

00:07:55.060 --> 00:07:56.220
So your feedback

00:07:56.220 --> 00:07:57.420
is valuable, so

00:07:57.420 --> 00:07:58.260
we know that we're working

00:07:58.260 --> 00:07:59.120
also in the

00:07:59.120 --> 00:08:00.160
right direction to

00:08:00.160 --> 00:08:01.020
to service

00:08:01.020 --> 00:08:01.480
you guys.

00:08:01.480 --> 00:08:03.600
So, is

00:08:03.600 --> 00:08:04.660
there anything that

00:08:04.660 --> 00:08:05.180
you would like

00:08:05.180 --> 00:08:06.080
us to improve,

00:08:06.080 --> 00:08:06.960
MetaQuotes

00:08:06.960 --> 00:08:08.220
to improve, in

00:08:08.220 --> 00:08:09.200
regards to the platforms

00:08:09.200 --> 00:08:10.180
or to the

00:08:10.180 --> 00:08:11.020
offerings you're

00:08:11.020 --> 00:08:12.160
getting, or any

00:08:12.160 --> 00:08:13.300
additional components?

00:08:13.300 --> 00:08:14.320
Well, there are

00:08:14.320 --> 00:08:15.120
a few items

00:08:15.120 --> 00:08:16.180
that would come

00:08:16.180 --> 00:08:17.240
to mind,

00:08:17.240 --> 00:08:18.300
knowing, you know, there are

00:08:18.300 --> 00:08:19.300
a lot of third parties

00:08:19.300 --> 00:08:20.020
out there. But

00:08:20.020 --> 00:08:21.080
I believe, you know,

00:08:21.080 --> 00:08:22.140
maybe the enhancement of

00:08:22.140 --> 00:08:23.660
the copy trading facilitation

00:08:23.660 --> 00:08:24.220
which is

00:08:24.220 --> 00:08:25.460
available with

00:08:25.460 --> 00:08:26.280
MetaTrader 5

00:08:26.280 --> 00:08:27.160
and MetaTrader 4,

00:08:27.160 --> 00:08:28.240
maybe if

00:08:28.240 --> 00:08:29.040
there was some

00:08:29.040 --> 00:08:30.020
enhancement to it

00:08:30.020 --> 00:08:30.640
to give

00:08:30.640 --> 00:08:32.040
more flexibility, that

00:08:32.040 --> 00:08:33.500
would be much appreciated by

00:08:33.500 --> 00:08:34.400
many brokers, I

00:08:34.400 --> 00:08:35.220
believe. Excellent,

00:08:35.220 --> 00:08:36.000
excellent. Thank you

00:08:36.000 --> 00:08:36.380
so much.

00:08:36.380 --> 00:08:38.060
So thank you

00:08:38.060 --> 00:08:39.260
so much for your feedback and

00:08:39.260 --> 00:08:40.160
for your time.

00:08:40.160 --> 00:08:41.080
We really value

00:08:41.080 --> 00:08:42.400
your cooperation with

00:08:42.400 --> 00:08:43.220
the MetaQuotes,

00:08:43.220 --> 00:08:44.200
and,

00:08:44.200 --> 00:08:45.360
we're

00:08:45.360 --> 00:08:46.340
going to take your feedback and

00:08:46.340 --> 00:08:47.260
work towards that

00:08:47.260 --> 00:08:48.040
direction as well.

00:08:48.040 --> 00:08:49.140
Definitely. So thank you

00:08:49.140 --> 00:08:50.340
so much. Thank you.

00:08:50.340 --> 00:08:50.680
Thank you.

00:08:52.980 --> 00:08:54.380
Thank

00:08:54.380 --> 00:08:55.380
you.