Software engineering company
We build softwarefor problems worth solving.
Kenresoft is a software engineering company. We design and build web and mobile applications, backend systems, APIs and developer tools for businesses and product teams, and we build our own products too, including Kenresoft CMS.
const projects = await cms.entries
.list({ contentType: 'portfolio' });
// shipped, maintained, still running
return projects.map(toCaseStudy);What we build: Software products, Web applications, Mobile apps, Backend systems, APIs, Edge infrastructure, Developer tools, Open-source packages.
What we build
Products, and the systems behind them.
Most products are several pieces of software working together: a web or mobile client, an API, a database, background jobs and an admin tool. We build all of them, and we choose the stack after we understand the problem.
- 01
Software & Product Engineering
We take products from architecture to production: the client apps people use, and the services, data and admin tools behind them.
- 02
Business & Digital Systems
Internal tools, dashboards, workflow systems and integrations that businesses run their day-to-day work on.
- 03
Architecture & Engineering
We design new systems and restructure existing codebases that have become hard to change or scale. Sometimes that means a new architecture. Often it means reorganizing what's already there.
- 04
Automation & Intelligent Technology
We automate repetitive work and add AI features where they solve a specific problem, not by default.
- 05
Developer Tools & Open Source
Open-source Flutter packages, Kenresoft CMS and other tools that solve recurring engineering problems once.
Selected work
Products, platforms and tools we've built.
01 / Featured
Phunplan
A Flutter app for discovering local activities, planning outings with friends and booking with activity providers. We built and integrated features across the mobile app, including bookings, maps, payments and notifications, and took it through release on Google Play and the App Store.
- Mobile App Development
- Backend & API Integration
- Bookings
- Maps & Location
02
Pathveragroup
The corporate site for a UK education group with five practices, from university admissions to scholarships. We built it in Astro, with separate paths for students, universities and employers.
03
Kenresoft CMS
An open-source headless CMS that runs in your own Cloudflare account. We designed and built the Hono API on Workers, D1 and R2 storage, a separate React admin, and the Astro integration that powers this site.
- 04
ExtensionResoft
An open-source Dart and Flutter package on pub.dev. It collects the form fields, validation, connectivity monitoring, animations and functional helpers we kept rewriting across Flutter projects.
- 05
Lightweight Rich Editor
An open-source rich-text editor for Flutter, built on Flutter's own text-editing primitives. It keeps typing, paste, undo and formatting responsive in long documents.
Why Kenresoft
Writing code has never been easier. Deciding what to build, and building it to last, is still the hard part. That's where we spend our effort.
We start with the problem
Before a framework or a database is chosen, we work out what the software actually needs to do and for whom. The technology follows from that.
One team, full lifecycle
The engineers who design a system also build it and maintain it. Nothing gets lost in a handoff between planning and delivery.
Software built to last
We choose technology the next engineer can understand and change, not whatever looks impressive on launch day.
We build our own tools too
Kenresoft CMS runs this site. We designed it, we maintain it, and we depend on it in production.
Engineering approach
How we engineer software.
We define the problem and its constraints before choosing a framework or a database. Then we design for the long run: clear domain boundaries, layers that change independently, well-defined APIs, and code that stays fast and memory-efficient under real load.
- 01
Understand
We define the problem, the users, the constraints and what success looks like before writing code.
- 02
Design
We set the architecture, domain boundaries and API contracts, including the decisions that get expensive to change later.
- 03
Build
We implement in small increments and keep the code focused on what the product needs.
- 04
Improve
After launch we fix issues, tune performance and extend the system as the product and its users change.
Technology
The stack we ship on.
TypeScript services on Cloudflare Workers, data in D1 and R2, and Flutter for cross-platform mobile. We pick tools the next engineer can read and maintain. This is the stack behind our own products, including this site.
Interface
What people touch- Astro
- React
- Tailwind CSS
- Flutter
- Dart
Services & data
Where the logic lives- TypeScript
- Hono
- Drizzle ORM
- REST APIs
Runtime & edge
Where it runs- Cloudflare Workers
- Cloudflare D1
- Cloudflare R2
Who we work with
Teams who care how the software gets built, not just that it ships.
Founders validating a new product idea, businesses modernizing a system that has outgrown its original design, and teams that need real engineering depth on a problem, not just more code written faster.
Some engagements are a full product built from scratch. Others are one focused piece of a larger system: an API, a migration, an integration, or a performance problem nobody has been able to pin down.
Our product
Kenresoft CMS
Kenresoft CMS is our headless content platform. We built it because we wanted a CMS that runs in our own Cloudflare account: a Hono API on Workers, content in D1, media in R2, and a separate React admin that only talks to the API. It's MIT-licensed, and it serves every page on this site.
API-first, Cloudflare-native
Content is served over a versioned REST API from Workers, with no frontend coupled to it.
Open source
MIT-licensed on GitHub. Deploy it to your own Cloudflare account and extend it.
Draft, schedule, publish
Draft and published states, revision history and scheduled publishing.
Roles and 2FA
Five roles, from owner to viewer, and two-factor authentication.
Audit logs and webhooks
Admin changes are recorded, and webhooks notify other systems when content publishes.
Plugin architecture
Features like e-commerce ship as plugins instead of growing the core.
Engineering notes
Architecture decisions, debugging and trade-offs from the software we build.
Read engineering notes
Let's talk
Have a system to build or fix?
Tell us what you're building, what already exists and where it's stuck. We'll explain how we would approach it.