We build it end to end
A defined scope, delivered in releases you can test. We own delivery from discovery to go-live.
Best for a new system or a rebuild
ServicesWeb applications
For businesses whose WordPress or Drupal site is slow to edit, slow to load and risky to update. We move the content to a headless CMS with a Next.js front end, or rebuild the site on the CMS you already know. This website is our own example: KTree moved it from WordPress to Payload and Next.js, and every old address still works.
Request a quoteFrom our clients
An Italian pharma company brought KTree in to make their web applications fast.
What you get
A content management system set up around your pages, posts, case studies and forms, with roles for authors and approvers. We work with Payload, Strapi, WordPress and Drupal, and design the content types so each piece is entered once and shown wherever it is needed.
Pages built with Next.js and React and rendered on the server, so they load quickly and search engines can read them. The site works on every screen size and follows accessibility guidelines for people who use assistive tools.
Pages, posts, images and files are moved across. Each old address is mapped to its new page, and page titles, descriptions and the sitemap are carried over, so links and search results keep pointing to the right place.
The site is set up on hosting sized for your traffic, with media on a CDN, a network that serves images and files from a location near the visitor. After launch we look after updates, security fixes and new sections under a support plan. The code, the content and the hosting accounts are yours.
How it works
In an older CMS the editing screens and the public pages are one program, so a plugin update can break the site. A headless CMS separates them: editors work in the CMS, and the public site is its own application that reads the content through an API.
Your options
The cheapest choice this year, and reasonable when the site is small and changes little. The cost is in the plugins and themes: each update is a risk, and editors work around the limits every day.
A new design on a new platform looks like the quick route. If the old addresses are not mapped before launch, links break and the search positions built over years can be lost.
Fast to launch, with hosting and security included, and a good fit for a simple brochure site. It gets hard when you need your own content types, integrations or full control of how pages are built.
One engineering team moves the content, builds the new front end and keeps every address working, at a fixed price when the scope is clear. We did the same move for this website. You own the code, the content and the hosting accounts.
Not praise. The problem, what we built, and what changed.
Ways to work with us
A defined scope, delivered in releases you can test. We own delivery from discovery to go-live.
Best for a new system or a rebuild
Odoo, React, Node, React Native, AWS and PHP engineers who work as part of your team, month by month.
Best for a product that keeps growing
Maintenance, upgrades and urgent fixes for ERP, web and cloud systems, including ones we did not build.
Best for a system already live
Related reading
Before you ask
Short, straight answers. Anything else, ask in the form below and an engineer will reply.
The usual cause of lost rankings is broken addresses, so that is what we protect. Every old address is mapped to its new page, titles and descriptions are carried over, and the list is checked before the switch. Nobody can promise a ranking, but a careful move gives search engines no reason to drop your pages.
A CMS that only stores and manages content, and hands it to the website through an API, a defined way for one program to ask another for data. The public site is a separate application, so it can be fast, and the same content can also feed a mobile app.
No. We build and maintain WordPress and Drupal sites: themes, plugins and modules, speed work, multisite setups and moves between versions. WordPress can also stay as the editing tool behind a new Next.js front end.
By scripts, not by hand. Pages, posts, images and files are exported from the old CMS, loaded into the new one and checked against the old site. Editors review the result before go-live.
Yes. We set up and customize Moodle: themes, course and enrolment changes, reports, and links to other systems such as a CRM or a payment provider. We also move Moodle sites to newer versions.
Request a quote
A senior engineer replies within one working day.