We settle that in the first call. Rule of thumb: Astro for marketing and content sites, Nuxt or Next.js for interactive applications. If your company already works with Vue or React, we take that into account.
Classic WordPress is quicker to build and cheaper to run. Headless pays off when the same content appears in several channels (website, app, shop) or the frontend has to be especially fast.
One team, one codebase: development is shorter and running costs are lower. Our own app, Zad, was built this way.
You do. You receive the repository, the documentation and access to every service we set up.
We choose providers and contracts so that your data is not used for training, and document where it is processed.
Yes. We start with a short audit of code, plugins, performance and security, then propose what to tackle first.
We run Directus and Strapi self-hosted in the EU if you wish, Sanity as a cloud service. We document the decision with data protection and running costs in mind.
Usually yes – for accounts, content or data. A headless CMS such as Directus is often enough; more complex logic becomes its own API.
Yes. We build parts of the system, review code or support your developers with architecture.
Clearly scoped projects at a fixed price, ongoing development by effort with a monthly report. Both are set out in writing in the proposal.