Your infrastructure.Simplified.
Optimized.

Global reach. Low local latency.
Deploy closer to your users, cloud providers and trading networks in the cities that matter.

Global infrastructure spanning North America, Europe and Asia Pacific
A CONNECTED FOOTPRINTNorth America 13 active · 4 plannedEurope 4 active · 1 plannedAsia Pacific 4 activeExplore locations

01 / OUR SERVICES

The right compute.
In the right place.

Start with what you want to build.
We’ll connect you with the infrastructure
and specialist team to make it happen.

01

Windows VPS

A familiar environment, ready for work. Licensed Windows servers for remote desktops, business applications and automation.

  • Hyper-V
  • Windows licensed
  • Remote access
Try Hyonix

Linux VPS

A flexible foundation for your next idea. KVM virtual servers for web applications, development environments and production workloads.

  • KVM virtualization
  • Application hosting

Bare Metal

Dedicated physical servers for demanding workloads. Direct access to hardware, with the freedom to build around your application.

  • AMD Ryzen
  • Dedicated resources
  • Full control

Dedicated Mac Mini

Apple hardware, exclusively yours. A dedicated Mac environment for development, build workflows and applications that belong on macOS.

  • Apple hardware
  • Dedicated access

02 / GLOBAL FOOTPRINT

A world of reach.
A local advantage.

Bring your workloads closer to the people
who use them. Explore our core and edge locations
and plan your next deployment.

Deployment map. Select a location pin or a city below to explore its facility.

Click a region or select a city for a closer view.

CoreEdgePlanned location
AS931

13 core · 8 edge · 5 planned

Select a city to explore

03 / GLOBAL REACH. LOCAL PRECISION.

Closer to the networks
that matter.

Proximity is more than a pin on a map.
We focus on the local paths between your compute,
your cloud platforms and your trading endpoints.

KRIXE NETWORK · AS931

Your workload.
A closer connection.

Keep traffic close to the cloud and edge networks your applications depend on. Choose the metro, then optimise the route.

Plan your edge deployment

CLOSE TO THE PLATFORMS YOU BUILD ON

BUILT FOR LATENCY-SENSITIVE WORKLOADS

Low latency to the markets you trade.

Place your trading applications close to exchange infrastructure, broker servers and Jito endpoints. Explore the networks below to find a suitable deployment location.

< 1msSelected local endpoints · target

A city match is not a latency measurement. Sub-1ms connectivity depends on the endpoint, facility and network path; confirm it with a route test before deployment.

CRYPTOCURRENCY NETWORKS

Deploy close to your exchange.

Match your deployment to the exchange’s server region, then test the specific API or trading endpoint.

Exchange server locations and closest Krixe locations
Network / marketServer regionClosest location
Binance USDS-M Futures Tokyo · AWS
Binance COIN Futures Tokyo · AWS
Binance European Options Tokyo · AWS
Binance Spot Tokyo · AWS
Binance US Tokyo · AWS
OKX Futures Tokyo · AWS
OKX Swap Tokyo · AWS
OKX Options Tokyo · AWS
OKX Spot Tokyo · AWS
OKX Nitro Spreads Tokyo · AWS
Coinbase Exchange Northern Virginia · AWS
Coinbase Derivatives Chicago · Equinix CH4
Deribit London / Slough · Equinix LD4
Bybit Derivatives Singapore · AWS
Bybit Spot Singapore · AWS
Bybit Options Singapore · AWS
Bybit Spread Singapore · AWS
Kraken Futures London · Equinix
Kraken London · Equinix
Bitfinex Derivatives Switzerland · Market SynergyNearby region
Bitfinex Switzerland · Market SynergyNearby region
KuCoin Futures Tokyo · AWS
KuCoin Spot Tokyo · AWS
Aster Futures Tokyo · AWS
Aster Spot Tokyo · AWS
MEXC Spot Tokyo · AWS
MEXC Futures Tokyo · AWS
Crypto.com Tokyo · AWS
Bitstamp Frankfurt · AWS
Bitvavo Frankfurt · AWS
Bitget Futures Tokyo · AWS
Bitget Spot Tokyo · AWS
Gate.io Futures Tokyo · AWS
Gate.io Tokyo · AWS
HTX Coin-M Futures Tokyo · AWS
HTX Coin-M Perpetual Tokyo · AWS
HTX USDT-M Contracts Tokyo · AWS
HTX Spot Tokyo · AWS
Gemini Northern Virginia · AWS
WOO X Tokyo · Google Cloud
Upbit Seoul · AWSNearby region
Bithumb Seoul · AWSNearby region
Phemex Singapore · AWS
Delta Exchange Tokyo · AWS
Blockchain.com Not published
Bitnomial Ohio · AWSNearby region
bitFlyer Tokyo · Microsoft Azure
HitBTC London / Slough · Equinix LD4
Poloniex Tokyo · AWS
Hyperliquid Tokyo · AWS
Lighter Tokyo · AWS
Lighter RH Tokyo · AWS
Polymarket London · AWS
Bullish Singapore · Google Cloud
dYdX v4 Tokyo · AWS

FOREX NETWORKS

Connect closer to your broker.

Your broker’s account server determines the best location. Find the closest deployment location for the connection you need.

One broker can use several cities.

Check the exact live or demo server and platform in your terminal. MT4 results do not automatically apply to MT5 or cTrader.

These are location matches, not live latency measurements.

04 / INFRASTRUCTURE DESIGN

Built to scale.
Designed for low latency.

Explore how compute, redundant power and diverse network paths come together, from our standard cabinets to direct router connections for trading workloads.

All paths available
Uplink AUplink BPower APower B
STANDARD CABINET CONNECTED CABINETSFollow a link to the trading routers Datacenter feed ADatacenter feed B PDU APDU B Upstream CUpstream CEXCLUSIVEUpstream AUpstream ASHAREDUpstream BUpstream BSHAREDUpstream DUpstream DEXCLUSIVETrading router AOpen cabinet →Trading router BOpen cabinet →Router ARouter ARouter BRouter BSwitch ASwitch ASwitch BSwitch BPDU APDU B3U chassis 1COMPUTE CHASSIS 13U3U chassis 2COMPUTE CHASSIS 23U3U chassis 3COMPUTE CHASSIS 33U1U server 4SERVER 41U1U server 5SERVER 51U1U server 6SERVER 61U ILLUSTRATIVE DESIGN / CONNECTIONS NOT TO SCALE

Select a component to trace its connections.

01 / SCALE

More compute, the same fabric.

Combine multi-node chassis and dedicated rack servers around a shared, redundant network design.

02 / RESILIENCE

Choice at every connection.

Dual power for every device, paired routers and switches, shared upstreams and an exclusive provider on each router.

03 / LOW LATENCY

Direct access for trading.

Trading cabinets connect directly to trading networks. Standard cabinets reach them through the trading routers.

05 / USE CASES

Built for
your workload.

Different workloads need different connections. Start with your application, then choose the compute and location around it.

01 / TRADING TERMINALS

A home for your
automated strategies.

Run MT4, MT5 or cTrader on a Windows VPS close to your broker’s account server. Keep terminals and expert advisors running independently of your own computer.

02 / EXCHANGE CONNECTIVITY

Shorter paths for
data and transactions.

Position market-data consumers, API clients and transaction services near exchange servers or Jito endpoints. Compare the actual network path before deciding where each component belongs.

03 / CLOUD-CONNECTED APPLICATIONS

Keep your application
close to its dependencies.

Place application services near the cloud APIs, databases and edge networks they call. Evaluate local routing alongside compute needs for a practical hybrid deployment.

04 / REGIONAL EDGE SERVICES

Bring regional services
closer to your users.

Plan regional application gateways, game services and content origins around your audience. Use our location explorer and backbone guide to compare primary and secondary deployment cities.

06 / OUR APPROACH TO INFRASTRUCTURE

Built on infrastructure.
Focused on people.

Discuss your infrastructure

Infrastructure decisions deserve a conversation. We work through the details with you, from the first requirements to a practical deployment plan.

Based in Singapore, our team connects a global network with an understanding of local requirements. Tell us who your application serves, which endpoints it relies on and what performance means for your business.

We help you weigh the trade-offs between location, hardware and connectivity, so the infrastructure you choose fits the way you work.

AS931Our network
1.2 TbpsNetwork capacity
21Active locations · 5 planned
3Connected regions
01

Start with your workload.

Your requirements shape the service, from remote desktops and application stacks to trading infrastructure.

02

Think locally. Deploy globally.

Look beyond distance to the facilities, cloud platforms and local routes that affect performance.

03

Bring the details together.

Discuss compute, hardware and connectivity with a team focused on the deployment as a whole.

THE FOUNDATION UNDERNEATH

Connected networks.
Proven infrastructure.

The networks, facilities and hardware behind our deployments.

01 / CONNECTIVITY

Upstream networks

Global connectivity through a diverse mix of network providers.

02 / FACILITIES

Infrastructure providers

Data centres that bring our compute closer to your ecosystem.

03 / HARDWARE

The building blocks

Server, networking, memory and storage technology across our infrastructure.

A FEW USEFUL ANSWERS

Plan with confidence.

From choosing a metro to testing a route, here is what to know before your next deployment.

Ask us a question

Locations & connectivity

How do I choose the right location?

Start with where your users are and which networks your application needs to reach. Choose a region in the location explorer to compare our footprint, then select a city for its facilities and test IP. For cloud or trading workloads, share the exact endpoint with us so we can discuss the local route.

What if my city is not listed?

Search for its full name. When we can identify the city, the explorer suggests our nearest active locations by geographic distance. If several cities share a name, choose the one you mean or add its country. Nearby does not always mean the fastest route, so test the connection that matters to your application.

What do core, edge and planned location mean?

Core and edge are the two groups in our active deployment footprint. Both show their facilities and published test IPs in the explorer; unannounced test IPs are marked TBD. Planned locations are future additions and are shown separately; they do not yet have ordering links or confirmed launch dates.

Can you help with cloud and trading connectivity?

Yes. We focus on local paths toward cloud and edge providers, cryptocurrency networks including Jito, and Forex networks. Send us your target metro, provider and endpoint. We can help you evaluate a deployment location around the connection you need.

Performance & deployment

How can I test latency before deploying?

Select a location and copy its network test IP. Run ping IP_ADDRESS or a traceroute from the network your application will use. That checks your path to the location. For traffic from our infrastructure to a cloud or trading endpoint, contact us to discuss testing that specific route.

Is the < 1 ms target guaranteed everywhere?

The sub-millisecond target concerns selected local trading endpoints. It is not a blanket latency promise across every location or destination. The source, destination, routing and measurement method all matter; confirm the requirements for your deployment with us.

Which services can I order, and where do I see stock?

Windows VPS is available through Hyonix, where you can see live stock, plans and pricing before ordering. Linux VPS, Bare Metal and Dedicated Mac Mini are coming soon. The service cards show their current status.

What should I send with a deployment enquiry?

Tell us the service you need, your preferred locations, CPU and memory requirements, storage and bandwidth expectations, and your intended start date. For latency-sensitive workloads, include the networks or endpoints you need to reach and any measurements you already have.

LET’S BUILD SOMETHING CLOSER

Your next deployment
starts here.

Tell us what you’re building. And where you want to take it.

Talk to our team