A small firm
in Leathertown.
Devora Systems builds software for other people and for itself, and publishes the work of developers who would rather build than negotiate with storefronts.
The firm operates from Acton, a mill town at the western edge of Halton Region that spent most of a century known as Leathertown — an economy built on making a durable thing well and stamping a mark on it. It is not much of a metaphor for software, except in the one way that matters: the mark meant somebody was accountable for the thing.
We stay small deliberately. The failure mode of a growing software firm is that the people who sold the work stop being the people who do it, and the quality of what ships becomes a function of who happened to be free that month. Every engagement here has a lead engineer who is in the first scoping call and is still there at handover.
Running our own products is not a side business — it is the thing that keeps our client advice honest. Carrying our own on-call rota, our own migrations, and our own support burden means that when we tell you an architecture will be painful in year two, we are describing something we have already lived through rather than something we read.
Acton, ON L7J 1H3
Canada
What we hold to
You own everything
Source code, infrastructure accounts, domains, and design files are yours from day one, in your repositories and under your billing. No proprietary runtime, no licence that expires, no hostage situation. If you replace us, the next team inherits a working project rather than an archaeology dig.
Boring technology, deliberately
We choose tools by how well they will be supported in five years, not by what is interesting this quarter. Novelty is spent where it produces genuine advantage and nowhere else. Most of your system should be unremarkable, and that is the point.
Estimates are commitments
We quote after scoping, not before, because a number given without understanding is a guess dressed as a promise. Once quoted, the price holds. When scope changes, we price the change in writing before it is built.
Written over verbal
Decisions, trade-offs, and their reasoning go into documents that outlive the people who wrote them. You should never have to rely on a conversation someone half-remembers from eight months ago.
Canadian data residency by default
Where your obligations require it, we architect for Canadian residency and design against PIPEDA from the start rather than retrofitting compliance after an audit finds the gap.
We say no
To work we are not the right firm for, to features that will not survive contact with users, and to timelines that can only be met by shipping something we would be embarrassed by. Declining work we cannot do well is how we protect the work we take.
Work we turn down
Publishing this costs us enquiries. It also means the enquiries we do get are from people who already know how we work.
- Staff augmentation by the seat
- Bodies rented by the month with no responsibility for the outcome. We take responsibility for outcomes or we do not take the work.
- Unpaid pitch work
- Speculative designs and free prototypes are paid for by the clients who did hire the firm. We would rather quote honestly.
- Fixed bids without scoping
- A number given before understanding the problem is a guess. It gets recovered later through change orders, and everybody resents it.
- Work we cannot staff properly
- If taking it on means hiring against a signed contract and hoping, we say no. That is how the work we do take stays good.