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 no per-seat licence that reprices itself every year.
What a web apps engagement includes
Most internal tools begin as a spreadsheet that outgrew itself and end as a SaaS subscription that fits badly. Between those is an application built to the shape of the work, which you own outright.
- A data model built around your process, not a template you bend to fit
- 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 that work, in open formats, tested as a feature rather than promised
- Deployment on infrastructure you choose, including your own
What this looks like in practice
Operations dashboard
One view of what several systems each half-know
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 performed, which is rarely the process as documented. This is where the requirements actually are.02
We build the smallest useful version
One workflow, end to end, in front of real users early — before the shape is expensive 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 exit path.
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 — a tool that cannot talk to your other tools is another silo.
What happens if we stop working with you?
You keep running. That is what the runbook, the documented deploy and the written exit path are for.
Want to talk about sovereignty?
Tell us what you run, where it runs, and who can reach it. We will tell you honestly what moving it to Canadian infrastructure would take.