From Figma to production
We build from Dev Mode. Type scale, spacing, responsive behaviour and motion live in the engine, so the design survives the build.
- ✓Payload CMS, Next.js & React
- ✓Multilingual and accessible
- ✓Typed, with tests
The platform
One engine, one fleet, one monthly fee
Every site we build is an application on the same versioned engine. That is not a technical preference but the reason we can maintain many sites at once without maintenance running away from us.
The stack
What it runs on
One versioned engine
Every site is a thin app on @rinsly-com/site-core and holds only what makes that site its own. A vulnerability is fixed once.
- ✓Fixed in one release, rolled out fleet-wide
- ✓No plugin sprawl, no WordPress
- ✓Every site keeps its own design
One platform, at the edge
One environment per site, with the database and the media on the same platform. No server of your own to lie awake about.
- ✓SSL, at the edge
- ✓Continuous database recovery
- ✓Stated storage and traffic limits
The fleet
One release reaches every site
Good to know
The technical part, plainly
Every site has a full CMS (Payload, Rinsly CMS): you manage words, pages and media yourself. Each site also gets a staging environment on a separate subdomain, so you can review changes before they go live. The live site runs at the edge; publishing is a deliberate step, not an automatic sync.
Because every site here runs on the same versioned engine. A vulnerability is fixed once and rolled out across the whole fleet. Ten separate WordPress installs, each with its own plugins, cannot be maintained that way, which is why maintenance on them is either expensive or simply not happening.
For the database this is the same for every plan, no distinction: Cloudflare Time Travel gives continuous point-in-time recovery to any moment within the last thirty days. Media files (images, uploads) are backed up nightly to separate storage; deleted and overwritten files remain recoverable. We run on a global edge network and work hard for good availability, but do not run our own active uptime monitoring; a guaranteed uninterrupted availability does not exist regardless, and anyone promising it should not be trusted. If you do want hard response times on paper, that is an SLA on the Custom plan.
The end client’s: the business whose website it is. The website and all its data are and remain their property, and that is in the agreement between Rinsly and that client.
If a design studio designed or invoiced the site, that changes nothing: it does not make the studio the owner of the site or of their client’s data. On termination we help the client transfer the site, data and domain.
Not really, and that is deliberate. The reason we can run many sites at once is precisely that they share one engine. A site on its own stack would give that away, and then we would be an ordinary builder invoicing by the hour.
Measure
Five grades in half a minute
Try our measurement on any URL. Free, without an account.