The problem we started from
A shop, a clinic, a tour operator or a school commissions a website. It is
designed and built, it is handed over, and it is accurate on the day it goes
live. Then the hours change for winter. A price goes up. Someone joins and
someone leaves. A number that has been wrong for eight months is still the
number on the contact page, because changing it means finding the person who
built the site, and they have moved on, or they are busy, or the small
invoice for a five-minute edit is not worth anyone's afternoon.
The site is not broken. Nothing errors. It has simply drifted away from the
organisation it describes, and the longer it drifts the less anyone trusts
it — including the people who own it. That is the failure mode we built
against, and it is a content problem long before it is a technical one.
What we decided instead
Your content and your design are kept as
separate things, in separate places, and neither one can break the other.
Your content lives here, in forms. Pages, sections, opening hours, staff,
services, photographs, the phone number. There is nothing to publish and
nothing to rebuild — you save a form, and the next person who loads your
site sees it.
Your design is a theme: a shell, a stylesheet and a small
renderer that receives your content and draws it. Changing theme changes how
your site looks and touches none of your words. That sounds like a small
thing. It means the decision that usually costs a rebuild — “this design has
dated, we need a new site” — costs an afternoon and no content migration.
Why this is not just a CMS. Your site can be hosted
anywhere: a single skeleton file on any host you already pay for, or a free
address on sites.bt. That file asks us for your
content as JSON and for your theme's files, and renders in the visitor's
browser. You are never locked to our hosting, because we are not your host.
Decisions we made that are worth stating plainly
Your images are not on a guessable URL
Uploaded files are stored privately and handed out as signed links that
expire. A document you put in a members' area is not a URL somebody can
guess or a search engine can index by accident. This costs us a little
complexity on every page render and we think it is the right trade.
We measure almost nothing about your visitors
Site analytics record the page that was requested, the host a
visitor arrived from, a broad device class, and the date. There is no
visitor identifier, no cookie, and the IP address is not stored. You can see
which of your pages people read; neither you nor we can follow one person
around. The privacy page lists every field.
The free plan is honest about what pays for it
A free site carries adverts. We say so on the pricing table, on the plan
itself and here, because “free” with an unexplained cost attached is how
people end up feeling tricked by software. Every paid plan removes the
network adverts, starting at the smallest one.
We built the engine underneath it
The platform runs on WONS Engine, our own server runtime — a single binary,
no build step, no JavaScript framework, no dependency tree to audit at three
in the morning. That is an unfashionable choice. It means the whole product
is a handful of files a person can read, it starts in under a second, and it
runs comfortably on modest hardware — which matters when your customers'
visitors are on mobile data.
Who makes this
WONS Sites is built and run by WONS,
in Thimphu, Bhutan. We are a small team, which shapes the product in ways
worth being upfront about: we would rather do a few things properly than
ship a long feature list, we answer support ourselves, and when you write to
us the reply comes from someone who can change the code.
The platform was developed by WONS,
a software company founded in Thimphu in 2023, in collaboration with
ByteTech Labs, an
engineering and infrastructure firm based in Thimphu and Phuentsholing.
WONS
Builds and runs sites.bt
A software company founded in Thimphu in 2023. WONS builds custom software, websites and mobile apps, runs sites.bt, and writes these guides from the questions small organisations actually ask when they try to get online.
wons.bt
We build for Bhutan first — prices in Ngultrum, payment through banks that
exist here, guidance written for someone registering a .bt
domain rather than someone in California. That is not a limitation we are
apologising for. Most website platforms are built for a market where
bandwidth is free and everyone has a card, and it shows.
What we will not do
- Hold your content hostage. Your site's data is available to you as JSON at a stable address. If you leave, you leave with it.
- Put adverts on a plan you paid to remove them from. Advertising is a property of the plan, and every paid plan turns the network off.
- Sell what your visitors do. We do not build visitor profiles and we have nothing to sell, because we do not collect it in the first place.
- Charge you to fix our mistakes. If something we shipped broke your site, fixing it is not billable work.
Where to go next
- How it works — the four steps from nothing to a live site.
- Guides — practical, longer pieces on domains, DNS, photographs and what to actually put on a business website.
- Themes — the 34 designs in the catalogue, each drawn with real content.
- Contact — a form that reaches a person, not a queue.