Maple Open Tech · Services
Web Apps
Applications that run in the browser and answer to you: your data model, your hosting, your export path, and costs you can plan years ahead.

What’s included in Web Apps
Many internal tools begin as a spreadsheet that has grown up. The next step is an application built to the shape of the work, which you own outright.
- A data model built around your process, shaped to how your team works
- Standards-based APIs, so the next thing you build can talk to this one
- Role-based access that matches how your organisation actually delegates
- Exports in open formats, tested as a feature of every release
- Deployment on infrastructure you choose, including your own
What this looks like in practice
Operations dashboard
One clear view across several systems
Client portal
Documents, approvals and history, per account
Internal workflow tool
The spreadsheet, made multi-user and auditable
How it runs
01
We watch the work happen
The process as your team really performs it. This is where the requirements are.02
We build the smallest useful version
One workflow, end to end, in front of real users early, while the shape is still easy to change.03
We extend it with you
Each addition earns its place by being asked for twice, and ships behind a flag you can turn off.04
We hand over the code and the keys
The repository, the deploy, the runbook and the handover notes.
Questions people ask
Do we own the code?
Yes, outright. Our licence governs the components we bring; anything built for you is yours, in a repository you control.
Can it integrate with what we already run?
That is usually most of the work. Standards-based interfaces are the point, so every tool you run can work together.
Can our own team run it?
Yes. The runbook, the documented deploy and the handover notes are written so your team can run it with or without us.
Let’s talk about Web Apps
Tell us what you are working on, and a person at Maple Open Tech will come back with how we would approach it.


