The things people ask first.
Don't see yours? Send a note, we answer the same day.
Don't see yours? Send a note, we answer the same day.
Can we migrate our existing sites?
Yes, we have a migration playbook for WordPress, Drupal and most static-site setups. Most studios bring their sites over in a weekend.
What does the editor look like for clients?
Like the public site, with a thin floating toolbar. They click the title to edit the title, drag an image to swap an image. A side panel lists every field on the page with a filled or empty dot, so nothing gets left blank by accident.
Can each client have their own design?
Of course. Each site has its own theme repo, its own typography, its own everything. The admin is the only thing that looks the same across them.
Do we host it, or do you?
We host on our own managed Kubernetes cluster
Can a client site sell things?
Yes. Catalog, customer accounts, cart and checkout are four toggles, with cash on delivery, Mollie and Stripe behind them. On top of that sit delivery zones by postcode, promo codes, automatic volume pricing and a bol.com sync. The shop modules are priced per site, on top of that site's own line, so only the client who sells anything pays for them.
What about SEO and speed?
Pages are server-rendered and cached at the edge for five minutes, images resize on request and are served as WebP, and video is transcoded into smaller copies the player picks between. Meta, canonical, Open Graph, JSON-LD, hreflang and sitemaps are emitted for you.
When our Kubernetes nodes are busy, we just add another. It keeps on scaling.
What do we get for cookies and statistics?
The cookie wall ships on every tenant: accept or reject, remembered twelve months, in a dozen languages, with a version you bump to re-ask everyone when the policy changes. Statistics are first-party and read from your own server: pageviews, time on page, scroll depth and outbound clicks, with identifying cookies minted only after consent. No third-party tracker is loaded unless you add one.