The standard · New Zealand

Same ingredients. Not the same meal.

A chef and a keen cook can shop in the same aisle. The infrastructure under this site is available to anybody with a card — that is the point of it. What is not available off the shelf is the standard: the decisions, the checks, and the work of holding every site to them. That was built once, and every customer sits on it, from the smallest one-page site upward.

233 screens, 40 devices8 checks on every screenEvery deployment keptSame backbone at every price

Three ways to get a website

All three work. They are not the same thing.

	You and an AI, this afternoon	The ordinary way	Built to the standard
Getting it live	An afternoon. An AI walks you through a host, a template and a domain.	A few weeks with a freelancer or an agency, most of it waiting.	Minutes, and the standard underneath it was built once and applies to every site since.
Screens it was checked on	Whatever you looked at, usually your own laptop and your own phone.	Two or three widths, at the end, if there is budget left.	233 screens across 40 devices, folded and open, portrait and landscape, and at 125, 150, 200 and 400 per cent zoom.
What happens when it breaks at 2am	You are the one awake, and the fix is yours.	A ticket, and whoever is on call, if anyone is.	Every deployment is kept. Going back to the last good one is choosing it from a list.
What ships without checking	Anything. There is nothing between you and publish.	Whatever the last person did not test.	Nothing. A release cannot ship until its gates pass: the screens, the checks on each, the prices on the page against the real ones, and the checkout path itself.
What it is made of	A theme, a page builder, and a handful of plug-ins that each update on their own schedule.	A content system, a database, a server and the plug-ins nobody wants to touch.	One file. Text, layout, styling and behaviour in a single document, with the photos packed inside it.
Who has to keep it up	You, forever.	You, or a retainer.	Us. If you leave, the file downloads and runs anywhere without us.

If you enjoy the building, do it yourself. The question this page answers is what it would take to reach this standard on your own, and whether that is a good use of the weeks it would cost you.

For the technical

What a standard actually consists of

It is a standard, not a setting: The infrastructure a small site runs on is available to anyone — that is the point of modern infrastructure. What is not available off the shelf is the decision list: which layer answers which request, what a release has to prove before it is allowed out, what happens to the one customer whose screen is 320 pixels wide, and what the system does when a payment provider answers slowly. That list is the standard. It was built once and every customer sits on it.
The same backbone at every price: There is no cut-down tier of the architecture. The cheapest one-page site is served the same way as the largest custom build: the same network, the same deployment path, the same rollback, the same checks. What changes with the plan is what is included (hosting years, mailboxes, backups), never the engineering underneath.
Measured, not asserted: Every claim about screens on this site is generated from the same list our test harness runs. If a screen appears on the list, a machine opened that screen and looked. Where something cannot be checked (real handsets, Safari, Firefox), we say so rather than implying coverage we do not have.
Built to be left: A site downloads as one file that opens anywhere, with nothing calling home. Keeping customers by making leaving difficult is a business model we decided against; the exit is part of the product.

We are not publishing the recipe: the exact services, how they are wired, and the parts being replaced are ours. What is published is what a customer gets, what is measured, and what is not. The screen list is at every screen we build for.

Exactly what is claimed

Stated precisely, for anyone who needs it that way

What is claimed: That every Veloċi website and the builder itself are designed against a documented list of 233 screen sizes derived from 40 devices, and that a defined set of checks is applied to each screen: overlap, scroll signalling, reachability of the next step, target size, text size, contrast, keyboard and screen-reader behaviour, and reduced motion.
How it is verified: By an automated harness that opens each surface at each screen size in a Chromium browser and records the result. The screen list the page publishes and the list the harness runs are the same file. Results are kept with the build.
What is not claimed: No uptime percentage, no certification, and no testing on physical handsets, Safari or Firefox. Screen sizes for devices whose manufacturer publishes only hardware pixels are derived from those pixels and the device pixel ratio, and are marked as derived on the list.
Infrastructure: Delivery, storage, certificates and DNS are provided by Cloudflare. Payments are processed by Stripe; card details are never received or stored by us. Sites are static documents served from the edge.
Effort: The standard described here was established as a single body of engineering work and is applied to every customer site thereafter, rather than being re-created per project.

Trade marks, third-party material and licences are dealt with separately, at respects and credits.

The honest arithmetic

What it would cost you to match this

Consider the total work involved. If you set out to hold your own site to what is on this page, this is the work: a list of the screens that matter, a way to open your site on each of them, a way to tell whether a bar is covering a word, a way back when a change is wrong, and the discipline to run all of it before every release. It is doable. It is also several weeks, and then it is yours to keep doing.

The 233 screensThe list itself, searchable, with what is checked on each. Against other buildersWhat each one includes, checked on a date we publish. Trust and verificationWho we are, and how to check it independently.

See the standard on your own screen

Open the builder on whatever you are holding. It is the same builder these numbers come from.

Start building

No payment or account to begin. You pay only when you download or publish.

Partner programme

Know a business that needs a website? We pay you $97 when they buy.

Every business finds Veloċi somewhere: an ad, a search, a friend. We'd rather pay the friend. The fees are our advertising budget, paid to the person who brought the customer instead of to Meta, Google or Bing: $36 to $182 a package, plus hosting and mailbox fees every year they stay. The customer pays the same price either way, every partner must say so wherever their link appears, and we never pay for a review.

See the partner programme →Bought a site? Get paid for recommending it