- pricing
- billing
- currency
- terms-of-service
Pricing a hosting business in a currency that is pegged to the dollar (until it isn't)
Our customers pay in manat, our costs are in dollars, and the manat has been fixed at 1.70 since 2017. Here are the four decisions we made so that a devaluation is a procedure, not a panic.
Most hosting pricing advice assumes you bill in USD or EUR and your costs are in the same currency. Ours are not. We are a hosting provider in Azerbaijan. Customers pay in manat (AZN). Servers, disks, licences and transit are priced in dollars. The manat has been fixed at 1.70 to the dollar since 2017. That sentence contains the whole problem.
A peg is not a guarantee
A fixed exchange rate feels like no exchange risk. It is actually the opposite: no risk at all for years, then all of it at once. Azerbaijan devalued twice in 2015, roughly halving the manat against the dollar within a year. Anyone with dollar costs and manat revenue lost half their margin overnight. The current peg has held for nine years, which tells you nothing about the tenth.
So the question is not "will the rate move" but "what happens to our prices when it does". We spent an afternoon on this and ended up with four decisions.
Decision 1: keep prices in manat
The tempting fix is to price everything in USD and let the manat amount float. We rejected it. Our customers are local businesses; a bill that changes every month in their own currency is a bill they cannot budget for. Local law also expects consumer prices in local currency. Predictability for the customer beats convenience for us.
Decision 2: write the rate into the terms
Our terms now state the assumption out loud: prices were set at 1 USD = 1.70 AZN. If the central bank's official rate moves more than 10% from that level, we may recalculate prices to the new rate. Customers are notified by e-mail, the new prices apply from the next billing period, periods already paid are never touched, and anyone who disagrees can cancel without penalty before the next period.
Two details matter more than they look:
- The threshold is measured from the last applied rate, not the original one. Otherwise a 10% move followed by another 5% move would let us reprice twice from the same baseline. The clause says so explicitly.
- It is a right, not an automation. Nothing in our billing system changes prices on its own. More on that below.
Decision 3: show dollars for foreigners, bill in manat
Some customers are abroad. For them a manat price is noise. In every non-Azerbaijani language the portal and the website now show an approximate USD equivalent next to each price: 14.25 AZN (~$8.38). The rate comes from the central bank's daily XML feed, pulled once a night into a small table; everything else reads from that table, so the portal and the website never disagree. The USD figure is explicitly informational. Payment is still in manat, the card network does the conversion, and the invoice says so.
If the nightly fetch fails, the last good rate stays in place and someone gets a Telegram message. Nothing user-facing breaks on a missing rate.
Decision 4: no automatic repricing, ever
This was the only point where we argued with ourselves. It would be easy to let the system reprice when the rate crosses the threshold. We decided it must never do that.
A devaluation is a political event, not a data point. On the day it happens we want a human to look at the new rate, look at what it does to every customer's bill, decide whether to act at all, and press a button with a second factor. So the repricing exists as an operation in our internal admin tool: a dry run that shows the old and new price for every active service, then confirmation with TOTP, then the customer notices. The 10% threshold only triggers a Telegram alert. The alert tells us; it does not act.
What this costs
Honestly: one afternoon of thinking, a day of implementation, a terms update with the 30-day notice our terms require, and one clause that most customers will never read. The payoff is that the worst day for a manat business is already handled on paper, and the answer to "what do we do now" is "open the tool, read the preview, decide".
If you run a hosting business anywhere with a managed or pegged currency, the specific numbers will differ. The shape of the problem will not.