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
Cloudflare, at the edge
One Worker per site, with the database and the media on the same platform. No server of your own to lie awake about.
- ✓SSL & uptime monitoring
- ✓Automated backups
- ✓Stated storage and traffic limits
The fleet
One release reaches every site
Data residency
Your data in the EU: if you want it
On request we set your site up with its database and media storage in Cloudflare’s EU jurisdiction. That is not a setting we want to dress up, so here is exactly what it does and does not mean.
- What we guarantee: your database and your files are stored within the EU, and any read replicas stay within the EU too. That is a hard platform constraint, not a preference.
- What we do not claim: that every request to your website is processed in the EU. The application runs on Cloudflare’s global network; forcing processing entirely within one region requires an Enterprise add-on we do not buy.
- What else you should know: Cloudflare is a US company. Where personal data is processed outside the EEA, that happens under the usual safeguards: see our privacy statement.
One practical point: the jurisdiction is fixed when we create the database and the storage, and cannot be changed afterwards. So say so before the build. For an existing site it is a migration, not a checkbox.
Good to know
The technical part, plainly
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.
We back up automatically: weekly on Care and Managed, daily on Growth and Op maat, and watch uptime. We work hard for good availability; guaranteed uninterrupted availability does not exist, 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.
Read on
What does it cost, and what does it earn?
The plans and their limits are on the pricing page; what a design studio earns from it is on the partner programme page.