About
What we run, where we run it, and which claims we are not making yet.
Why FaraServ
Each one is a mechanism you can test rather than a slogan. Where a figure is involved, the way it is measured is published with it.
When the gateway confirms payment, the service is built with no human in the loop: container created, ports opened, game process started. Card-to-card transfers need a receipt checked by hand, so that path is manual and the checkout page says so.
No manual approval on gateway paymentsOn the NVMe line one vCPU is pinned to one physical thread and is never split between customers, so a noisy neighbour cannot steal CPU out of your tick rate. The SSD line is deliberately shared, and it is labelled shared on the plan card.
1 vCPU = 1 physical threadTraffic is scrubbed at the upstream edge before it reaches your machine, and the filter is always on rather than something switched on by hand mid-attack. Per-game UDP profiles are tuned separately so legitimate game traffic is not dropped along with the flood.
Worlds, databases and backups sit on NVMe in the same machine rather than on network storage, so chunk loading and autosave never wait on the datacentre fabric. On the NVMe line those drives are in RAID 10, so one failed disk does not stop the service.
Local storage, not network-attachedA snapshot is taken automatically every day and you can trigger one yourself whenever you like — before a mod install or a version bump, say. Restoring is your own button, not a ticket you file and wait on.
Daily, plus a manual snapshot whenever you want oneThe commitment is that availability gets measured by a prober outside our own network, with the history public on the status page. Until that prober is running, the number you see is a target and is labelled as one. If the SLA is missed, the credit lands on your invoice automatically instead of waiting for you to claim it.
Persian support runs on Telegram and the ticket system because that is where Iranian buyers actually ask; the English side runs on Discord and tickets. We publish no landline until somebody sits behind it — an unanswered number is worse than none.
The delete button is in your own panel and billing for that service stops the moment you press it — no cancellation ticket, no retention call. Unused prepaid time returns to your wallet and can be spent on the next service.
No minimum termNetwork
Ping, jitter and packet loss for every location, published as ranges from Tehran, because a single number is a promise nobody can keep.
| Location | Route | Ping from Tehran | Status |
|---|---|---|---|
| DubaiUnited Arab EmiratesDXB1 | Regional | 35–65 ms+30–55 ms | Available |
| IstanbulTürkiyeIST1 | Regional | 45–75 ms+30–55 ms | Available |
| FrankfurtGermanyFRA1 · Interxion FRA | International | 75–110 ms+30–60 ms | Available |
| AmsterdamNetherlandsAMS1 · AMS-IX | International | 80–115 ms+30–60 ms | Available |
| TehranIranTHR1 · Asiatech | Domestic | 2–12 ms+15–40 ms | Unavailable |
| YerevanArmeniaEVN1 | Regional | 30–60 ms+30–55 ms | Unavailable |
We publish the tools instead of a seal: a looking glass, a status page, and a latency test that runs from your own connection.
These figures are placeholders and must be replaced with measured values before launch.
We display no trust seal you cannot click and verify at the issuer.
Take the smallest plan, start a stopwatch at checkout, and compare what you measure against what this site claims.
No setup fee, no minimum term, and a refund policy that fits on one page.
Refund policy