About
A company built around one conviction
That the description of a system and the system itself should be the same artifact.
What we do
Paduma Technology runs two business models at once. We are a consultancy — self-hosted delivery platforms, distributed systems that have to hold up, architecture models that stay true. And we are a product company, building formal, version-controlled languages for describing software together with the compilers, validators, runtimes and renderers that turn those descriptions into working systems.
The work sits at an unfashionable intersection: language design, formal modelling, and the ordinary engineering discipline of making something reliable enough to run in production. We think that intersection is where the leverage is, and it is why the two halves are the same competence rather than two businesses sharing a name.
Every engagement is scoped to end — set up and hand over, or a bounded project with a date. That is deliberate, and it is for the client's benefit rather than ours: the sensible objection to bringing in outside help is not wanting to depend on it afterwards, and a defined ending with the knowledge transferred is the only honest answer to it.
How we work
Declarations belong in version control
If a description of a system cannot be diffed, reviewed in a merge request and validated in CI, it will drift. Everything we build is plain text first, and tooling second.
Nothing ships without a demanding user
A modelling language is easy to make elegant and useless. LotusTable — a real-time multiplayer mahjong platform with real players — exists partly to keep Statelume honest. Real concurrency and real latency find the gaps that fixtures never will. Statelume is not demonstrated by LotusTable; it builds it.
A claim names the thing that proves it
We keep an internal inventory of what we can do, in which every entry has to name the work that demonstrates it, and is marked according to how deeply it has been proven. Everything on this site is drawn from it. Where we have not done something, you will not find it claimed here — and where a capability has a limit worth knowing, we would rather put the limit on the page than have you discover it later.
Rendering is a projection, never the source
Layout is stored separately from meaning. How a diagram looks must never contaminate what the model says, or the picture quietly becomes the truth and the drift starts again.
Scope is a design decision
Statelume covers behavioural state machines and deliberately not protocol machines. It takes named references and deliberately not embedded expressions. Saying no is most of what keeps a language usable.
Where we are
Paduma Technology Inc. is based in Quebec, Canada, and works with teams remotely. We work in English, and the platforms we build run wherever you want them to — your metal, your colocation, or hosts you rent.