ORAX.uz
Infrastructure for builders.
In plain words
- What it is
- Hosting is the place on the internet where websites “live”: rented servers, domains and certificates for secure connections. Formerly called CORES.uz.
- Who it’s for
- Anyone launching a website or online service — from individual developers to companies — and resellers who sell hosting on to their own clients.
- What it gives
- Server, domain and certificate in one place, on one bill. Resellers can place orders automatically from their own software.
ORAX — formerly CORES.uz, rebranded — is a hosting platform: shared hosting on ISPmanager or FastPanel, VPS / VDS, dedicated servers, domains, SSL and dedicated IPs, with a knowledge base, a blog and an API for resellers.
Business context
ORAX — formerly CORES.uz — sells hosting, servers and domains with local payment methods. Customers want hosting ready right after payment; resellers want to sell it under their own brand.
The problem
Developers and businesses usually buy servers, domains and messaging from different vendors, each with its own account and billing, and with little local community or support around them.
The solution
One platform with a USD balance and local payment methods. Shared hosting is provisioned automatically after payment, VPS are delivered configured within a business day, and resellers manage services through a signed, idempotent API.
What I built
Built alone — architecture, code and production. No other developers worked on it.
Architecture
- Billing on a USD balance in front of several hosting panels
- A public API (OAuth 2.0 via Passport, 14 scopes) and a reseller API
- An OpenAPI 3.1 specification with 135 paths
Backend
- Automatic provisioning of shared hosting right after payment (ISPmanager, FastPanel)
- Reseller operations: provision, suspend, terminate; files, databases, DNS, SSL
- Dedicated servers through a live supplier auction
Frontend & apps
- Vue.js client platform
- Knowledge base and blog
APIs & integrations
- ISPmanager and FastPanel
- Payme, Click, Xazna, OSON, Paynet, Uzum Bank, WebMoney and cards
- Sign-in with My-IT
- MCP JSON-RPC endpoints for AI agents
Database
- MySQL; customer balances migrated from CORES during the rebrand
Security
- Idempotency-Key on requests that move money
- Reseller webhooks signed with HMAC-SHA256
- Rate limits: 90 requests/min on the public API, 60/min for resellers
Delivery & operations
- Linux servers
- A public status endpoint
Engineering deep dive: From order to provisioning
- A customer orders hosting, a VPS or a domain on orax.uz.
- Payment through a local provider or card tops up the USD balance and pays the order.
- Shared hosting is provisioned automatically in ISPmanager or FastPanel.
- The customer receives access to the new service.
- A reseller does the same through the reseller API — with an Idempotency-Key on every money-moving call.
- ORAX reports changes to the reseller with webhooks signed by X-Orax-Signature.
Technical decisions & trade-offs
- Automate what can be automated — Shared hosting is provisioned automatically after payment; VPS are delivered configured within one business day. (Trade-off: Manual steps for VPS keep the setup right but cap delivery speed.)
- Resellers as API clients — Resellers run provisioning, suspension and termination through their own API keys and receive signed webhooks. (Trade-off: A public reseller contract must stay stable.)
- Idempotent money operations — Requests that move money accept an Idempotency-Key, so a retried request never charges twice. (Trade-off: Clients must generate and keep keys.)
- A rebrand without losing balances — CORES customers and their balances were migrated into ORAX.
Core modules
- Shared hosting (ISPmanager · FastPanel)
- VPS / VDS
- Dedicated servers
- Domains & DNS
- SSL & dedicated IPs
- Reseller API
- Local payment methods
- Knowledge base & blog
orax.uz
Boburbek